The Spreadsheet That Beat Our Churn Model
We spent six weeks on a gradient-boosted churn predictor. A three-column spreadsheet from the support lead did better.
ML engineer in Seattle building practical AI products. Skeptical of hype, excited by results.
We spent six weeks on a gradient-boosted churn predictor. A three-column spreadsheet from the support lead did better.
Why a single mean hides the story in most business data, and three simple alternatives that lead to better decisions.
The AI features that survive contact with real users are rarely the flashy ones. Here is why I start with the dull jobs.
Clicking around in a playground is not testing. A small, honest evaluation set will tell you more than a week of demos.
Most failed ML projects fail before the first line of training code. These questions catch the problems early.
Large model costs creep up quietly. A few unglamorous changes brought ours down sharply while quality held steady.
I audited the view logs of a dashboard I was proud of. The results were humbling, and they changed how I build reports.
A checklist born from projects that went wrong, so that the next analysis starts from understanding instead of assumptions.
You don't need a fancy platform to test prompt changes. A list of real examples and a tiny script got me most of the way there.