Hello! I am a software developer and over the years I found that I am extremely unproductive when it comes to finishing one task and then starting another right away. It is best noticeable when I complete something that took me more than one day and then I am guaranteed to not do anything productive for the rest of the last day(doing something for 3.5 days - unproductive for the half of the last day). Same applies to working on side projects. I am focused when I research one problem, implement it, but I have no willpower to continue to the next problem. This affects my career in a bad way and I am sure I am not unique and there are ways to fight it.
It's like you need to repeatedly and unintentionally expose your mind to information that pertains to the project before you get into the flow of working on it. Just staring at it with no other outlets for activity or inlets of information forces the issue and speeds up how your brain is loaded with necessary information so that solving the problem becomes easy.
So another way to say it is remapping your working memory has a high cost until the previous information naturally falls out and your motivation and desires depend on that. So make it easy to move information into your working memory by making it the only information available. Instead of hackernews/reddit, put up the issue and reqs.
Also, for everyone else saying that you're not a robot, screw that. With the right techniques you can be a robot like the rest of us.
Having the issue to be the only information available is a great advice! Thank you sir
Staring my personal backlog, my mind starts to imagine the possible solutions, alternatives, and after some time depending on the complexity of the task at hand, I start working autonomously, fully motivated. If I even take a half minute break from staring for HN/Reddit/Email before I begin working, I need to restart the cycle. Knowing the weaknesses of my mind really helps.
Maybe take a 2 min walk or go to the restroom instead of switching to a mind-distraction task.
That said, task switching is a practical reality, so coping strategies are important, too.
For help with that, check out Cal Newport's "Deep Work: Rules for Focused Success in a Distracted World" (https://www.amazon.com/Deep-Work-Focused-Success-Distracted/...). Full disclosure: He and I share a literary agent.
For longer, 2-3 day tasks, I completely log off and don't connect to the world until it's done. This means avoiding any network tool through the evenings and mornings until the stretch is over. Easier said than done. Some of my family and friends think I'm weird or get frustrated by my inaccessibility. But they get over it.
After a 2-3 day deep binge like the OP I also face challenges moving from one discipline (say programming) to another (a marketing video). One tool I use is yoga. For a while I had a daily meditation habit going but it's been replaced with 2-3x / week hot yoga. I find it has a way of cleansing my mind and energizing me for the next thing. I also go on fat bike rides to unlock the power nature's constant stimuli has on your mind as Cal talks about in the book.
I use a kitchen timer, too, which has minutes and seconds (e.g., digital).
Some tasks with too much inertia/resistence I ask: "Can I work on this for 5 minutes? 2 minutes? 15 seconds?"
That will build momentum and show that it's often not as hard as it seems when you're on the other side of history.
If you're interested in improving your productivity by simplifying your work, it is a good book.
But like all self-help books its effect wears off over time.
Keep in mind that Cal Newport is an academic at MIT. He has autonomy, he works in a field he loves etc. For other people his point of view is valuable, but his advice IMHO is not that easy to follow. You may need to improvise and find your own way.
Dead Comment
I keep notes of what I’m doing and what I’ve learned as I do my work. I keep a separate note document for each task/project. I do this in One Note so that it syncs to my phone and I can attach clean processed images of whiteboards. But I used to do this with plain text files and vi. Either way I indent sub tasks.
In this document I break out and list all the things I’m going to do, with either a checkbox in one note or a [ ] if I’m using text. When I have done the task I change it to [x], and when I start the task I change it to [.]
When I get interrupted, I switch to the other file and keep track of what I’m doing there. When I switch back to the original task I scan the file and look for the [.] and that’s where I need to resume working. This step is crucial and helps me avoid the situation where it takes me 20 minutes to re-aclimate and remember what I need to do next.
Each day I do work I make an entry in the text file that tells me things below this line are in this date. As I complete projects I put the documents into a history folder keyed by date. This also lets me go back and see what I was doing on a particular date. This helps me avoid that “blank stare” feeling I get when management inevitably asks me why the task took so long or what the hell I’ve been doing all week. I’m not a slacker, I just need systems to help me overcome my memory and attention deficiencies.
You mentioned having trouble finding the willpower to go back and resume a project. A big cause of procrastination is not having faith that you’ll be productive with the project in the time you have available to work. Having the work broken down into achievable measurable chunks is key to fixing this problem. And that’s the major part of what this note system is all about fixing.
E.g. rather than "Research using Foobar in the next mobile project", the first task is "Write a Foobar Hello World". Rather than "Write proposal for project X", the first task is "Draw logical architecture diagram for X".
I find the inertia against getting started is a lot less when the task is a five-minute, self-contained unit. It also helps task switch because you don't treat them like links in an unbroken chain of tasks, but individual units.
Only downside: you have to spend some work up front slicing your projects into smaller units. It's kind of analogous to story slicing...
Trick 1: Improve your cardio health.
Generally a balanced meal gives you a lot of willpower. Cardio exercise specifically seems to improve recover rate a lot, not just physical but mental.
Trick 2: Develop a trigger.
Find a routine, a kind of trigger that puts you in the mood to work. There's a trigger already built into all of us, a moment of serenity that we see as taking a break.
This is the kind of productive thing that makes you work late at night, or weekends, or continue nonstop for 20 hours straight. It might not even be work - it could be a game, book, or some tedious hobby like woodworking.
I use Linkin Park songs because my productive moments were making games in school. I also saw Chester Bennington as a role model, because of his emotional drive and his success as a VC. Some of his songs also resonate with me on a spiritual level. His suicide got to me, and I find his songs as a sudden reminder of why I do what I do.
It doesn't have to be a song. It can be something like flipping a coin between your fingers, taking a deep breath, pumping your fist, a 5 minute meditation. The more portable the better - you don't want it to be something like eating a can of spinach.
You also need to associate the trigger with positive things. One of my mistakes was poisoning an old trigger with death marches.
Whenever you hit a moment of pure joy, try to associate that with your trigger. It could be the completion of a tough patch of work, playing with kids, breathing fresh morning air.
There's a lot of principles that go into this, but I would recommend the books The Power of Habit and The Art of Learning if you want more details.
- Don't do large tasks. Spending more time up-front breaking down a large task into smaller, more-manageable tasks might help. This is something that many engineers struggle with, but there are huge advantages to this kind of discipline that go beyond taming your concentration issues, so this could be valuable in more ways than one.
- As others have said, go for a walk. There's something about activating our peripheral vision and looking from side to side that activates different parts of our brains and makes us more creative. It's even used as a therapeutic technique (EMDR) for dealing with PTSD.
- Find non-project tasks that you can do to fill less productive gaps. Do code reviews, go back to old projects and fill-in additional test coverage, play with some new technology/tool...a lot of teams neglect hygiene tasks anyways, so you may benefit from acknowledging your weaknesses and trying to make the best of it.
- Offer to pair with engineers for the rest of the day. If you know you can't be productive for that time period on your own, perhaps you can add value as an extra set of eyes.
- Don't fight it, embrace it. There's a mantra in startups to embrace your limitations. As engineers, we're not nearly as good at problem solving when we have no constraints. But when there's some real-world concern that points us in a particular direction, it's often easier to find the right solution. So look at this the same way. Don't beat yourself up about it. Be kind to yourself and accept that it's just a reality. Once you do that, put on your engineering hat and think of how best to deal with an unideal situation. Because situations are never ideal in the real world.
- Learn to meditate, particularly anapana meditation where you train yourself to concentrate on nothing but the breath. Concentration is a skill that can be practiced. It may be that you're not able to concentrate on something new because you're still concentrating on your previous task. Learning to clear your mind may help you move on to something new after a short break.
Best of luck!