So, I think I start to understand why I always fail to use Org-mode, or any other software made for the same goal.
Until now, I wanted to use it to track and plan all my tasks. Including tasks I don't want to do but have to. So, every time I used it, it remind me of all the boring stuff I don't want to do. It result as my brain prefer to avoid using it and be focus on something else.
When I was using Org-mode, I finished by being freeze: I don't do the tasks I don't want to, and because of that, I was feeling that I didn't deserve to do what I wanted to. In the end, I was doing nothing because of that.
And I also tried to use Org-mode during period of time where I have a lot of work to do, where mistake was not possible for me. In these times, I can't experiment new things. I need to rely on thing that I have already used and have proven it worked for me, even if it's less efficient than Org-mode.
So, what to do now ?
I start to use Org-mode to track only, no planing. I mark only the tasks I want to do. Like that, I will be very happy to use it.
When I took the habit to use Org-mode, I will start to time my tasks. It will help me with my inability to represent time in my head.
Then I will start to introduce task I don't want to. Maybe with a counter. If I have more than 3 tasks per week, I have the right to push the rest of them to next week.
And finally, I will maybe introduce planing.
But for each step, I will wait to take some habits.
@fox That's an no interesting aspect: unlinking Org from things you don't like to do (dish washing, tax statement, visiting mother in law ... err, just joking).
I also used Org a lot for documentation: In my company, I was the only one on Emacs. And I liked to have docs in the git repository, not in some directory with Word documents. So I wrote the doc in Org and expected (usually) to HTML and (sometimes) to PDF.
I'm a weird guy: I like documenting to some degree.
I happened to program a lot on the embedded devices. There you have lots of ICs attached via i2c, SPI or what not. You have to manage from the bootloader and/or Linux kernel. So you need detection code, driver implementation, tests for all this. And sometimes user facing docs ("how to get the board temperature"). For the first part I used Org's checklist. Already when reading the schematics I made lots of entries of what I needed to implement. And the last part was done org-babel blocks (begin/end example, begin/end shell).
In one larger project (special device made for a mining supplier) I had perhaps 400 check marks. And hundred org-babel blocks. But for my brain this was no chore. Instead I drawed satisfaction out of closing them one after the other.
So this is how I tricked my Neandertal brain :-)
However, I see suck at org-agenda line tasks. I have too few of them to get into any routine.
Add comment