https:/
Every JavaScript project has a collection of config files to control the behavior of tools like Prettier, ESLint, Typescript, Vite, Tailwind, Post CSS, and more. Let's take a comprehensive tour of the web development tooling ecosystem.
Is it really fun, or just frustrating?
I wish Jeff didn't say "CSS by itself is too painful", though… 😔
Design Happens Between Breakpoints
💯
Why are software development task estimations regularly off by a factor of 2-3?
I have never found a better analogy to show the systematic difficulty in providing software estimates, which are frequently wrong:
Semantic Versioning Will Not Save You
As a maintainer of several open source projects (both in Ruby and JavaScript), I agree with everything Hynek says about the difficulty for a maintainer to define versions and give a hint about potential compatibility issues.
Fulfilling the promise of CI/CD
This may surprise you, but continuous deployment is far and away the easiest way to write, ship, and run code in production. This is the counterintuitive truth about software: making lots of little changes swiftly is infinitely easier than making a few bulky changes slowly.
Un petit débat sur la compatibilité cross-browser dans l'état de l'art du développement de sites Web
Adrien « Voulf » Leygues lance un petit débat sur l'état de l'art du développement de sites Web focalisé sur la compatibilité cross-browser. Voici mon point de vue.
Jeff Delaney 
Jason Grigsby
Michael Wolfe
Hynek Schlawack
Charity Majors