The premise of the article really resonated with me because I've noticed myself doing the same. My shelves are full of books on various programming languages that I read enthusiastically. But how many have I actually built anything nontrivial with? Very few. I find my motivation ebbing away when it comes to sitting down and writing code. I think the hardest part is just getting started, so I'm scheduling time each day to write something. It doesn't have to be fantastic, just something to get me moving forward.
It is quite simple. Do you want to build something? Then go build it.
You notice you lack information while building? Go read it.
Not the other way around.
Unless you want to read for the sake of reading/learning, which is also fine. It improves your general knowledge. But if you want to get something done, then of course, there is no other way except doing it.
But of course, if it is something bigger, than thinking before doing it make sense. Take a pen and paper and make sketches and todo lists - and then implement them.
>It is quite simple. Do you want to build something? Then go build it.
>You notice you lack information while building? Go read it.
>Not the other way around.
>Unless you want to read for the sake of reading/learning, which is also fine. It improves your general knowledge. But if you want to get something done, then of course, there is no other way except doing it.
I have nothing to add except that this is a beautiful comment that sums up my post way better than I could have myself. :)
> I think the hardest part is just getting started, so I'm scheduling time each day to write something. It doesn't have to be fantastic, just something to get me moving forward.
