Burning both ends of the candle night after night, weekend after weekend, has long been part of web design and development culture. Especially in the startup subculture, we pride ourselves on working long hours with little sleep. It’s part of a new generation’s favorite myth—the one where we get in early in a company destined for an enormous IPO, work our little hearts out for a year or two, and end up rich and happy. The truth is rather less glamorous: the way we are working starves our prefrontal cortex, hurting not only our precious health, but also our productivity. Nick Cox shares the science behind the high cost of constant crisis mode, and explains how to strike a better balance.
More from A List Apart
We’re obsessive about collecting input from a wide range of potential users and stakeholders. But with such an onslaught of feedback, there’s always a risk of having your motivation and faith in humanity sucked right out of you. Sometimes, you just need calm critique from the few people who really get you. So which kind of feedback is best? The answer is both.
From the Blog
As a freelancer, I work in a lot of different code repos. Almost every team I work with has different ideas of how code should be organized, maintained, and structured. Now, I’m not here to start a battle about tabs versus spaces or alphabetical order of CSS properties versus organizing in terms of concerns (positioning styles, then element layout styles, then whatever else), because I’m honestly not attached to any one system anymore.
Part of getting comfortable with the command line is making it your own. Small customizations, shortcuts, and time saving techniques become second nature once you spend enough time fiddling around in your terminal. Since Git is my Version Control System of choice (due partially to its incredible popularity via GitHub), I like to spend lots of time optimizing my experience there.