{"id":1031,"date":"2015-10-19T06:18:47","date_gmt":"2015-10-19T10:18:47","guid":{"rendered":"https:\/\/cindypotvin.com\/?p=1031"},"modified":"2016-01-06T20:39:29","modified_gmt":"2016-01-07T01:39:29","slug":"youre-not-learning-too-slowly","status":"publish","type":"post","link":"https:\/\/cindypotvin.com\/youre-not-learning-too-slowly\/","title":{"rendered":"You’re not learning too slowly"},"content":{"rendered":"

Learning a new framework or language always feels slow and sluggish at first. I’m working on learning<\/a> Ruby on Rails right know after a year or two of not learning a new framework and I had also forgotten the feeling. At first, I stumbled at every step on the way and nothing was familiar even if I’ve been programming for the web for many years. Not to help things, Rails is a strongly opinionated framework, so a lot of things are done by convention and not by configuration or by code. It’s a great productivity boost once you know the proper conventions, but it’s hard to deduce all of them at once when getting started. <\/p>\n

\"hourglass\"At first, I had the impression that I was going slower than usual. For a developer with a good grasp of the web and of other frameworks, a few weeks should be enough to get up to speed in a related technology and reach a point where they’ll be able to produce work at a decent pace. Not top cruising speed, but a few months down the line nobody will notice that they were new at it. <\/p>\n

I’ve started two months ago and I’m barely getting there, but the thing is, I’m going at it in my spare time. I realized it was totally normal and that I was not growing soft with some simple mathematics. I’m sure you’ve also had the impression that you were too slow and not as productive that you could be when you started learning a framework for a new project or a new job, but it’s totally normal if you look at the time involved. Here is a ballpark estimate of what you can expect depending on the time you have to learn:<\/p>\n