this post was submitted on 15 Apr 2025
297 points (99.0% liked)

Programmer Humor

22469 readers
1223 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
top 14 comments
sorted by: hot top controversial new old
[–] [email protected] 21 points 1 day ago* (last edited 1 day ago)

Kudos to Spotify's design language for us being able to determine what app it is from just a generic error screenshot

[–] [email protected] 18 points 1 day ago

Another round of tech layoffs and leadership pay increases should fix it

[–] [email protected] 27 points 2 days ago (2 children)
[–] [email protected] 13 points 1 day ago* (last edited 1 day ago)

We also have [email protected]!

OP has a very appropriate username for posting software gore. I guess I kind of do too.

[–] [email protected] 2 points 1 day ago

100% a more fitting community for this post, I just didnt rememeber it at the time

[–] zqwzzle 6 points 1 day ago

There’s a PM out there creating a ticket to fix this issue with some LLM driven nonsense.

[–] [email protected] 4 points 1 day ago

The fact that spotify uses bright green as "fatal-error" color makes me a bit mad.

[–] [email protected] 8 points 2 days ago (4 children)

Unlocalized strings are not errors.

[–] [email protected] 42 points 2 days ago (2 children)

Of course they are an error, what are you talking about.

Error: A mistake; an accidental wrong action or a false statement not made deliberately

[–] [email protected] 5 points 2 days ago

It's a common dictionary, which is probably not very good in this context. I think it would be more appropriate to refer to ISTQB, as it is likely the most relevant source when it comes to software testing and failures:

Human beings make errors (mistakes), which produce defects (faults, bugs), which in turn may result in failures. Humans make errors for various reasons, such as time pressure, complexity of work products, processes, infrastructure or interactions, or simply because they are tired or lack adequate training

Or to put it simple:

We're seeing a failure here.

[–] [email protected] 2 points 1 day ago

Pellaeon started as Rukh brushed silently past him; he hadn't realized the Noghri had followed them down. Thrawn waited until Rukh was standing at his side, then turned back to Colclazure. "Do you know the difference between an error and a mistake, Ensign?"

The entire bridge had gone deathly still. Colclazure swallowed again, his face starting to go pale. "No, sir."

"Anyone can make an error, Ensign. But that error doesn't become a mistake until you refuse to correct it." He raised a finger-

And, almost lazily, pointed.

Pellaeon never even saw Rukh move. Pieterson certainly never had time to scream.

- Hier to the Empire, by Timothy Zahn

[–] [email protected] 16 points 1 day ago

I have several Jira tickets that would like a word with you.

[–] [email protected] 4 points 1 day ago

I guess it depends on the definition, but I'd say they absolutely are errors; if some function produces a result that is both unexpected for the user and outside the design criteria it should be considered an error.