Change of plan: Learning Django instead of Ruby on Rails
I mentioned previously on this blog that I was going to start learning Ruby on Rails. I’d been a bit busy since then so haven’t had time to get started, but in-between now and then I’ve had multiple recommendations (both on the web and from people in person) that I should start off learning Python and the Django framework instead.
I don’t want this to turn into a RoR vs. Django discussion, but just so people are aware, for the following reasons I’ve decided to change course and learn Python and then the Django framework.
- If I know people face-to-face who know the language I’m in a lot better position to get help if I’m stuck (provided they don’t get sick of me asking).
- My boss recommended it which could possibly mean I can spend some time at work learning it (can’t beat getting paid to learn in work time)!
- While it seems both communities are pretty vibrant at the moment, more people know how to code in Python than Ruby (Python has been around for almost 2 decades longer than Ruby has). This means they’ll be a wider group of people online who can answer my annoying beginner questions (Nai Chng mentions in this article that there are far more Python questions being asked on Stackoverflow than Ruby questions).
- With all the random coincidences of being recommended Django over Rails, it just seems like I’m being led towards the Django framework!
- There’s no reason why I can’t switch again and go back to learning Ruby on Rails if need be.
I’ll put up periodic updates on my learning progress and hope to post a link to my first web app in a couple of months or so.
P.S. Please don’t start a Django vs. Rails argument!
Post a Comment