Notes from the work.
Short notes on how we scope, design, build and ship software.
Showing all 9 articles.
The handover is part of the product.
What owning your software really means, with a checklist you can run on any system.
Good software starts before the first line of code.
Why we map the work before writing code, and how it shaped Test-Start's data model.
AI should solve a problem. Not become one.
Three questions we ask before adding AI to a product, and how they shaped Instruktori AI.
Build an MVP with somewhere to grow.
What to keep simple on day one, what to build for growth, and what to cut.
What an AI assistant should refuse to answer.
Why limits make an assistant better, and how we check its answers against a source.
Fixed scope or long-term partnership?
How to choose between a defined project and an ongoing partner, and when to switch.
Multilingual is a data problem.
How we build for many languages from the first schema, and what goes wrong later.
Fast is a design decision.
Why we set a speed budget before design starts, and what we measure.
How we scope a project in one week.
What we ask before we estimate, and what a one-page architecture note looks like.








