this post was submitted on 31 Mar 2026
143 points (99.3% liked)
Programming
26392 readers
173 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
Why do engineers do this?
Simply fix the relevant technical debt as part of implementing a feature or fixing a bug. That way you can chip away at it over time.
Waiting for the big removal of technical debt will never come. It’s an ongoing process.
Leave the code base better than you found it – always.
The answer is to say “We will try our best, but this is very ambitious.” Then you let the deadline pass, usually it’s artificial in the first place. When the deadline passes say: “As we feared this took longer than we hoped for.”
If there’s some urgent feature request coming from sales then that means the Thursday deadline is in the contract and it’s already signed.
So what? If you weren’t consulted when the deadline was set, it’s not your problem. Have some balls and rip your bosses a new one when they pull bullshit like this. “That deadline was unattainable when it was set. Had our team been consulted, we could’ve worked on a solution. But since sales went over our heads, this is their mess to clean up.”
You don't with in software do you? The software guy always gets blamed anyway.
Yeah so there's absolutely no reason not to pipe up on bullshit like this
To quote my manager from today: “I don’t want us to spin our wheels and turn this into a month long effort”
The request is to effectively rearchitect a foundational part of the system. It’s a large lift project that should take weeks.
Of course I pushed back, I have good rapport with him and I’m not worried about getting fired over this. Not everyone has that.
“This isn’t a bazaar. We don’t haggle over deadlines. We professionally estimate them.”
Nevermind, it does sound like you work in software. This is a very familiar quote. x.x And it always comes right before planning slows to a crawl.
I've never heard the phrase "We professionally estimate deadlines", but I'm gonna start using it. Thanks for that!
“You want the four year sabotage and effort instead of the one to two month long effort?”
Yes, the investors require it.
As the tech lead at my company, I treat all deadlines as fake until proven otherwise.
Also, when they start pressing me for dates that things can be done, I start multiplying by 4…
Multiplying by Pi is what I do. :)