Hacker News new | ask | show | jobs
by johnchristopher 617 days ago
> I live by this principle: If it takes you more than 30 seconds to test a change, you're going to have a huge productivity drain.

> That means writing a test should be easy and running it should be fast (including any compilation steps). As soon as something takes more than 30 seconds, you've lost a lot of people. They've switched tabs. They're on HN or reddit or they've pulled out their phone.

And here I am, compiling tailwind CSS on a blade based template consisting of hundreds of partials. ~30 seconds then refresh. FML.