Ideas on product, engineering and what we learn building real software.
Discovery, responsible AI, systems that can't go down and the real life of a software house. No hype, just what works in practice.
Featured reads.
What is Product Discovery and why it reduces project risk
Before writing the first line of code, we find out what's actually worth building. That's how you reduce risk and waste.
Read article →AI in software development: the risks and how to navigate them
Data leaks, dependency and code nobody understands. How to use AI without giving up control.
Modernize or rewrite a legacy system? How to decide
Rewriting from scratch is almost never the answer. An honest guide to deciding between modernizing and starting over.
Explore by category.
12 articles
Squad staffing vs. hiring developers
Hiring takes months and carries risk; staffing solves it in weeks. We compare cost, speed and risk of both paths.
Software maintenance: when to sustain, when to modernize
Sustain as is or invest in modernizing? The signs to decide — and why modernizing isn't rewriting from scratch.
What is a software house (and how to choose one)
What a real software house is, how it differs from a software factory and a freelancer, and the criteria to choose well.
Usability testing: what it is and why it matters
Watching real people use the product swaps guesswork for evidence. What it is, why it matters and how to run a test.
Prototyping before building: why it pays off
Building is expensive; changing your mind later is more expensive. A prototype lets you fail cheaply before the code.
What is Product Discovery and why it reduces project risk
Before writing the first line of code, we find out what's actually worth building. That's how you reduce risk and waste.
AI in software development: the risks and how to navigate them
Data leaks, dependency and code nobody understands. How to use AI in development without giving up control.
Modernize or rewrite a legacy system? How to decide
Rewriting from scratch is almost never the answer. An honest guide to deciding between modernizing and starting over.
Code review that teaches, not humiliates
Code review is a team's best mentoring tool. As long as it's about the code, not the ego.
A roadmap is not a feature list
A feature list becomes an infinite backlog. A good roadmap talks to the business metric, not this month's wish.
Beautiful because it works: UX people get on the first try
A good interface disappears. The user remembers what they accomplished, not the button they had to hunt for.
Human review: why every AI output passes through a specialist
AI accelerates, but the responsibility stays ours. How we set up the process before anything goes to production.
Tests that bore you to write pay off in production
A critical system can't go down. We explain why the extra care starts long before deploy.
Strangler fig: modernize without taking the system down
The pattern that lets you change the plane's engine mid-flight: evolving the legacy without bringing the operation down.
Allocated squad: joining your team without breaking your process
Staffing senior people is more than sending résumés. It's joining the client's rhythm, process and tools.
Design system: the base that lets your product grow
Components, tokens and consistency. Why investing early in a design system saves months down the line.
Technology partners, not vendors: what changes in practice
We don't just deliver what was asked. We think about your business the way a CTO would, and that changes everything.
No articles in this category yet.