It could work if it was some important code that caused some castrophic event… and the end he sees he actually changed those lines…that ended up causing the thing to fail.
To get the nuance right, it’s like if you lived your very normal average every day life, day after day, never intentionally hurting anyone or anything. Then found out you murdered someone weeks/months/years after the fact and were asked how you did it.
the worst part about debugging for me, is i have no idea how long it will be before i can solve a single bug. it could take me 2 hours, 1 day, a week, no idea. Because i have no idea where the bug came from. I have ti go through increasingly more detailed testing cycles. Then devise more laborious testing cycles. This is why i chose not to work as a programmer. In other professions, I know i can give an estimate of the time taken to complete the task. Debugging? No real idea. What if the boss says finish it by tomorrow? I might be there all night.
In my experience coming up through Windows desktop development, more than half the time the murderer was a closed source, compiled, dependency, that only behaved oddly in extremely specific circumstances.
the worst part for me, was not only being unable to estimate the time to solve the bug, i found that often the problem was in syntax or shadings of understanding on how functions or bracket syntax worked. i could refer to all the biggest programming books off the shelves, and the answers they provided would not work. Programming is one of those professions where answers lay with people who had busted their brains or lucked it trying to make it work, and had collected over many years, snippets of code which they knew worked. If you weren’t chummy with these people, you would never find the answer. This isn’t really a worthwhile profession. Unlike physics, or maths, where there is an independent answer governed by forces outside of an individual human, programming is a profession which inherently depends on learning errors from another human. It’s a pointless profession and gets you nowhere in life at the end. Sadly. (Unlike say law, or accounting or physics, where at old age, you know more about the world around you.)
I spent like 2 hours on a really time sensitive bug today, I even resorted to asking chat gpt, the solution was… doing what I did in the first 5 minutes a second time… 😭
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
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.
It’s more like this: it feels like you are both the detective, the victim and the murdere
I’d watch a noir detective film about a programmer going over some wackadoodle code.
It could work if it was some important code that caused some castrophic event… and the end he sees he actually changed those lines…that ended up causing the thing to fail.
Index Out of Bounds: A classic off-by-one mystery
I’m the last person I would have suspected, but I was looking for me all the time!
When you use
git blamejust to realize, that you’re the only contributor to the repository…And it was… me. It’s always me.
Don’t you dare Sixth Sense me.
Patrick Star
My sister thinks this is a mental illness.
To get the nuance right, it’s like if you lived your very normal average every day life, day after day, never intentionally hurting anyone or anything. Then found out you murdered someone weeks/months/years after the fact and were asked how you did it.
the worst part about debugging for me, is i have no idea how long it will be before i can solve a single bug. it could take me 2 hours, 1 day, a week, no idea. Because i have no idea where the bug came from. I have ti go through increasingly more detailed testing cycles. Then devise more laborious testing cycles. This is why i chose not to work as a programmer. In other professions, I know i can give an estimate of the time taken to complete the task. Debugging? No real idea. What if the boss says finish it by tomorrow? I might be there all night.
Looking for a new job I hope…
In my experience coming up through Windows desktop development, more than half the time the murderer was a closed source, compiled, dependency, that only behaved oddly in extremely specific circumstances.
the worst part for me, was not only being unable to estimate the time to solve the bug, i found that often the problem was in syntax or shadings of understanding on how functions or bracket syntax worked. i could refer to all the biggest programming books off the shelves, and the answers they provided would not work. Programming is one of those professions where answers lay with people who had busted their brains or lucked it trying to make it work, and had collected over many years, snippets of code which they knew worked. If you weren’t chummy with these people, you would never find the answer. This isn’t really a worthwhile profession. Unlike physics, or maths, where there is an independent answer governed by forces outside of an individual human, programming is a profession which inherently depends on learning errors from another human. It’s a pointless profession and gets you nowhere in life at the end. Sadly. (Unlike say law, or accounting or physics, where at old age, you know more about the world around you.)
deleted by creator
I spent like 2 hours on a really time sensitive bug today, I even resorted to asking chat gpt, the solution was… doing what I did in the first 5 minutes a second time… 😭
git blamesays the culprit was me but how did that happen?Yup, this image with a
git blamereference is available too but I preferred the Scooby Doo one.