The build step helps Node.js/npm run in the browser, optimize end-user performance, etc. But long build times limit productivity. With modern tooling, do we still need a build step?

nikitonsky: There’s no reason to give disabled buttons different styles

Portrait Monument of women’s suffrage pioneers, Capitol Rotunda, Washington, DC (© Andrew Harrer/Bloomberg/Getty Images)

nikitonsky: How do you want to verify your identity? I choose email. And start monitoring my inbox for the code.

Atrani, Amalfi Coast, Italy (© Amazing Aerial/Shutterstock)

nikitonsky: This tag UI is optimized for wrong thing: excluding instead of including.

Polar bears asleep in Canada (© David Pike/Minden Pictures)

Suspension bridge in Tambopata National Reserve, Amazon Basin, Peru (© Pere Rubi/Getty Images)

Profiling is the nice, cozy, and lazy way to efficiency. There’s something neat about avoiding optimization and having the numbers to prove it relative to an initial baseline. In PHP there’s Xdebug and KCachegrind and I recently saw php-spx in my feeds. A profiler in any language environment with snapshots of performance over time is just — well nice. The terribad situation is not understanding exactly how something became slow. It might be too late then.

Hoodoos at Bryce Canyon National Park, Utah (© Piriya Photography/Getty Images)