Google Launches Free Tool To Let You Run Your Own Online Courses
edudemic.com
edudemic.com
However, I don't get a lot of replies if I apply for a job. HR ladies don't care if you're good, only if you check an item on a checklist.
I get by on my own products and on my rep, which is fine, but sometimes I need a gig to pay the bills.
So, my point is, it's great to have all these online courses, seriously, but how is this going to help people get jobs? I can see it helping them make their own job, but some people just want a regular old day job.
If I'm missing something, and there's a good program with some sort of certification, then please point me that way.
I'm really into this kind of teaching, and I hope it helps the poor, cause there's lots of job openings but not enough talent.
This is just one step, a big one, but not the hole solution.
Google is either throwing AppEngine fluff or a pump fake.
This isn't iMovie; it's a courseware building platform. They didn't claim it would be useful for everyone.
Speaking of which, what tool would you suggest instead of Moodle?
https://code.google.com/p/course-builder/source/browse/#git%...
There's really not much there, and a lot of the code is kind of junk code meant to get people stuck on GAE. Here's my criticism of it so far:
* Most of the controller code looks slapped together and kind of hacked on rather than designed with any thought. https://code.google.com/p/course-builder/source/browse/cours...
* There's hardly any other services other than a model for Lesson/Unit/Student and controllers that are hardcoded for their own course. For example, their entire Assessment system in lessons.py isn't backed by any model and is just dumped into the Student model, which means students can't be assessed more than once or on multiple courses or lessons? Hopefully I'm reading that wrong.
* The model isn't even really right. There's no Course or Instructor model and all the other things that should be models are just tossed into lessons.py controllers and dumped into memcache.
* Very tied to GAE it seems, and to set this up you'd better be damn good at that and python. There's no way in hell this'd ever be useable by anybody but a programmer.
* The assessment stuff is either going to be useless or a major time sink for them. Instructors are notorious for having batshit crazy assessment systems making it impossible to create a universal one they'll all use. I'd ditch that stuff or hook it into google docs spreadsheet instead.
* Seems to have almost zero Student->Instructor communication, and only a placeholder for the Forums. If they plan on doing the classic Google Supportless Tech Support then they better fix that, or hook it into G+ better. Problem with G+ is they'll need to make it so students can't monopolize instructor time in private.
* They'll very definitely be tying this to all their services, which means it'll only be slightly useful outside of the google ecosystem. If they plan on getting into the K-12 hosting then that'll be a problem for them since many school systems can't host student data on outside computers because of student privacy laws.
It's easy to rip apart code like this, and most likely when I release the code to my stuff people will do the same (and should). But, if they post a breathless press release touting it, then I expect it to be much more capable than this. This to me looks like classic corporate FLOSS white elephant code where they hope some poor suckers will jump in and make it great for them so they don't have to work on it anymore.
Oh well, at least they shipped.
I use GAE and feel it's an incredible boon to teams who want to focus on app logic and not infrastructure.
sure it might not be your preference, but it's a great technology, extremely easy to use, and very useful. You should recognize it as such.
Shameless plug, but for those looking for more of a turnkey hosted solution, check out Pathwright: http://www.pathwright.com
Installing the example code and running it indicates that there was a previous course that started July 10.
Most of the complaints about pricing were fixed when users looked more carefully at their code. For some it's not worth it to do so, but that's not Google's fault. And before that, their inefficient code was costing Google money. You'd have done the same thing.