There’s a pattern in JavaScript codebases that quietly spreads complexity through entire applications. You’ve probably seen something like this: async function getConfig() { return defaultConfig; } At first glance, this barely feels like a decision. Maybe one day getConfig() will fetch something remotely. Maybe it’ll hit IndexedDB later. Making it...

Every so often I open a PR and see something like this: deployFeature(flag, true, false, true); I run into it more often than I’d like. Not because it’s complicated. Just because I have no idea what I’m looking at. So I click into the function definition, scroll a bit, lose...

I used to write a lot of JavaScript like this: const result = users .filter(user => user.active) .map(user => user.name) .sort() .slice(0, 5); Nothing here is wrong. I wrote code like this all the time. But this is exactly the kind of thing that feels fine at first, then slowly...