Taro Logo
1

How to Time Audit High Leverage Tasks - Which Part of the Stack to Focus On Most?

Profile picture
Senior Software Engineer at Taro Community2 days ago

I left a startup where I suffered from burnout about 1.5 years ago and am now finally back in a cadence coding everyday and I feel like I was so rusty (on web dev), the time I 'took a break' from paid professional work, I spent a lot more time on AI and iOS development.

What advice do you have for someone who wants to avoid burnout, wants to take breaks, but has a tendency to overwork and switch between different tech stacks?

How do you also differentiate where to spend your time?

Time audit

  • Rest
    • Even though I have taken this step to really look closely at where my time is going (using trackers and time estimation tools like Toggl, Rize, Sunsama, planners, Kanban, Goblin tools etc.), I feel like my biggest lag is sometimes oddly, is rest and doing the boring/mundane things you have to do (overhead tasks from the LNO framework) even though when I take it, it actually is the best thing to get me unblocked (from debugging code) etc.
  • High Leverage Tasks - Which Part of the Stack to Focus On Most?
    • For example, I was able to track my time and differentiate between real L (High Leverage) work vs. O - overhead work.
    • I've tried to ruthlessly track my time totaling at least 40 hours a week and found, it still did not feel enough time to get everything I needed to do done (mostly because I found I spent way too much time on dev admin, debugging, or explaining context to an AI which left me frustrated wasting time vs doing 'real work' on the logic). This has happened - the AI piece failing for me, too many times, that I almost want to avoid it completely outside of writing code snippets I already know how to do, and only generate answers from GPT, Grok (Cursor sometimes even when I merge changes and Git, some things get lost and I feel like I end up with a lot of bloat, having to debug harder, or things break and I need to start a project over completely).
    • When switching between stacks (that I do need to do), how do I differentiate between high leverage tasks (web dev doesn't pay me directly to pay the bills, but still necessary vs. the work I spend more time on AI, iOS development etc.)? Or do I just drop a stack entirely so that I'm more productive and not burnt out? What tasks also that is defined as "rest" or non-technical overhead, should I drop so I don't burnout?
25
1

Discussion

(1 comment)
  • 3
    Profile picture
    Coaching Managers & Senior ICs | Ex-Meta, Amazon
    2 days ago

    Burnout is not about doing too much of something.

    Burnout is about not doing enough of what empowers you.

    If your goal is to avoid burnout, you should track what activities empower you versus what drains you.

    Start simple. Pick one area of your life and track just this empowering/draining dynamic for a few weeks. Build your intuition first.

    Once you can clearly feel the difference between what gives you energy and what steals it, you'll naturally start gravitating toward the empowering activities.

    Track just one thing at a time. Do just one thing at a time. Multi-tasking is the silent productivity killer.