/
9 min read
Your Global Scope Is a Disaster (And It's Breaking Production)
After debugging countless production incidents caused by global namespace collisions, I've learned that scope discipline isn't optional—it's survival.
Read article
Start typing to search the site
After debugging countless production incidents caused by global namespace collisions, I've learned that scope discipline isn't optional—it's survival.
After years of defending preprocessors, I've watched native CSS absorb every feature that justified Sass—and do it better.
After years of chasing JavaScript frameworks, I've learned that boring, mature technology ships products while trendy stacks ship complexity.
Why I stopped reaching for SPA frameworks first and started shipping HTML-over-the-wire for most projects
The shift from writing code to orchestrating systems is happening faster than you think
Why every "lightweight, tailored solution" eventually becomes an unmaintained, undocumented mess