4 ms·
“this works, but next time, a better architecture would be x, let's refactor next time we come back to this” In my experience there is rarely ever a “next time
by logbiscuitswave 4y ago
“this works, but next time, a better architecture would be x, let's refactor next time we come back to this”
In my experience there is rarely ever a “next time” and “fix it later” becomes “fix it never”. It’s always cheapest to fix worst practices up front rather than letting them metastasize into a huge pile of technical debt later. It’s also rare to find anybody interested in or willing to go back and fix old stuff when priorities often involve chasing the next shiny thing.
- strix_varius 4y agoExactly - this, coupled with phrases like "blowing up the sprint," suggests that nobody on this team is likely to trust that the offer of "fixing it later, next time" will be held to.
- bcrosby95 4y agoMy rule is code at inception doesn't have to be the best, but every time you touch existing code you must make it better. Then the code that gets touched the most gets touched up the most. Code that doesn't ever get touched is fine being kinda crappy.