What Is Technical Debt, and When Does It Become Dangerous?
A plain definition of technical debt, why every early product has some on purpose, the signs it is becoming a problem, and how to manage it without a rewrite.
Read more9 posts on Glossary.
A plain definition of technical debt, why every early product has some on purpose, the signs it is becoming a problem, and how to manage it without a rewrite.
Read moreThe part of your product users never see, what it does, why it is often half the budget, and the questions to ask about it.
Read moreWhat the frontend covers, how it relates to design and to the backend, and why one product can have several.
Read moreThe one technical concept every founder should understand: how software talks to software, and why it decides what your product can connect to and grow into.
Read moreWhat the phrase covers, what actually matters about it for a non-technical founder, and the one thing you should insist on.
Read moreWhat a database is, why its design in the first release matters for years, and the questions about backup, ownership and privacy every founder should ask.
Read moreWhere your product actually runs, what the cloud bill covers, typical monthly costs for an early product, and the account ownership rule that is not negotiable.
Read moreThe difference between a clickable prototype and a functional one, what each proves, what they cost, and how a functional prototype becomes the first slice of the real product.
Read moreThree words that get used interchangeably and mean different things, what each is for in a project, and which one you should be reviewing at each stage.
Read more