The way I heard it, and think sounds better, is below.
99 little bugs in the code,
99 bugs in the code.
Fix one bug, compile it again,
101 little bugs in the code.
For a more modern version, you could go with
Send it to Claude, compile it again,
1001 little bugs in the code.
Close to the one I heard as well
99 issues with bugs in the code
99 issues with bugs
You take one down, ya patch it around
You got 105 issues with bugs in the code
My neck hurts from just looking at that setup.
This may just be my age showing, but unless you’re stuck writing .net, or maybe java, then there’s no reason to have more than 120chars of horizontal real-estate in your IDE. Get a 16:10 monitor and flip it 90° instead.
Also who codes like that in a professional context? How do you read your notepad, when all you have is some christmas ornamentation for lighting? Again it may be an age thing, but often I rely more on my pencil and notepad than my mouse.
I don’t understand why people go to wide formatting. If you stick to 80 columns, you can fit like 4 different files side by side at the same time on today’s monitors. No more flipping back and forth!
Because Windows. Also, you gotta flip back and forth to hide your entertainment, like a nudey mag in a comic book.
You don’t understand, its clearly the workstation of an MSFT engineer who needs to 50 nested deep entries of XML lol.
Agreed, I could never order my punch cards with lighting like this. I’m also unsure how the keyboard and mouse are working without the PS/2 jack and cable, and those potted plants aren’t anything like the Devonian flora I’m familiar with.
Get a 16:10 monitor and flip it 90° instead.

Have you tried it? It’s marvelous. You can fit soo many lines at once. I always keep a monitor in portrait mode.
the neck pain alone would negate any boost to productivity.
I just use a standing desk with a 4k 70" screen. I have all the width and height I’ll ever need with proper text scaling.

The phonetics or w/e of the lyrics lining up is doing something itchy to my brain.
Proposed improvement:
99 bugs in the code on the wall,
99 bugs in the code.
Take one down,
patch it around,
1456 bugs in the code on the wall!
Take one down, prompt it around, -2,147,483,648 bugs on the wall!
Different error means progress!
Or regression.
Hey, no one said what we were progressing towards. We could be progressing towards the goal, a dead end, or disaster
Future progress
Some days… Ill take regression over no change at all
As a little segue, is this the best way to organize 2x 34" monitors, I’d thought to go side by side but have no idea.
Vertically oriented (portrait) screen(s) go to the side.
Two ultrawides next to each other involves two things that eventually get annoying:
- lot of head turning, fine at first but ends up achey
- your keyboard is either centred on one screen, or centred on neither, and at some point you’ll always end up twisted - typing in one direction and looking in another.
Neither seemed like a big deal to me at first but it seems like most people end up at vertical stacking.
Also it uses way less desk space.
99 bottles of bugs on the wall
99 bottles of bugs
Take 1 down
Give it to claude
1456 bugs on the wall
that monitor setup looks designed in a lab to fuck up your neck
I have something similar. Most of my “notice” stuff is up top: email, slack, dashboard, etc. Code on bottom. Sometimes if I’m being active in lots of things, I’ll stand as needed to look at the top monitor properly.
don’t you lose rven faintly ergonomic access to your input devices if you stand up tho?
I’ve never bought into the “top of the monitor should be at eye level” stuff that DSE guidance teaches. I reckon for a single screen, my eyes should be level with the top third of the screen – so I don’t have to crane my neck, but I’m also not encouraged to hunch over.
First it’s bottles of bugs, then just bugs. The units of measurement don’t match!
100 bugs on the wall, please submit all support requests through authorized channels only 😛
deleted by creator
The little rascals breed like tribbles.
Me, trying to fix failing tests my colleagues keep ignoring.
“48 of 1307 fail, but for these seven it’s this’d the assertion expecting a new enum value, easy!”
“106 of 1307 fail. What the fuck?”
Well, at least now you know why they keep ignoring them.
Their solution was to remove them from the pipeline. And I wondered why test coverage went down in SonarQube.
0.9% is not a lot of coverage, let me tell you that.
So I was given a project after a major part of it was made by an AI fanatic coworker and right before delivery, we were asked to make some specific types of documentation to submit.
One of which included code coverage reports.The party receiving the documentation then said that they need 100% test coverage…
Of a GUI application that interfaces with multiple proprietary devices over serial port, network, USB etc and is dependent upon the physical environment to get all code paths.I just gave that all to the AI fanatic coworker and am not even planning on reading the test code.
If the program itself satisfies my logical requirements, I’ll ask him to change the test code to match the changed application code.One hundred percent coverage is obviously not realistic. But I would wish there were more tests at least checking core components.
Sounds like they just poured out one of the bottles
It’s appropriate this image has a bug
Jokes like this will never be not funny; and it boosted my confidence today ( seriously) as I find a difficult bug of my own.
Honestly, about my own bug; I don’t see why scrambled data is so bad. Keeps users on their toes, and avoids them becoming too complacent










