Re:What should I learn next as a programmer?
by jasim on Monday February 15, 2016 @09:28AM
(#11103526)
Thanks for this response. Completely agree that we need to build things that give us quick-wins. Writing a quick script that does something convenient illuminates the joy of programming like no other.
My point was of a more general nature, for those of us who want to make a long-term career out of programming, and keep getting better at it. A lot of us (myself included) get stuck re-building simple stuff in a newfangled technology every few months and mistake that for progress. If we are to ever get to a place where we have the confidence to build larger and more complex things, we have to try making them, instead of being slaves to the latest project with the most Github stars. It won't be easy, but that is the point of deliberate practice - do something that is slightly beyond our reach and slowly push the bar.
For people learning general programming...they should build something that is useful to them, in the very near future. When I had to learn Ruby on Rails for my new job, coming from PHP (and, well, a computer engineering, FWIW)...I learned Ruby quickly by using it to scrape Craigslist for apartment listings to my own CSV files for easier organization. It's a task I could already do in PHP, but now I could reap the benefits of a faster apartment search while learning a new language. As a new programmer, it's also helpful to understand what it means to build for an end user, even if that end-user is you. Even as an experienced programmer, I find it very helpful to do selfish-side-projects...because knowing what I need to have at the end of the day helps me get over the many obstacles I throw in front of myself (e.g. Am I following proper style? Should I refactor this now or later? etc. etc) that usually hinder my enjoyment of programming.