I'm happy to see them going ahead with this. Codelearn has some interesting technology under the hood and deserves a bit more recognition than it seems to have had so far. (Disclaimer: I've had a preview of their platform as I often write about Ruby/Rails stuff.)<p>Another thing to bear in mind is that this almost harks back to how the Rails community was in 2004-2006. A ton of people blogging about the things they'd learnt and found out. Then they became experts, Twitter was born, and not so many people blog "hey, I learnt this about Rails!" anymore.. :-)
Neat idea! We'll be following along as we've found students do better with a bit more structure than this program provides, but there are so many ways of learning it may work well.<p>What I like most is the personal help. It promises not just a video but guidance to the <i>best</i> video based on where the "noob" is located... that's awesome.<p>I would say that "passively by dropping comments to the blog" feels like a low bar (but maybe I'm reading too literally?). The response rates to questions must be prompt – the difference between getting an answer in 30 seconds and 10 minutes is huge for me, and I've been writing software for 15 years. It's only worse for beginners.<p>For our students at Thinkful (<a href="http://www.thinkful.com/" rel="nofollow">http://www.thinkful.com/</a>) getting human contact promptly is key... our students only like banging their heads against the wall for so many minutes before getting demotivated!
I'm a touch sceptical here - while I appreciate a noobs perspective whenever I'm starting something new, I prefer to see something that encourages best practice - a mix of experience through the eyes of a noob would be better in my opinion.
I'm very comfortable using CakePHP. I've built many apps using knockout.js on top of it, extensively used jQuery and AJAX throughout and have used both MySQL and MongoDB to drive the data.<p>For someone like me who is confident in their abilities of another MVC framework, how much of a learning curve is involved transitioning over to ROR (or any other MVC for that matter)? Has anyone switched from say Django, CakePHP or MVC4 over to Rails, or vice versa?
Good idea, questionable execution:<p>* Should have had a female in the group<p>* The first guy isn't "learning to code", he's a programmer learning a new language/framework