Ask HN: Time coding vs time improving your coding skills?

I'm fairly new to programming; it's been a longtime hobby I'm hoping to turn into a profession.<p>I get really bad analysis paralysis and often find myself poring through books on text editors, design patterns, clean coding etc - at the end of the day I've got a bunch of theory and have built absolutely nothing. Or to the extreme: Perhaps I should learn Haskell and write it in that?<p>conversely, sometimes I'll bash away at the keyboard coding up an idea I've had, not really being mindful of the fact that I'm repeating myself a heck of a lot or doing things horribly inefficiently - and that searching for that python library of vim shortcut would save me half a day.<p>Anyone got any advice about how they approach this? How do you keep decent momentum up, but know when it's time to stop and sharpen your axe?