Uncertainty and Learning as Tech Debt
Software engineering is an engine for processing tech debt into concrete learning about the customer
Refactoring
How big should a method be?
How big should a method be? It doesn't matter, as long as the reader isn't tired in reading it or curious to read it.
Saving the day with Continuous Refactoring
Have you run across this scenario before?
1. Dev team keeps getting tight deadlines for feature delivery
2. It responds by shipping tech debt-laden