David (@hellodavidryan)
Coding is a culture of blurters. This can yield fast decisions, but it penalizes people who need to quietly compose their thoughts, rewarding fast-twitch thinkers who harrumph efficiently. Programmer job interviews, which often include abstract and meaningless questions that must be answered immediately on a whiteboard, typify this culture. Regular... See more
Paul Ford • Paul Ford: What Is Code? | Bloomberg
offices have become interruption factories. A busy office is like a food processor—it chops your day into tiny bits.
Jason Fried • Remote
You should protect your team’s “deep work” at all costs. Traditional work environments optimize for rapid-fire communication. Meetings, Slack, text messages, and stand-ups are examples. Levels thinks these defaults are disastrous and reduce the amount of “deep work” its team can do. It does everything possible to protect this time.
readthegeneralist.com • Levels: A Cultural Anomaly | the Generalist
Software entrepreneur Ray Ozzie has a specific technique for handling potential interruptions — the four-hour rule. When he’s working on a product, he never starts unless he has at least four uninterrupted hours to focus on it. Fractured blocks of time, he discovered, result in more bugs, which later require fixing.
Shane Parrish • Maker vs. Manager: How Your Schedule Can Make or Break You
Mythical Man-Month, Anniversary Edition, The: Essays On Software Engineering
amazon.comInterruption is the enemy of productivity