4 ms·
> If we truly want cross trained people, the education system is the one that needs to change. Absolutely and it goes beyond the profiteering that people typic
by y-c-o-m-b 7y ago
> If we truly want cross trained people, the education system is the one that needs to change.
Absolutely and it goes beyond the profiteering that people typically rant about. The barriers to obtaining a degree for the sake of obtaining a degree are high in itself. Then we add bureaucracy and a bottom-up approach to teaching that I think excludes a good amount of potentially qualified people that would otherwise do great.
Software development is a great example of highly successful people that either dropped out of high school or college because they discovered a top-down approach can lead to the same outcome as a bottom-up academic one. Top-down example being: you want to build an app, you learn only what you need to build it (e.g. html, css, and javascript) then with continued years of applying that experience in related areas you naturally acquire more of the fundamentals of computer science.
I don't think it's appreciated here on HN because a good chunk of the members have higher education degrees and can't see past their own bias, hence the down-votes and lack of actual responses. I've seen this topic appear before and with it comes condescending responses towards those that don't hold a degree. This was especially evident on the HN platform when people learned Edward Snowden was a drop-out.
The current attitude towards this is well rooted in society and still a hard one to break. Thankfully tech companies are starting to come around to the idea.
- yellowapple 7y ago> I don't think it's appreciated here on HN because a good chunk of the members have higher education degrees and can't see past their own bias, hence the down-votes and lack of actual responses. Ding ding ding. I've gotten my share of flak on a couple occasions for working in IT without a degree. These people looking down on me are probably right that they're smarter than me and more knowledgeable than me and could probably code circles around me. I know I ain't getting a FAANG job any time soon. I know full well that there are gaps in my knowledge that someday I'd be interested in filling once I've got enough saved up to try college again. Doesn't mean I can't be productive, too, nor does it mean I can't teach myself what I need to know to get the job done. Maybe duct-taping systems together with MSSQL sprocs and proprietary programming languages/runtimes and shell scripts and CSVs ain't the most glamorous work compared to playing around with blockchains and neural nets and Jupyter notebooks, but it's work that needs done regardless, and I ain't too proud to do it, even if it's putting grey hairs on my head decades before they've got any business being there. "Top-down" v. "bottom-up" is definitely a good way of putting it. The code I write ain't pretty, but it's gonna do exactly what I need it to do to solve the user's problem, and chances are it's solving problems for which there are no elegant solutions. It ain't gonna run like a Lamborghini, but that's okay; I just need it to run like a Tacoma.