JaredRichardson
JaredRichardson on Hacker News
I have found the embedded industry to be a tad more conservative (That was an understatement. ;) ), so it may be a bit longer before they pick up the model.
Yesterday we had a junior team member run into a problem with a data structure, so that led to an off the cuff tutorial on data structures (linked lists, hash tables, benefits, trade offs, etc) for several team members, but in the context of the current project. And wasn't a part of the academy, just how we mentor our team. We've found that kind of "in context learning" is much more effective than many classroom environments.
I'm not sure how far back the idea goes, but I've only seen it recently, so I'm not sure what you'll find in terms of formal employment rates. However the RoleModel program is lining up sponsors. A "sponsor", among other things, gets first crack at interviewing the graduates. http://craftsmanshipacademy.com/sponsor/ But I must say, I don't think you'll find Ruby a bad skillset to have. http://news.ycombinator.com/item?id=3404616
I strongly suspect these programs are just the beginning of the backlash against what many are calling the higher education bubble. People are tired of graduating thousands (or tens of thousands!) of dollars in debt after investing years of their life. These programs compress down the process, and eliminate a lot of the non-core learning, to help you become productive as quickly as possible.
I have a CS degree, but have seen and worked with a number of the people that have come through the RoleModel mentoring program in past years. I think the academy concept is a more formal iteration of that same idea. I'm looking forward to our first class in a few months.
There are some companies that will raise your compensation to reflect your experience, but most won't. And that's the problem.
On the other hand, not training your team costs a whole lot more! Shipping junk products can tank your company outright.
I'd appreciate any help spreading the word. I'm involved with much more of the technical sites than the managerial ones.
Re: DSLs... I don't think the DSL specs always stay in front of the customer (they sometimes do), but they're a valuable tool. Whether it's a developer, a technical customer, or a non technical customer, you've provided a much simpler way to show what the system does. That's a huge win.
I also find that developers who spend time in DSLs tend to write much cleaner code. Once you get used that level of abstraction, you use it in other places.
I don't think that using tools makes us "bad"... I think pretending that we're "good" when we really need the tools make it much more difficult for us to past our egos and really look for what we need. There are so many great practices and tools available, but most developers I've encountered because things are "good enough". I was hoping to encourage people to try something new. Something a "good" programmer would never need, but a "bad" programmer would desperately want.
In regards to knowing the API versus using an IDE... spend some time with a Ruby developer. Someone who's not used to having great IDE support. They've been forced to learn the language. The difference in their productivity level is amazing. Contrast them with a developer who only learned Java or dot Net and was using Eclipse or Visual Studio from day one. Those developers tend to not learn the underlying APIs and I think it hurts their ability to know what functionality and libraries are available to them.
Anyway, it's very cool seeing an article I wrote on HN!