Deep Work is what Why Programmers Work at Night should have been: an insightful masterpiece that tells you how to get shit done when everyone’s grabbing for your attention.
“OMAIGOD YASS” pretty much sums up my reaction to everything Cal Newport said in the book.
Ignore email so you can focus on things that matter? YASSSS.
Get off the internets so you can focus on things you enjoy? YASSS.
Block that addictive shit if you have to? OMAIGOD YASSS.
Train people that you’re flakey in communication and never to expect a prompt reply? YASSS.
Batch meetings into chunks and avoid as many as you can in the first place? YAS!
Schedule long swathes of uninterrupted time, and lock yourself in a cabin if you have to? OMAIGOD YES PLEASE.
Say No to as many opportunities as you can because they’re a distraction from what you really want to do? YES!
Schedule every last moment of your time so you always have a game plan? Yes, great idea, but I prefer routines because I’m bad at scheduling.
Take five minutes at the start of the day and at its end to go over your priorities and close any running mental loops? OMAIGOD YAS.
Ask your boss, “Is my job to Do The Work or to be available to coworkers’ whims”? I’ve been meaning to, but I’m afraid of the answer 😀
When inspiration strikes, clear your schedule, focus on that shit. Don’t let it go. OMAIGOD YASS
Schedule regular time to reflect and to think without distraction? FUCK YES (this is why I run)
Basically, it’s an amazing book, and I cannot do it justice. I listened to it as an audiobooks and now I want to buy like fifty copies and give them to everyone I know. Maaaybe I’ll do that but probably not because that would be expensive 🙂
Outside the practical advice he gives on how to do these things that he suggests you should do, I enjoyed the results. The guy went from publishing 2 academic papers per year as a freeloading student to publishing 9 academic papers and writing Deep Work while competing for tenure. All in one year.
Holy shit, dude.
He does admit that it was too tiring and he’s going to chillax a little. Maybe publish only 8 papers while writing another book. 😀
I want to say there’s something I don’t like about the book, but there isn’t. The whole thing was great. You should read it.
Learned something new? Want to improve your skills?
Join over 10,000 engineers just like you already improving their skills!
Here's how it works 👇
PS: You should also follow me on twitter 👉 here.
It's where I go to shoot the shit about programming.