dearProgrammer
Wednesday, 12 Mar 2025
Exclusive insights, data, and analysis for financial market experts.
Search
Have an existing account?
Sign In
**Abandon all hope, ye who enter here.**
This joke is so old, that i had pretty much the same counter i’ve added to my project like 10 years ago. Last time i’ve checked it was increased by 10. I don’t work at that place anymore, but curious how it goes.
I worked on it 2 hours, now everything is fine 🙂
if you work another two hours it gets an overflow error and becomes 0 hours?
“`
dontDead();
open(inside);
“`
Also every attempt should be documented in a new line that says the name of the programmer and the date. Attempts going over multiple days count as 1. Its the start and the moment one gives up that count.
Reset that counter to 1 again, nobody will know.
Just waiting for the sad PR with only the counter changed
drums in the deep. We cannot get out. The shadow moves in the dark. We cannot get out. They are coming.
You know, I see something even remotely close that and my instant reaction would be “yup, never touching this file again”
I’d just try to re-write the routine from scratch….then increase the counter lol
Just see how the code interacts with the rest of the project.
Then write extensive tests that ensure all cases are tested.
Then write it from scratch.
I shit you not, I once had to debug code that had the comment “And this is where the magic happens” at the top of a complicated loop with a regex. Took me days to figure out what the fuck it did.
> Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
Optimize for readability over being smart or being cute.
Just a couple more screenshots! We are almost there!
The real tragedy is that every line of code is a reminder of the time we can’t get back. It’s like a monument to our poor choices and questionable decisions.
Should multiply this by the hourly cost to the company and could use it as a strong argument for allowing time to refactor the code. That could easily be over $20k, even more if there were seniors working on it.
The programmer equivalent of, “Don’t open this door under any circumstances, ever!”
I have a similar comment… for the number of times I see this comment…
God:
Waste 2 hours for a round number
It made me remember of SCP 055 lol
I’m glad I’m not the only one who furiously builds in an autistic flurry just to make a masterpiece and forget how it works after it’s complete
here there are no gods
Emacs
Shut just remove everything and rewrite from now on then, jeeezus
What an idiot they could just dump the code into ChatGPT and say “optimize my code please” and call it a day
r/programmer_irl
>“Everyone knows that debugging is twice as hard as writing a program in the first place. So if you’re as clever as you can be when you write it, how will you ever debug it?”
― Brian Kernighan
we cannot get out: the end comes soon
we hear drums, drums in the deep.
*They are coming*
IDEnvironmental Storytelling
That’s just a challenge, I see this and drop everything I was doing and make it my mission.
Me thinking about refactoring my old projects
“Better not”
i think i know who ai is going to replace
The only thing I see is 254 billable hours 🙂
Related:
[OC]
My least favorite thing about the modern code review process is you never find stuff like this in enterprise anymore.
And that’s the place where you need it the most because everyone who used to know this language at your company have retired and become carpenters.
Try ChatGPT
No problem:
– Declare Scope
– Use factories instead of constructors and inject them.
– Make abstractions for all the classes that was initialized by constructors before.
– Write unit tests.
– Create interfaces by facades, adapters, bridges…
– Adjust the code.
chatgpt, optimise this code. Done.