(no title)
Deritio | 3 years ago
Or clean code because no one will ever touch it again.
Or a feature you only need once and just write it somehow.
And then all this shit stays in your product and starts dragging you down.
This is totally different than when you start with a monolith and know that you might want to rework it later but accept potential future work.
And you should start with a modular monolith anyway.
I don't think it's reasonable to try to redefine the term technical debt.
No comments yet.