|
|
|
|
|
by nosignal
5233 days ago
|
|
Interesting you mention this; I've recently started a new job which requires me to learn a whole new skillset (web programming with JavaScript). I've been a developer of desktop apps for a while so programming isn't new, but the language and the paradigms (async? wtf?) are challenging. This is in contrast to my early memories of "web programming" aka making a static Geocities site with notepad and wondering why everyone was so excited about the web when it was this easy to make a web page... turns out it's not that easy anymore. The point being that it really is in those moments of confusion and frustration - where you try something and it doesn't work, or you realise you don't understand how to do what you want to do, especially when you think what you're doing is supposed to be easy - where distraction comes in and you go off track. I've managed to realise that and am glad I'm not alone. The next step - actually doing something about it - is a little harder (hence why I'm on HN right now...!). |
|
This morning I followed the workflow in the OP, and it really improved my performance. I set a timer for an hour, really put work into understanding everything, and when I was done I took a 35 minute break (it is a Sunday). It was rewarding and productive; I'm going to keep this behavior up. Thanks Jiri