I never thought of tech debt as a tool, that's an interesting perspective.
If it's a deliberate decision to take it on (like in the case of the mobile app), I think this is a valid point. A lot of times, tech debt ends up being created on accident by invalid assumptions, changing requirements or simply mistakes. I think, those two need to be differentiated.
In the end, perfect is the enemy of good and striving for zero tech debt will likely stall any progress. So will too much of it.
#(Cool) Dev
