- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Hahaha… Ha… Ha…
Don’t forget about the fabled but often discussed “tech debt sprint”.
At my company we allocate 20% of our time on “Better engineering”, and it counts as impact when you’re up for bonuses/raises so people actually have a reason to push to do it
Words cannot describe the jealousy I am feeling reading this tbh
i saw something like this once and their source was the neatest and most professional i’ve ever seen and it’s convinced me that this is the only way refactoring ever happens.
Worst part is when the un-refactored code continues to confuse other devs, meaning it keeps causing additional work, but you still don’t get time to actually fix it.
Commit1: actual change
Commit2: this code is so misleading and I have to refactor it refactors
Me: painfully rejects PR the story said nothing about refactoring…The mistake is admitting that you’re refactoring. I just implemented the feature/ fixed the bug. Why did I change so much? The issue was a little underscoped.
The fun thing is to try to force your fellow devs to refactor piecemeal through comments on their pull requests.
We build our own prisons.
(I know I’m full of shit, even when I’m writing the comment).
