962
Shiiieeettt....... (lemmy.world)
top 50 comments
sorted by: hot top controversial new old
[-] Hotzilla@sopuli.xyz 274 points 8 months ago* (last edited 8 months ago)

They did it once by mixing meters and feets, and crashed the Mars lander.

Edit: looked it up, wasn't actually meters vs feet, but newton-seconds vs some American eagles per gun unit for force

[-] nul@programming.dev 76 points 8 months ago

It's guns per eagle, get it right. What would eagles per gun even be?

[-] infinitepcg@lemmy.world 30 points 8 months ago

it happened again with the Intuitive Machines lander that landed on the moon last week

[-] pennomi@lemmy.world 53 points 8 months ago

The Intuitive Machines lander issue was that no one disarmed the safety switch on the laser guidance system. (No, really!) Luckily NASA had a backup system installed that ended up working better anyway.

[-] infinitepcg@lemmy.world 27 points 8 months ago* (last edited 8 months ago)

Pretty much the hardware version of && false

[-] threelonmusketeers@sh.itjust.works 13 points 8 months ago

that ended up working better anyway

Not sure if it ended up working better, as it landed with nonzero horizontal velocity. Though I suppose we'll never know how well the original system would have performed...

[-] c0mbatbag3l@lemmy.world 21 points 8 months ago

Pound-seconds, I believe. Good ol' LM giving imperial numbers to NASA.

load more comments (1 replies)
[-] MooseLad@lemmy.world 15 points 8 months ago

Hopefully, the transition to metric is soon and I can stop reading this same joke every week.

load more comments (1 replies)
[-] Jumuta@sh.itjust.works 13 points 8 months ago

it's an orbiter not a lander

[-] threelonmusketeers@sh.itjust.works 38 points 8 months ago

It was intended to be an orbiter.

[-] SolarMech@slrpnk.net 79 points 8 months ago

If a TODO passes code review, more than one person fucked up.

[-] OsrsNeedsF2P@lemmy.ml 32 points 8 months ago

At my first job after university, we did releases every Friday evening. From 3-5pm, all you would see in the Slack channel was a flurry of everyone committing straight to master (with a bunch of merge conflict commits between). Oh and then we'd release. Fun times.

[-] ShadowCatEXE@lemmy.world 17 points 8 months ago

A free for all, late Friday deployment is baffling… We’ve got a strict window of Tuesday-Thursday for releases (unless it’s a critical issue), and a 2-3 day merge freeze to help mitigate unexpected changes.

We’ve got a relatively small team with LOTS of moving parts, so minimizing deployment issues is always top of mind.

[-] SchizoDenji@lemm.ee 9 points 8 months ago

I literally know multi billion dollar B2C startups doing the same. It's got so toxic that the management regularly fires people and to fill their spots, they offer obscene amounts of money just for starter positions.

load more comments (1 replies)
[-] winky9827b@lemmy.world 23 points 8 months ago

Eh, then you just get those idiots who avoid using TODO: because it makes the code review "harder".

// This is a broken example.
// Note: remove X before doing Y
[-] targetx@programming.dev 11 points 8 months ago

That's no longer a technical process issue but more of a teamcoach/HR kind of issue then. You should be able to assume good intentions from colleagues, imho.

[-] Patches@sh.itjust.works 6 points 8 months ago

You guys do code reviews?

load more comments (4 replies)
[-] sbv@sh.itjust.works 78 points 8 months ago

I feel like modern compilers would turn their nose up at that shit. "Dead code? Ewww! No way I'm letting that into my syntax tree!"

[-] ShortN0te@lemmy.ml 72 points 8 months ago

A lot of IDEs would probably throw a warning about unreachable code.

[-] bus_factor@lemmy.world 25 points 8 months ago

Golang won't even compile with dead code. Unfortunately that's too strict, you just end up commenting out the whole block instead. At least the commented out code is obvious in review, and some automated checks catch it if you have them.

load more comments (1 replies)
[-] Pyroglyph@lemmy.world 13 points 8 months ago

implying that any developer actually reads warnings

[-] vox@sopuli.xyz 14 points 8 months ago* (last edited 8 months ago)

most of my (rust) projects have zero (or maybe 1-2) warnings, unless I'm in the middle of working on a feature

[-] micka190@lemmy.world 24 points 8 months ago

First thing I do on my projects is enable warnings as errors and increase my warning levels when reasonable.

Unfortunately, the same can't be said on the projects I work on at work. Drives me crazy that we get likes 300+ warnings whenever we run the app and that we can't change it because "they're just warnings*.

[-] Alexstarfire@lemmy.world 8 points 8 months ago

🤢 Good lord.

Though, I say that as I was basically forced to accept code that was using something marked deprecated because it was unreasonable to refactoring the code in that project. And I know we're never going to change it unless it stops working. 😭 At least I marked it as an issue on the review.

[-] micka190@lemmy.world 9 points 8 months ago

Oh yeah, I'm genuinely about to hand-in my resignation as soon as I find another job over this kind of shit. I keep being told that the business is really trying to clean-up its act when it comes to coding practices, but they keep putting some of the most incompetent people I've ever worked with in charge of shit (because they do promotions based on years of experience instead of actual actionable experience). It's awful.

[-] PoolloverNathan@programming.dev 7 points 8 months ago

That's when you add #![deny(bad_code)], making sure that nobody notices.

load more comments (5 replies)
[-] 1stTime4MeInMCU@mander.xyz 12 points 8 months ago

Guess what? Flight Software usually uses ancient proprietary compilers for specialized hardware running an RTOS, rip 😢

[-] sbv@sh.itjust.works 6 points 8 months ago

Woah woah WOAH WOAH.

So you're saying software for the Artemis landers aren't being built with the latest TypeScript compiler and running on a canary version of v8?!

load more comments (2 replies)
[-] dan@upvote.au 58 points 8 months ago

At my workplace, we have a lint rule that reports an error if @nocommit is anywhere in the file, plus a commit hook that blocks all commits with @nocommit anywhere in them. It works well and has saved me a few times.

Works pretty well, except the lint rule and its associated tests have to do something like "@no"+"commit" to avoid triggering it,

[-] bus_factor@lemmy.world 15 points 8 months ago

I did the same thing with "DO NOT MERGE" back in the day. Saved some people who didn't even know about the check.

[-] wim@lemmy.sdf.org 6 points 8 months ago

In a lot of modern work flows this is incompatible with the development pattern.

For example, at my job we have to roll a test release through CI that we then have to deploy to a test kubernetes cluster. You can't even do that if the build is failing because of linting issues.

[-] dan@upvote.au 10 points 8 months ago* (last edited 8 months ago)

The test release shouldn't have anything marked with @nocommit though... The idea is that you use it to mark code that is only temporary local debugging code that should never be committed.

load more comments (2 replies)
[-] EdibleFriend@lemmy.world 18 points 8 months ago

Dude looks like Hank and Dale had a baby.

[-] darkdemize@sh.itjust.works 10 points 8 months ago
load more comments (2 replies)
[-] Bishma@discuss.tchncs.de 16 points 8 months ago

Isn't this pretty much what happened with the LIDAR on the most recent commercial moon lander?

[-] Steve@startrek.website 10 points 8 months ago

Yes but it was a physical switch

load more comments (1 replies)
[-] OpenStars@startrek.website 15 points 8 months ago

B-b-but it clearly says right there in the todo, that's good enough, r-r-right?!

[-] Bishma@discuss.tchncs.de 17 points 8 months ago

I mean, my IDE highlights all the TODO's in yellow. I don't know how we could possibly make it any less error prone.

[-] bus_factor@lemmy.world 8 points 8 months ago

That requires someone to look at that section in the IDE. If it doesn't block the merge, it doesn't do shit.

load more comments (2 replies)
load more comments (7 replies)
[-] RedditWanderer@lemmy.world 12 points 8 months ago

If anyone is interested there is a wonderful walk about one of the apollo flight computers

load more comments (1 replies)
[-] summerof69@lemm.ee 11 points 8 months ago

This got a lot of compression over less than a couple of hours!

[-] Plavatos@sh.itjust.works 7 points 8 months ago

Anyone know the artist? Saw another one by them a couple days ago about brute force protection.

[-] lud@lemm.ee 9 points 8 months ago* (last edited 8 months ago)

The source is a user on Reddit: https://www.reddit.com/r/ProgrammerHumor/comments/1ayuh4b/comment/krx0p8h/ There are a few more on their profile.

Thanks Google lens

[-] intensely_human@lemm.ee 7 points 8 months ago

git blame

Naomi Nagata

[-] MonkderZweite@feddit.ch 7 points 8 months ago

They still have those control desks in modern missions?

load more comments
view more: next ›
this post was submitted on 25 Feb 2024
962 points (98.1% liked)

Programmer Humor

32360 readers
1337 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS