Engineering notes
How we think, starting from real problems. Each note starts from a general question, explains the decision and points to the case where we applied it.
Vulnerability assessment: how to tell if the critical findings in your report are real
We received a vulnerability assessment of our company website with critical findings. How do we know they are real before paying to fix them?
Where we applied it: A security-assessment product
02Rewrite a legacy system or migrate it by domain?
A twenty-year-old system still runs the operation. Do you throw it away and rebuild, or take it apart one piece at a time?
Where we applied it: An insurance group
03How to move from REST to GraphQL without rewriting the frontend
Dozens of services change their contract. Does the frontend that uses them have to change on the same day?
Where we applied it: A private healthcare network
04Entering an ecosystem of forty microservices
The service count says little. What actually matters when you enter a system of this size?
Where we applied it: A consumer platform with payments and subscriptions
05When a remote call should become a local rule
A calculation calls another service fourteen times for one answer. Is the problem the network or the design?
Where we applied it: A consumer platform with payments and subscriptions
06A switch for every fragile integration
The ERP is changing and the onboarding flow writes into it. Does everything stop until it is ready?
Where we applied it: A private healthcare network
Describe the system. We'll tell you what we see.
Ten minutes, one question at a time. At the end, our honest read of the case. It's the filter, before the call.