Four Thousand Weeks Review: Ending the Productivity Obsession

I once spent exactly 47 hours in a single week just to write a script that automated tagging tasks on Notion. By the time the script ran perfectly, I realized I had zero energy left to actually do those tasks.

That’s when I turned to Four Thousand Weeks by Oliver Burkeman.

⏳ 4000 Weeks and the Illusion of Control

The average human lifespan is about 80 years. Converted into weeks, we have roughly 4,000. That number is startlingly short.

Burkeman points out a paradox: the more we try to manage our time, the more we feel its scarcity. We tech folks are obsessed with “inbox zero,” optimizing workflows, and using AI like Claude Sonnet 4.6 to code faster. But the truth is, when you work faster, people simply assign you more work.

Completing everything is an illusion. You will never get it all done.

❌ Productivity is a Trap

The biggest highlight of the book is how it exposes the self-help industry.

We are taught that if we find the right method, the right tool, we will master our lives. (I know this sounds pessimistic, but trust me, letting go of that idea is actually liberating). The more you cram into a day, the more the quality of your attention degrades.

Burkeman advises us to proactively choose what to “fail” at. By accepting that there are projects you will never touch, you can finally focus on what is right in front of you.

⚠️ When Philosophy Collides with Jira

This is why this book only received a 3.0 from me.

Burkeman’s philosophy is great, but it’s incredibly difficult to apply for a software engineer in the middle of a sprint. You can’t exactly tell your Project Manager: “I’ve decided to embrace the finitude of human existence, so I won’t be finishing this ticket.” The tech environment has hard deadlines and pressures that “letting go” doesn’t immediately solve.

It’s like trying to reshape your Sự nghiệp Dev sau 30: Cú lừa của lộ trình thăng tiến — you need practical action, not just psychological comfort. The book is completely missing a concrete framework. It’s a long philosophical essay, not a handbook.

📊 GTD vs. Four Thousand Weeks

To see the difference clearly, look at how this book contrasts with traditional Getting Things Done (GTD):

Criteria	Getting Things Done (Traditional)	Four Thousand Weeks	Practical Notes
Goal	Clear the inbox, do everything	Accept the inbox is always full	You need a mix of both to survive.
Method	Break down tasks, assign context	Limit Work In Progress (WIP)	Kanban’s WIP limits fit this idea well.
Mindset	Maximum optimization	Accept missing out (JOMO)	Hard to do when your boss is pushing.

🛠️ How to “Hack” This Philosophy into Tech Work

Despite the lack of tools, we can still extract a few practical techniques from the author’s theory.

1. Hard-cap your Work In Progress (WIP)

Don’t list 20 things to do today. Pick exactly the 3 most important ones. If a 4th task appears, it has to wait until one of those 3 is completed.

2. Clearly define the boundaries of “failure”

Choose ahead of time which areas you are okay with neglecting. For example: this week I’m focusing on deploying the GPT-5.2 integration feature, so I accept that my email responses will be delayed. I currently have 113 unread emails, and I am perfectly fine with that.

— Get book summaries and practical Notion templates for free in my resource library.

3. Stop confusing tools with the goal

Don’t waste time setting up complex systems you don’t actually need. Sometimes, a plain text file is more effective. This is exactly like the 5 Sai Lầm Trí Mạng Khi Dùng AI Trong Obsidian that techies often make: trying to turn the tool into the solution instead of using it to support thinking.

❓ FAQ

Should I buy this book?

Yes, if you are experiencing burnout and feeling guilty for not working enough. No, if you are looking for a specific task management system like Kanban or Time-blocking.

Will it help me code faster?

Absolutely not. In fact, it advises you to slow down. If you want to speed up your coding with AI, read my post Windsurf IDE: Đừng Vội Bỏ Cursor Lúc Này instead.

How long does it take to read?

It’s quite short; you can finish it in about 2-3 evenings. However, the second half of the book gets a bit repetitive and wanders from the points made in the first half.

🎯 Conclusion

Four Thousand Weeks isn’t a panacea for tech workers. It’s quite weak at providing clear action steps.

However, its true value lies in shattering our obsession with absolute control over time. I still use task management tools, I still optimize servers, but I’ve stopped beating myself up every time my to-do list remains unfinished at the end of the day. Finitude isn’t a system bug—it’s a feature of life.