My take is that a key part of learning how to program (or anything new, in general) is in the motivation - if your student is just "kicking the tyres" then forcing them to commit $3k or making them digest an entire book is only going to deter them.
Once they're motivated though, they'll usually plow through obstacles that would've stopped them just last week. So give them small wins at first and give them an idea of what it's all about, then ramp up the difficulty once they've figured out what they want to do.
A common "tell" for this I find is that they move from "how does 'x' work" to "I need to do this thing; how do I do that?" combined with doing lots of stuff (They might do it in a weird, non-programmer way, but they'll still be doing it).
Udacity gets you thinking on your own. It teaches you principles then presents a blank screen and says 'now make something that does XYZ'
That's a whole world away from a pre populated page of code where you type between the quote marks.
Going from a blank page to something that works - where the steps, logic and reasoning are all your own - THAT's what makes beginners jump around the room with excitement.
Beginners also often need to be reminded that if you get stuck your job is to stop coding and find out.
Bloomberg LP, Zoho and Infosys all have very good versions of this in-house. Convert a economy major into a developer who knows C,C++,Fortran or Cobol in 4 months.
Zoho does it with high school grads but their process takes like 2 years I think for them to be contributing engineers.
I like the part where they get people to commit to atleast 3 hours. In my model I assumed you would need 8 hours of full commitment per day.
We draw the line at 3 hours and weekends are required, plus you can't be gone more than one week during the 8 weeks. If people can't commit to any of those, we would rather try again with them in the future when their schedule works out better.
I figured out some other interesting business models. Especially applicable in NYC. Email me (in profile) if you want more info.
I think lots of models can work, but we tried what we saw as the holy grail of "we'll deploy on your behalf, build the editor, and structure the guide" model and keeping the user in the browser just doesn't work.
Figuring out a business model that results in a better clientele is an achievement, but we learn how to find good people to teach rather than "how to actually teach people to program" in general. This model dismisses those with a casual "tourist" interest in order to focus on those who are already motivated. Business wise, that's a great idea for Jared, but companies or teachers looking to have a mass impact will need to keep doing their research because many a tourist has turned into a fine developer (and some are finding success in this area with wildly differing models - Treehouse, Code School, Zed Shaw, etc.)