4 ms·
I worked on team once where tech debt was "avoided" at all cost. It actually had a weird effect on the code base. We had a practice of writing a pull request 3
by 49531 10y ago
I worked on team once where tech debt was "avoided" at all cost. It actually had a weird effect on the code base. We had a practice of writing a pull request 3 times before shipping it, kind of refactoring everything before we merged it.
We ended up with a really complicated codebase as a result. It was tricky to dive into the project because everything seemed so layered with complexity.
Now a days I try to take the most naïve approach to a bug or feature, that way if something breaks it's straightforward to fix. I only abstract when a process has slowed me down a few times.
This is all done with your normal tech debt fighting tools though, like linting, style guides, CI and unit tests.
- PaulHoule 10y agoThis is part of the problem with quantifying "technical debt", that is, what some people think is "good code" is overengineering.
- ScottBurson 10y ago"Perfection is finally attained not when there is no longer anything to add, but when there is no longer anything to take away." -- Antoine de Saint-Exupéry
- njharman 10y agoYour team failed to avoid technical debt. Needless complexity and over engineering are debts.
- ktRolster 10y ago>It was tricky to dive into the project because everything seemed so layered with complexity. That's technical debt. Good code makes things easier to add, work gets done faster, not slower.