The honest report card from a team that has shipped four production apps on RSCs. Mostly good, occasionally rough.
The technical reality
Most engineering decisions are reversible. A few are not. The skill is in knowing which is which, and spending your decision budget accordingly. The teams that ship reliably are not the ones with the most exotic stack — they are the ones who match technology choice to the actual shape of the problem.
- Choose boring technology for the load-bearing parts.
- Reserve novelty for places where it earns a clear, measurable advantage.
- Optimise for the failure modes you can predict, not the ones you cannot.
What we have learned shipping production code
Production teaches lessons that no architectural review can. Code that looked elegant in PR breaks under real load. Patterns that work at ten requests per second collapse at ten thousand. Systems that ship clean require constant gardening to stay that way. The discipline is in the unglamorous middle work — the tests, the dashboards, the runbooks.
- Observability before optimisation. You cannot fix what you cannot see.
- Tests as documentation. The team you hire next year will thank you.
- Boring deployments. Friday afternoon releases should be possible, even if you choose not to do them.
The best code is the code you did not have to write. The second best is the code you can delete a year later without anyone noticing.
Where to invest the next dollar
If you have a fixed engineering budget — and everyone does — the highest return is almost always in developer experience. Faster local environments. Better feedback loops. CI that takes minutes, not hours. These investments do not show up on roadmaps, but they compound across every line of code your team will ever write.
Where this leaves us
If you have read this far, you probably already know whether this thinking maps to your situation or not. We are not interested in convincing you. We are interested in working with the small number of teams who arrive at conclusions like these on their own and then need a partner who can help them act.
If that is you — for engineering work or anything adjacent — come and talk to us. The first conversation is always on us, and it always goes somewhere useful.
Written by Vikram Sundaram for the Lilizon Journal. Published 2025-06-20. Filed under Engineering.