3 ms·
> And they boasted of it! To a theater full of CS students. I think this is highly contextual, and how you interpreted that statement depends on how you were p
by kbenson 10y ago
> And they boasted of it! To a theater full of CS students.
I think this is highly contextual, and how you interpreted that statement depends on how you were primed to interpret it. You can assume they meant that it's an age based hierarchy, or you can assume that it's an extremely complex job that a CS degree doesn't adequately prepare you for, so it takes a couple years of apprenticeship before you are qualified to do something yourself.
There are plenty of industries like this, where it's not just about being smart and using your intellect to put the relatively small amount of parts together into something that works, but instead has a large chunk of learned wisdom that is not quick to impart, the importance of which is sometimes discounted until it's dealt with, and the consequences of messing up are fairly high.
Some examples: electricians, plumbers, architects. Fields that we've decided often require certification and that certification requires an apprenticeship period, because we don't want electrical fires or dead electricians, or water damage to our homes, or leaking sewage, or collapsing buildings.
In a lot of ways, I think the problem with the software engineering industry is that we don't have a system like this in place. Name me a programmer that thinks he was just as good at 22 at not making architectural or security mistakes as he was after 10 years more of programming and I'll name a programmer I never want to work with. Chances are they'll be the same person.
- eli_gottlieb 10y agoYeah, when I want kernel or firmware code written, I want it done by someone experienced, or someone trained by someone experienced. I've had the very fortunate experience of being the latter person (up until only a little while ago), so looking back, I can damn well see the difference.