Advice

Damit das Tao of Programming nicht verlorengeht, wenn das Original mal verschwindet...

Back when I was managing at Uber, I latched onto a thinking tool that I drilled into the teams I worked with: reach the right outcomes by prioritizing the company first, your team second, and yourself third. This “company, team, self” framework proved a helpful decision-making tool, and at the time I felt it almost always led to the correct decision. It also helped me articulate why I disagreed with some of my peers’ decisions, which violated this hierarchy by placing individual or team preferences over the company’s priorities.

A brief introduction to keeping your body moving as someone who spends a lot of time sitting down.

The great thing about measuring developer productivity is that you can quickly identify the bad programmers. I want to tell you about the worst programmer I know, and why I fought to keep him in the team.

Learning from Entrepreneurs, Rickshaw Drivers and Poker-PlayersThe two founders of WhatsApp applied for a job at Facebook back in 2009, but their applications were rejected. Instead they went on t…

How elite coders outperform the rest

The key is to understand the difference between habits, routines, and rituals, and to design a life where your daily actions allow you to play with the entire spectrum of consciousness.

Patrick Collison, the CEO and co-founder of Stripe, maintains a list of people quickly accomplishing ambitious things together titled Fast. On the page, he talks about The Eiffel Tower (739 days), Boeing 747 (930 days), JavaScript (10 days), Git (17 days), The Empie State Building (410 days), and more. Why do ambitious things sometimes come together so fast? * Right time, right place. Sometimes, groundwork from many disparate threads comes together, making the previously impossible possible.