Velocity measures how much you ship. Cadence measures how often.
Why we shifted
On a 10-week build, a team shipping a small thing every two days outperforms a team shipping a big thing every two weeks — even when the second team’s "velocity" is higher on paper.
- Smaller batches are reversible.
- Smaller batches keep stakeholders engaged.
- Smaller batches surface integration risk early.
How we instrument it
We track time-since-last-merge per engineer per day. If it climbs past 36 hours, that is the standup topic.
Testing Medusa: What to Test, What to Skip, and How
Commerce code moves money, so untested checkout logic is a liability. A pragmatic test strategy — what earns its keep, and what is theatre.
Observability for Medusa: Logs, Traces and the Alerts Worth Having
Self-hosting means owning the question 'is checkout working?'. Structured logging, tracing, the four metrics that matter and alerts that do not cry wolf.
Caching Medusa: What to Cache, Where, and What Never To
Four cache layers, one rule about carts, and the invalidation strategy that stops a price change taking twelve hours to appear.