Book Review: Four Thousand Weeks: Time Management for Mortals

Four Thousand Weeks: Time Management for Mortals

(link) by Oliver Burkeman

This book is a shorter one that I binge listened to while on a road trip. It isn’t your typical productivity book where they tell you how to “hack” your life to find every second that should be spent “doing” things. I found the message in it to be one that gave me a good reminder that life is short and we need to be careful about where and how we spend our time. The same applies to the work we do. We only give our employer so many hours of the day, it is our responsibility to make sure that we spend those hours wisely so that the value they gain is worth it.

“what you pay attention to will define, for you, what reality is.”

“Productivity is a trap. Becoming more efficient just makes you more rushed, and trying to clear the decks simply makes them fill up again faster. Nobody in the history of humanity has ever achieved “work-life balance,” whatever that might be, and you certainly won’t get there by copying the “six things successful people do before 7:00 a.m.” The day will never arrive when you finally have everything under control—when the flood of emails has been contained; when your to-do lists have stopped getting longer; when you’re meeting all your obligations at work and in your home life; when nobody’s angry with you for missing a deadline or dropping the ball; and when the fully optimized person you’ve become can turn, at long last, to the things life is really supposed to be about. Let’s start by admitting defeat: none of this is ever going to happen. But you know what? That’s excellent news.”

“The day will never arrive when you finally have everything under control—when the flood of emails has been contained; when your to-do lists have stopped getting longer; when you’re meeting all your obligations at work and in your home life; when nobody’s angry with you for missing a deadline or dropping the ball; and when the fully optimized person you’ve become can turn, at long last, to the things life is really supposed to be about. Let’s start by admitting defeat: none of this is ever going to happen.”

“The real measure of any time management technique is whether or not it helps you neglect the right things.”

Key Thoughts

  • Accepting the shortness of life is both a positive and negative realization. Spending too much time pondering it can bring anxiety and worry. Not spending time pondering it allows for wasting too much of it and not appreciating it.
  • Todays world is filled with tools, gadgets, and things to make our lives easier. But do they? What do we gain by using the dishwasher over hand washing if we are just going to spend that time doom scrolling through social media apps. But spending that time being “productive” is just as bad, it brings on stress and other issues.
  • List all the things you want to do with your life. Choose the top 5. Accept that you will probably never do any of the bottom 15. Take those off your list completely rather than sitting and worrying about never accomplishing them.
  • Becoming better at procrastinating is a concept that I never considered as a goal in life. But they had a great point. Making sure to drop the things that aren’t bringing joy and value to you and your life is something that is worth doing.
  • Working remotely takes away some of the human interaction that is necessary
  • Questions to ponder
    1. Where in your life or your work are you currently pursuing comfort, when what’s called for is a little discomfort?
    2. Are you holding yourself to, and judging yourself by, standards of productivity or performance that are impossible to meet?
    3. In what ways have you yet to accept the fact that you are who you are, not the person you think you ought to be
    4. In which areas of life are you still holding back until you feel like you know what you’re doing?
    5. How would you spend your days differently if you didn’t care so much about seeing your actions reach fruition?

A few tools for embracing our finiteness

  1. Adopt a “fixed volume” approach to productivity. Keep two to-do lists, one “open” and one “closed.” The open list is for everything that’s on your plate and will doubtless be nightmarishly long. Fortunately, it’s not your job to tackle it: instead, feed tasks from the open list to the closed one—that is, a list with a fixed number of entries, ten at most. The rule is that you can’t add a new task until one’s completed.
    1. Establish predetermined time boundaries for your daily work. Train yourself to get incrementally better at tolerating that anxiety, by consciously postponing everything you possibly can, except for one thing.
  2. Focus on one big project at a time.
  3. Strategic underachievement—that is, nominating in advance whole areas of life in which you won’t expect excellence of yourself—is that you focus that time and energy more effectively
  4. Focus on what you’ve already completed, not just on what’s left to complete.
  5. Keep a “done list,” which starts empty first thing in the morning, and which you then gradually fill with whatever you accomplish through the day.
  6. Reduce phone distractions as possible—first by removing social media apps, even email if you dare, and then by switching the screen from colour to grayscale. Choose devices with only one purpose, such as the Kindle ereader, on which it’s tedious and awkward to do anything but read
  7. Pay more attention to every moment, however mundane: to find novelty not by doing radically different things but by plunging more deeply into the life you already have. Experience life with twice the usual intensity. When presented with a challenging or boring moment, try deliberately adopting an attitude of curiosity.
  8. Act on the impulse right away, rather than putting it off until later.
  9. Do Nothing” meditation, for which the instructions are to simply set a timer, probably only for five or ten minutes at first; sit down in a chair; and then stop trying to do anything. Nothing is harder to do than nothing.

What kind of Software Engineer am I?

The four wings of a software engineer are:

  1. Product / Business
  2. Design
  3. People
  4. Technical
Four Wings of a Software Engineer ~ blog.robertsimoes.org

Recently a coworker shared this blog post in our departmental “Blogroll” slack channel. It struck a cord with me and helped me to understand some of my struggles with imposter syndrome over the years.

In the article he defines 4 different types of Software Engineers. As I read his descriptions I realized that I have spent my career feeling inferior to other Engineers because I am weakest as a “Technical” engineer. I always knew that my skills lay in other places but always had a hard time defining them, and felt like a failure because I didn’t have the “Technical” skills my coworkers did.

As a fulltime Software Engineer I often struggled with learning new technologies quickly, understanding how all the pieces fit together, determining the best engineering solution for the problem in front of me, and knowing the proper terms for the tasks I undertook. While my code was always solid, I would go into interviews and say things like “I don’t know the correct term, but here is how I solved the problem.” Thankfully I got hired anyway!

After reading his article, I realize that I fall in the “Product/Business” and “People” categories. It explains why my shift to be an Agile Lead to aid other Engineers in building better software feels so right. A few years back I rose up to a Team Lead position and quickly my team became the highest performing in our department, not because I was strong technically, but because I knew who was and cleared their slate so that they could solve our problems. Eventually I was moved into the position of “Agile Delivery Lead” so that I could take what I was doing that was working and apply it across our department. I’m still in that role today and loving it!

Imposter Syndrome is a real thing, and I have spent a good part of my career feeling that way. Finally after 20+ years I have my feet under me and feel like I am contributing to our Engineering department in a valuable way. Thanks Robert for helping me understand.

Agile Delivery Lead

Last November a change was made to the composition of our development teams.  I had been working as a team lead since the previous March and things were going really well.  But a gap in the department was identified and I was asked to change roles to fill it.   My new title became “Software Engineer – Agile Delivery Lead”, yes it is a mouthful but it encompasses what I do.   Almost 6 months later I have settled into my new role and we have been slowly defining what that means for our teams, department, org, and myself.   I’m still working on what my duties entail.   For right now I have identified a list of responsibilities that are on my plate and we prioritized them based on how much I can help by performing each role.  As with anything, it changes constantly.

#1 Team Support:  Keeping the teams moving and the work steadily flowing onto our production systems is the first priority that I have on my plate.  I currently work directly with 2 development teams and keep my ears open for what 3 others are working on.  This includes activities such as Daily Standups, Weekly retrospectives, quarterly retrospectives, team velocity reporting, and managing the “Coming Soon” part of the team backlogs.

#2 Product Manager Support:  Working with the product managers to help to research potential improvements to the systems and start scoping out the work.   Research, reporting, epic/ticket creation, determining order of the work to get done, backup for the team when the PMs are out, and reviewing the work completed.

#3 Senior Software Engineer: Utiliziing my skills as a Sr. SE in the department to help move the platform forward.   Estimating, documentation, cross-training, code reviews, backup for Engineering Leads, architecture, and special projects.

#4 Department support:  Helping upper management with keeping a pulse on the various teams and making sure things are flowing smoothly.  Team velocity reporting, department velocity reporting, process research & implementation, and help to manage engineering needs backlogs.

#5 Personal Projects:  Continue to grow my own skills and knowledge by doing projects that will help the team, department, and company work more smoothly.

Dev Team Lead Resources

Articles

Books

Quote: Team Goals

My mission is to create teams that change the world.

I began this mission as a software developer. I saw in myself and other teams a passion for creating products that people would use and love. I saw that same passion dashed over and over again when the products fell flat. I knew there was more out there.

I have sought for years to find ways of enabling teams and organizations to have a different story. One where the hard work pays off. One where people take pride in a job well done and a product that people love.

I’m a long way off still from saying my mission is accomplished, but I’m here to share what I’ve learned and to help people find that new story.

~ Ryan Latta, LeanAgileUS 2019 bio https://twitter.com/recursivefaults