this post was submitted on 18 Jan 2024
292 points (97.4% liked)

Programmer Humor

23248 readers
953 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
 

cross-posted from: https://feddit.de/post/7998794

cross-posted from: https://feddit.de/post/7998742

Meme transcription: 4 panels of Vince McMahon reacting increasingly ecstaticly to:

  1. Your software isn’t working. Vince McMahon looks curious.
  2. The bug is in a library. McMahon smiles.
  3. There already is an issue on Github. McMahon makes an orgiastic face.
  4. They published a fix last week. [I don’t know how to describe the face McMahon is making.]
top 12 comments
sorted by: hot top controversial new old
[–] [email protected] 45 points 1 year ago (1 children)
  • The bug is from a library
  • There are 5 dozen related bugs on GitHub
  • The last commit to the library was 3 years ago
[–] [email protected] 7 points 1 year ago
  • Library is a read-only repo
  • last commit was 10 years ago
[–] [email protected] 22 points 1 year ago* (last edited 1 year ago)

Another version of this is unexpectedly finding some niche, single-developer software tool that does precisely the thing you need, all because some genius angel stranger (strangel?) from the internet happened to encounter the same problem, and somehow knew how to fix it.

[–] [email protected] 14 points 1 year ago

And then you wake up.

[–] [email protected] 11 points 1 year ago (2 children)
[–] [email protected] 10 points 1 year ago

Time to write a ‘Known limitations’ section.

[–] [email protected] 4 points 1 year ago (1 children)

Time to compile it myself.

[–] [email protected] 1 points 1 year ago

I'm tired, I thought it's published next week

[–] [email protected] 9 points 1 year ago

This has happened to me once, in 20 years of development.

That's pretty good.

[–] [email protected] 6 points 1 year ago

The bug is in the library of a library that the library owns. They fixed it and published it in the library of the library but the library hasn’t been updated in 2 months.

[–] [email protected] 5 points 1 year ago

And the library update isn't published for 6 months

[–] [email protected] 3 points 1 year ago

I just went through this exact process (not for the first time) two weeks ago with a bug in the golang standard library. Fun times. Deep in the dependency stack of a container build my team doesn't own so who knows when I'll get a fixed version.