I encourage you all, you CAN do the things you set yourself up to do them. Procrastination is just not having all the ingredients in the right place at the right time so you can ACT with what is in front of you.
From TFA in GTD methodology, you have the following lists:
> In
> Next actions (probably several – more on that later)
> Waiting for
> Projects
> Some day/maybe
I've only casually read about GTD methodology but I have been really satisfied with some progress I've made with my programming projects by taking a similar approach. This is my "In" list.
* I journal every thought in a markdown file. (I add it to a list by adding a new heading at the bottom of the file and then writing paragraphs or tables or mspaint drawn graphics :-) or draw.io graphics)
* If I have a "Next action", I add a phone alarm or JUST DO IT immediately.
I think my mind is massively parallel and is always processing things like shower thoughts and sleeping on things but procrastination is being put off by things you can't do immediately, that your mind sees no obvious path to JUST DOING IT. Some work is just automatic, intuitive. Other work requires lots of thought and knowledge.
But most of the time, I'm doing one thing at a time, be it thinking what to do next - by adding to the "in" list and processing. And I'm not spidering endlessly into the distance and then being paralyzed by analysis paralysis. I don't do that! Writing things down is thinking. I am always processing the "in" list.
> Projects
My github repositories often start as a Replit and I use the issue tracker on GitHub to add thoughts and break down problems and solutions in issues. Or I add to the README.md.
My main journal acts as my "someday maybe" list.
I was an evening into some programming project and there was a refactoring that I realised that I had to do, but I didn't feel like doing it. I did it anyway and I pushed through it. Then that was extremely satisfying because I got what I wanted by trading effort/willpower for a profitable result.
From TFA in GTD methodology, you have the following lists:
> In
> Next actions (probably several – more on that later)
> Waiting for
> Projects
> Some day/maybe
I've only casually read about GTD methodology but I have been really satisfied with some progress I've made with my programming projects by taking a similar approach. This is my "In" list.
* I journal every thought in a markdown file. (I add it to a list by adding a new heading at the bottom of the file and then writing paragraphs or tables or mspaint drawn graphics :-) or draw.io graphics)
* If I have a "Next action", I add a phone alarm or JUST DO IT immediately.
I think my mind is massively parallel and is always processing things like shower thoughts and sleeping on things but procrastination is being put off by things you can't do immediately, that your mind sees no obvious path to JUST DOING IT. Some work is just automatic, intuitive. Other work requires lots of thought and knowledge.
But most of the time, I'm doing one thing at a time, be it thinking what to do next - by adding to the "in" list and processing. And I'm not spidering endlessly into the distance and then being paralyzed by analysis paralysis. I don't do that! Writing things down is thinking. I am always processing the "in" list.
> Projects
My github repositories often start as a Replit and I use the issue tracker on GitHub to add thoughts and break down problems and solutions in issues. Or I add to the README.md.
My main journal acts as my "someday maybe" list.
I was an evening into some programming project and there was a refactoring that I realised that I had to do, but I didn't feel like doing it. I did it anyway and I pushed through it. Then that was extremely satisfying because I got what I wanted by trading effort/willpower for a profitable result.