this post was submitted on 17 Jan 2025
648 points (94.9% liked)
Programmer Humor
32896 readers
1628 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you learn to code, you learn that major bugs in releases are horrible and indicative of neglect.
In a professional sense my experience is that they're more often the result of under-staffing and rigid, fixed release schedules.
And changing priorities and scope.
Yeah, it shouldn't happen in a release. But, if I had a penny for every time I've seen the last minute development that wasn't tested yet and not even due for the current release squeezed in. I'd literally have a pound, or dollar or whatever else has 100 pennies in.
Well it'd be 8 shillings, 4 pence, in pre-decimal British currency.
I sometimes suspect that the push for decimalisation was in part to avoid having to teach computers the old system.
Afaik it actually was, the UK wanted to move more financial calculations to computers and it was a lot easier to use a decimal currency for that
Programming a robust global date-time system and having a transparent conversation between metric and *imperial/traditional" units is just a warm-up to show that you can work with the truly demented currency system. Make sure everything is rounded off to the nearest whole ha'penny.
And sheer pigheaded stubbornness.
Yes. Generally, tons of major bugs in a production release are a sign of the company just not working right in general
Yeah, I learned to code almost 20 years ago in order to mod video games, and learned that many bugs and massive problems in mods and games are caused by coders being either extremely lazy or making extremely dumb decisions.
In general, a ginormous problem with basically all software is technical debt and spaghetti code making things roughly increase in inefficiency and unneccesarry, poorly documented complexity at the same rate as hardware advances in compute power.
Basically nobody ever refactors anything, its just bandaids upon bandaids upon bandaids, because a refactor only makes sense in a 1 or 2 year + timeframe, but basically all corporations only exist in a next quarter timeframe.
This Jack Forge guy is just, just starting to downslope from the peak of the dunning kruger graph of competence vs confidence.
Here's a copy of that image without the watermarks
Didn't even see the watermarks.
Thanks!
I unironically need glasses.