this post was submitted on 25 Feb 2024
8 points (100.0% liked)

Programmer Humor

32316 readers
203 users here now

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

Rules:

founded 5 years ago
MODERATORS
 
top 22 comments
sorted by: hot top controversial new old
[–] Hotzilla@sopuli.xyz 2 points 8 months ago* (last edited 8 months ago) (5 children)

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 2 points 8 months ago (2 children)

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

[–] Tier1BuildABear@lemmy.world 1 points 8 months ago (1 children)

A gun that shoots eagles, obviously

[–] Sombyr@lemmy.zip 1 points 8 months ago

We don't shoot eagles in America, we shoot turkeys. Just as Benjamin Franklin intended.

[–] infinitepcg@lemmy.world 1 points 8 months ago (1 children)

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

[–] pennomi@lemmy.world 1 points 8 months ago (2 children)

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 1 points 8 months ago* (last edited 8 months ago)

Pretty much the hardware version of && false

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 1 points 8 months ago

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

[–] Jumuta@sh.itjust.works 1 points 8 months ago (1 children)

it's an orbiter not a lander

It was intended to be an orbiter.

[–] MooseLad@lemmy.world 1 points 8 months ago (1 children)

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

[–] NaibofTabr@infosec.pub 1 points 8 months ago

Technically the US measurement system is metric since the Mendenhall Order of 1893 reestablished all customary units as conversion factors of metric units. In 1933 the ASA redefined the inch to be exactly 25.4mm, following the lead of the British Standards Institution in 1930 (precision was increasingly important for manufacturing, and the previous value of 25.40005mm had become impractical). The international yard and pound were officially adopted by the US National Bereau of Standards (now NIST) in 1959, the Metric Conversion Act was passed in 1975, and finally EO 12770 (1991) required all agencies of the executive branch to transition to metric units.

So, from one point of view we've been transitioning to metric since 1893 and it's still not done. From another, the inch is just a metric unit as its length is officially defined in millimeters (all customary units are now based on SI units), therefore the conversion is complete.

[–] dan@upvote.au 0 points 8 months ago (1 children)

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,

[–] wim@lemmy.sdf.org 0 points 8 months ago (1 children)

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 0 points 8 months ago* (last edited 8 months ago) (1 children)

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.

[–] Bene7rddso@feddit.de 0 points 8 months ago

Are you committing to master? I don't see any reason why you shouldn't commit your debugging code to your own branch. Obviously clean it up before merging

[–] SolarMech@slrpnk.net 0 points 8 months ago (1 children)

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

[–] OsrsNeedsF2P@lemmy.ml 1 points 8 months ago (1 children)

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 1 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.