After finishing their Ruby course and being thoroughly impressed by the structure, the explanations and the overall approach to simplifying Ruby, I signed up for their Rails course and the Blocks and Iterators course. Just started Rails, it's a lesson you don't rush, so taking it one lesson a day. The reason it should be taken slowly is, like with their Ruby course, there are parallel projects happening while learning. That is, they teach using one app, and ask you to do another app using similar methods, so you need time to digest the information and apply it to two projects. If you have an idea for another app, you can start off on that as well. 
Meanwhile, I'm on their Blocks and Iterators course, which again deconstructs the topic beautifully with interactive, engaging diagrams/animation drawings. I take a screen shot of these drawings for future reference, like a ready reckoner of sorts.
Again,I keep wondering how did I miss this course? I remember seeing it while searching for online Ruby courses when I was caught by the coding bug, but for some reason didn't sign up. I am on Treehouse, Udemy and Tealeaf for Ruby, Rails and other courses but I strongly recommend Pragmatic Studios as the first step. I've also started re-taking the Ruby course, as a refresher, to relook at the concepts and see how I can apply them to say, a problem on Tealeaf. 

I just finished the Pragmatic Studio's Ruby course. They give you a timetable which lays down a one month long plan to take the course but I finished it way ahead. Because it was so simply and beautifully explained I didn't want to stop at just doing one segment a day. 
Mike and Nicole have an excellent way of teaching a complicated language to beginners. First, the diagrams. Important aspects of the language are explained with simple diagrams that visually deconstruct the point, making it easy for you to understand the concept. If you want, you can take screenshot for future reference.
Second, the tete-e-tete between Mike and Nicole. They've mastered the art of two people teaching a lesson at the same time which is a difficult thing to do (there's a Udemy course on a different subject where the teachers of that course try that but doesn't work). Here, Nichole and Mike take turns at asking the relevant questions and raising important points and answer them. 
Three, the whole layout of the course, from strings and numbers to coding three apps. They code a movie app while you are asked to do a game app while there's a bonus coding opportunity for a crowdfunding app using the principles taught in the course. 
The TDD segments are a bit tough, they are more like your afternoon math classes, a pain but necessary. I skimmed over the TDD (Test Driven Development) sections but will have to go back and learn them. In fact, I've already re-started the course as practice is essential in learning anything new.
Towards the end, a couple of points tend to get rushed but that's nothing big. I've signed up for their Rails course and am going to take up their Blocks and Iterators course today. 
I can say in all honesty that if you are a beginner or coding enthusiast looking for your foray in Ruby, this must be your first stop. 

After signing up for Tealeaf Academy's Ruby course, I managed to solve two of the problems, the calculator challenge and the Rock, Paper, Scissors project. They worked too which was encourag_ing and satisfying. Then came the tough parts: Tic Tac Toe and Blackjack. I got the higher language or pseudo logic part quite right (you are encouraged to use English to write down the solution, and introducing code to convert the steps into a working programme) but the problem was in understanding what code to write to translate the pseudo-code into a working one. I am an author and a freelance writer. Logical thinking is as far away from me as saving for a rainy day is to a bachelor on his first salary. This knowledge helped me from smashing my new Mac and throttling the duck.
Did I tell you about the duck? In proamming circles, apparently, they have this method whereby you are supposed to talk to a rubber duck. You tell him your problem, what's keeping you from writing a working code, lying down on a counch while the duck takes notes, yawns, looks at the watch and says, We'll meet next week, meanwhile remember what we talked about today', and charges you $80 a session. 
It's called Rubber Duck Debugging. This, they say, helps. While I see the logic behind talking out your problem loud, I fail to see how a duck can prevent himself from serious threats to his life from frustrated programmers, most of whom are rookies like me. There were times I wanted to beat the crap out of the duck, like Happy Gilmore. That'll only end up in a trail of dead ducks, so to speak. So I took the Codecademy course and finished it in a day and half. Must say it was quite informative for a free course.Finished a couple of Ruby modules on Treehouse. Still, no clue about how to code the blackjack game. So I looked at the solution and did the TicTacToe and am currently doing the Blackjack game. The instructors say you must make some serious attempts to try and code before going to the solutions videos which makes me a trier at least.
The thing is, some of the steps don't even occur to me. I'm sure this is the case if you come from a non-coding background. I've only got the coding bug a few months ago. While trawling the Net, I stumbled onto the Pragmatic Studio again, and this time decided to give it a shot. They were having a discount on their 9th anniversary, and it was affordable, so signed up for their Ruby course, and finished 15% as of now. I like what I see there, like the teachers, and the way they've laid out the programme. It feels good. Progress report to continue, till next time, happy coding, and spare the duck.