this post was submitted on 09 Dec 2025
1268 points (99.5% liked)
Programmer Humor
27827 readers
906 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
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
Sounds about right. There is no longer any incentive to focus on maintenance and incremental improvement (the stuff that actually keeps the lights on and the revenue flowing). It's all about the new and shiny--even when it results in regression.
Which is why AI and vibe coding will survive. Besides the part where it’s not my code, the company owns it. The fuck do I care how good it is. If it works and gets me a promoted or moved to a new spot in a different company. Heck yeah. Issues down the road are not my problem.
Personal project: page load takes under 10kB and any button or link loads in millisecond.
Work project: Fuck it 26MB page load. It's not like the pages load in under 5s before anyway.
The personal project is a matter of personal pride, whereas for work, any old thing will do, as long as it meets the requirements.
I’m in business operations, downstream from you guys. Reading posts like these are helping me understand better what you all are going through.
We had several of our systems “upgraded” and broke a lot of our tools. The dev team vanished off to work on the next shiny bullshit “upgrade” and turned my 15 minute tickets into 3-4 hour tickets.
My manager was telling me to ping someone and let them know. After nothing happened there, I started opening tickets. After about 140 in 2 weeks, I finally got someone’s attention and we’re grudgingly getting a couple devs assigned to start repairing the automation that broke.
I am sorry to have to do that, but our entire team was drowning and pinging someone on teams with API errors wasn’t getting anything done.
It's a terrible working arrangement in most companies--particularly between dev and infrastructure teams. "Legacy" sysadmins that were previously celebrated for maintaining rock-solid environments with high uptime are now denigrated (and eliminated) when they can't make up a new shiny for MBA managers (who are not real leaders)--to peddle the same bullshit to senior executives.
It's all fucked.