this post was submitted on 26 Mar 2026
40 points (97.6% liked)
Programming
26237 readers
516 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
STORY TIME.
I once worked with a guy who spent so much time and energy trying to prove he has smarter than any of us. That smug bastard was a senior contractor paid twice as much as us lowly regular contractors. I once had to do some simple evolutions on one of his projects. Seriously it was one of the worst shit code I've ever seen.
Every single line had to be a 200-character long hack of nested functions, ternary operators and conditional operations. It's like this condescending fucker was living in a hackathon where the most simple shit had to be implemented in the most brain-fucking, unreadable, convoluted manner, in as few lines as possible. His code was a literal fucking brick wall of symbols. It's like this fucking idiot never heard of if..else blocks and/or decided that ternary operators were the only way to do conditional statements.
This cunt was fucking proud that none of us rubes was able to maintain his shitstain code. He even gave me a smug smile when I started working on this dumpster fire.
Anyway, I trashed the whole thing and rewrote it from scratch in a "dumb" way. Lots of air, simple unitary instructions, a code so simple a non-tech person could probably follow it along with little difficulty. Oh, I also fixed several major bugs and design flaws while reimplementing it.
Guess which version is still in production and has been evolved and maintained by more than a dozen contributors since then?
Funny thing is, when he eventually got booted from the project, we realized that nobody could maintain his code, not even himself. Since his main project wasn't in my department I barely looked at it when he was here, but when I was asked to take a look, a simple commit history check told me everything I needed to know why every single feature took fucking weeks to be released.
Surprised he got as far as he did. Every line of code that touches production should be reviewed.
If it's shit, fail it until it ain't. To allow that shows a distinct lack of technical leadership.
You've since shown far more and that should build trust. Never trust contractors without verification.
It was a long time ago when code reviews were not yet standard practice everywhere. He was also protected by one of the few customer's employees in the team, who was almost universally hated, because they bonded over some controversial political views.
Yeah nowadays this code would never make it past a PR.