GeezerVison

If you’ve ever built a tooltip, a footnote, or a popover then you’ve written some version of this: const rect = trigger.getBoundingClientRect(); tooltip.style.top = `${rect.bottom + 8}px`; tooltip.style.left = `${rect.left}px`; Looks fine, until the window resizes. Or the page scrolls. Or the tooltip lands near the bottom of the viewport...

For a few years I destructured almost everything. Objects, props, parameters, return values. If there was an object, I destructured it. It wasn’t a conscious decision anymore, it was just what modern JavaScript looked like. I still use destructuring, but it’s not an automatic go-to for me now. Mainly because...

There’s a pattern in JavaScript codebases that quietly spreads complexity. 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 async now can...