Lately I’ve found it difficult to get to the next phase in my knowledge as a programmer. After having spent the last year and a half learning to program and building my new startup, my job’s role has mostly transitioned out of programming daily to marketing, sales, and product management. I’m finding myself losing the motivation to get better just for the sake of getting better. Without having clear programming deliverable in my sights, the need to open up a book or take more Treehouse classes has left me for the time being. I don’t consider myself a career long programmer, and I’m having trouble figuring out how much I should learn.
That’s not at all to say that I don’t want to continue to learn more, but I know that I don’t want to be a career developer. When I started I wanted – and I believe I achieved – the ability to be able to prototype ideas. Some might say I cut corners, as I never worried about scaling or learning to write tests. Doing things right is very important to me, so I did write with best practices in mind and kept my code clean.
Lately I feel as if I’ve achieved almost all I want to achieve with programming. One disincentive from keeping focused on programming is that I still think there’s much that I could improve on in other areas, more important aspects of my career as a serial entrepreneur I could and should focus on instead. Josh Long, Managing Editor of Treehouse, asked me if “knowing what I know now, I would learn to program again.” I told him emphatically that I would never trade learning to program for anything, but that I’m not honestly not sure how much farther I want to progress.
I’d love to start a discussion among the readers of this blog about how much you think non-career programmers should learn. Do you believe that I, and others, should continue to dedicate some of my time to learning new concepts, or what? I’m really looking forward to your answers, as it’ll help me figure out what to do next.