Jiteshkumawatjpr·Nov 2Reading Git History Like Tree RingsWhen we acquired the smaller company last year, I was handed their codebase — fifteen years old, a monolith with a settlement of services…
Jiteshkumawatjpr·Nov 2The Feature Flag That Outlived the Feature, the Team, and the StrategyThis is a biography. The subject is a boolean.
Jiteshkumawatjpr·Oct 31The Bug That Took Three Weeks and One Shower to SolveThe ticket was titled “Report totals occasionally wrong (small amounts),” and I want you to appreciate every word of that title, because…A response icon2A response icon2
Jiteshkumawatjpr·Oct 26Shadow IT: the Spreadsheet Secretly Running the CompanyWe found it during the migration audit — the one I’ve written about, the weekend that became a quarter, the census of everything secretly…
Jiteshkumawatjpr·Oct 26Why I Read Other People's Config Files for FunWhen I join a new codebase — a new team, a new company, the acquired system nobody explains properly — I don’t start with the README, and I…
Jiteshkumawatjpr·Oct 24The Migration That Was Supposed to Take a Weekend — It Took a QuarterThe plan fit on one page, and I want that detail up front because the one-page plan is the first symptom of the disease this essay is…
Jiteshkumawatjpr·Oct 22Side Projects: My Graveyard and My GardenThe podcast app: 2016, my nights and weekends for most of a year, a genuinely decent piece of work that precisely zero human beings ever…A response icon1A response icon1
Clemence Ayekple·Oct 8Ten Seconds to Take It Back: How We Built Undo SendA button that looks like the simplest feature in the app, and the race condition that made our first version lie to users.
Clemence Ayekple·Oct 7Monday, 6:00 AM: The Streak Counter That Melted Our DatabaseHow a habit-tracking app went from 40,000 to 1 million users, and why the fix for our worst bottleneck was to stop computing a number.
Clemence Ayekple·Oct 6Twenty-Seven Knocks: How Our Own Retry Logic DDoSed the Payments ServiceAct I: The Slowdown
