Halvor William Sanden
All articles

Things that got done

The key takeaway for me in Getting Things Done was getting the things out of my head. For a few years now I have put all ideas, tasks and projects into my task system instead. It increases the chance of doing the things and frees up mental resources. Great for planning, but not for reviewing. At best it can show you what's done, but not the result of it.

Being obsessed with productivity while/and learning new skills, I rarely spend time on what's done. Future tasks are much more interesting. While I was venting my frustration to a colleague about all the things I wanted to learn, she recommended that I should start by writing down the things I have learnt. As Julia Evans does – sharing the knowledge she has gained, without telling people that her way is the only way.

Time spent writing is time not spent learning. But it will put things in perspective and probably lower the frustration about what I have not done yet. I have realised I don't start at zero every time I finish a task. I build on what I know and have done. Even when I start learning a new programming language.

I'm writing to be reminded what's done, what I once didn't know and the progress I've made. To be aware that things require time, and that it's OK to slow down.

Gained knowledge

UX/UI

Programming

Tools and productivity