Engineering Decisions Show Up in Your NPS Score
Three years of NPS data showed a direct correlation with engineering quality investments — which changed how I make the case for technical work to the business
Three years of NPS data showed a direct correlation with engineering quality investments — which changed how I make the case for technical work to the business
What we learned from a year of structured AI adoption — real multipliers by task type, how we chose our tools, and why the bottleneck moved from writing code to reviewing it
From 11+ engineers in two teams to 46 across four offices — what breaks at each growth stage and what you have to rebuild deliberately
For years we deferred technical debt to keep moving. Then we stopped everything for one quarter — and the results changed how we think about engineering quality permanently.
A close look at engineering hiring numbers — 1.6% application-to-hire rate, 89% offer acceptance, and why both numbers matter
How we handled revisiting an architectural decision that turned out to be wrong — and what it taught us about the second half of disagree-and-commit
Why top-down performance reviews miss the most important work engineers do, and what changes when you add 360-degree input to the process
How a pattern of large pull requests led us to abandon feature branches — and what we learned about diagnosing the right problem
How a flat QA team more than tripled test coverage in three years — by investing in automation infrastructure rather than headcount
The six operating principles behind Spin.AI's engineering culture — what they look like in practice, not on a slide deck
Lessons from a third acquisition — why the technical plan is the easy part and the human side is what determines success
Implementing a three-layer encryption architecture for secure cloud data storage
Implementing agile methodology elements in a Bank
Automating IT service operations in a Bank