Technical debt: 3 signals that cost you before you see them
Technical debt shows up in the team’s daily work before it shows up in the code. Three concrete signals to detect it before it gets expensive.
Signals
Articles on reducing technical chaos: debt, needless complexity, dependencies. Concrete practices for sober, durable systems.
Needless complexity: the price of “just in case”
Every layer added “just in case” is paid for daily: in reading, testing, onboarding. How to spot the complexity that serves no one.
Keeping ownership of your system, even without being technical
A system you cannot leave is not yours. Three simple tests to know whether you truly keep ownership of what is built for you.