I sincerely doubt it. For learning the non-practical fundamentals of, say, computer science, there is no known learning environment that beats a university.
> Not a degree, but a trade school
So, only directly applicable skills, no theory and nuts-and-bolts fundamentals? Sounds far inferior to a bachelor's degree.
The software field is known for being open to talented autodidacts, in a way that, say, bridge engineering is not. That doesn't mean it makes sense to dismiss the benefits of quality formal education.
Someone with a decent bachelor's degree in computer science will have a depth and breadth of knowledge far in excess of where they'd be if they'd spent that time teaching themselves web development on the job.
> No BS courses like philosophy, social sciences, etc
Here in the UK, a STEM degree is quite 'pure', and you aren't expected to study topics like philosophy. That doesn't mean there's no value in studying them though. If philosophy struck you as a complete waste of time, then either it was taught badly, or you failed to make the most of it.
This is just nonsense. I would go so far as to say that I never actually learned anything in my undergrad CS classes. A combination of challenging internships and personal curiosity let me to teach myself everything I was taught in school before I was taught it in school. Of course, I only got those internships in the first place because I went to a good school and had connections that I gained by attending that school, but the idea that an otherwise competent developer can't teach themselves CS theory efficiently on their own is totally absurd.
Furthermore, being taught CS fundamentals in a university is far from a good indicator of developer ability. I've interviewed a shocking number of candidates with at least a BS in computer science who were completely unable to complete incredibly simple exercises (think similar in complexity to FizzBuzz). I expect developers to have a strong grasp of the fundamentals, but they also need to be able to actually apply those fundamentals. CS departments are utterly failing in that regard.
I'm not sure whether to think your school had an awful CS program or you went into your classes with the wrong attitude.
There are lots of practical skills that get taught in universities that aren't direct trade knowledge -- you didn't feel like you learned how to learn? Or were exposed to new ideas and parts of the field that you otherwise wouldn't know about?
> A combination of challenging internships and personal curiosity let me to teach myself everything I was taught in school before I was taught it in school.
Which doesn't mean that their CS program wasn't teaching anything worthwhile, just that it didn't have a monopoly on that value. It also doesn't mean that they had the wrong attitude; on the contrary, I think learning out of self-interest is a much better attitude than waiting for that knowledge to be fed to oneself in a classroom.
God forbid you don't even consider that you're wrong. "Wrong attitude" signaling is pathetic.
> There are lots of practical skills that get taught in universities that aren't direct trade knowledge
That's a problem, but it's also hyperbole. I mean, I'm talking to a 1998 CS/EE from Berkeley who couldn't bother to try to repair his own power supply because it has a danger sticker on it. What you learn in University is to be so blind in your lane, that you don't even recognize it. It's the antithesis of learning to learn.
Write a substantive counterpoint, if you want me to consider a differing opinion.
If you aren't interested in doing that, there's little point attacking me for expressing mine.
Out of that list, I think the only thing I hadn't heard about prior to attending college was multithreading [1]. They did cover a lot of theoretical material though. In fact, there were a few professors in the computer science department that despised computers and barely touched the things (personally, I think they were failed math professors).
[1] I attended university in the late 80s/early 90s.
Today, I'd expect any recent CS graduate to have studied most, or perhaps all, of those topics. In my CS degree we covered every one of them.
(Of course, I'm simply mirroring beambot's comment, here.)
Also, all of the BS humanities and other non-pertinent classes were entirely useless, and for many it seemed the curriculum was entirely politically driven; learned very little from these.
IBEW electricians apprentice program is 5 years long. 6 months classroom, 6 months on a job site, repeat for 5 years until you're a journeyman.
IMO the exact same pattern would be more effective than a 4 year degree any day. I've interviewed 100s of college grads at a top tech company, and I used to teach a bootcamp program. My 14 week bootcamp grads were more useful than any college grad I've interviewed, but had weak understanding of the fundamentals. If that bootcamp was 2 years I could've probably gotten them up to speed. If that classroom time was intermixed with actual industry experience they'd come out the other end ready to hit the ground running.
That's the issue with bootcamps, along with the cost.
A local bootcamp (Wyncode) is 11 weeks at $10,000, which is ridiculous. 1-2 programming classes at a local school can probably supplement your fundamentals, honestly, Operating Systems, Parallel Programming, and Senior Project would probably be the most useful courses for a bootcamp grad.
Beyond that, our course material was bleeding edge. When some new hottness came out we incorporated it into our curriculum. Colleges have too much bureaucracy to keep up with the latest tech trends.
I think it is tolerable that a bootcamp leaves out 3 semesters of calculus, 3 semesters of physics, 2 semesters of discrete math, 1 semester of statistics, 1 semester of digital logic, more math, and more science. The value here is limited.
What is terrible is that a bootcamp usually neglects anything outside of one narrow specialty that happens to be popular, typically web development. The typical bootcamp isn't teaching how to create a compiler, an OS, factory automation, life-critical software, or hard real-time software.
I mean, I did that for my CS degree. It was 8 months classroom, 4 months in the field, but pretty close, right? And I got paid pretty good money for those 4 months in the field!
I'll never understand the others in my program that didn't try to find internships.
Regardless, courses in English, Literature, and other courses I had to take outside of my main coursework for Computer Science has made my personal experience better, I believe, or at least more fulfilling.
I believe that it is also the job of a good education to prepare someone to be a good member of a Democracy, and as part of that one must be able to accept other tolerant points of view, and be able to reach compromise. Courses all throughout our education should aid us in developing the empathy necessary for the process to work. It appears that we have failed, in the US, in this regard. Quite horribly.
I was fucking furious when I realized I'd been duped. I'm a voracious omnivore and I do believe Universities should promote wider learning but this was a straight up money extraction scam.
We shouldn't be punished for choosing difficult courses, and actually learning the material, even if it is slightly behind the pace of the course itself. Unfortunately, doing so has implications for your entire future in the United States (unless you have the money to buy your way into college, of course).
It could be specific to the University I went to, or some aspect of the fact that I went to a Jesuit University that made the quality of the philosophy coursework I took so high.
Regardless, I'm sorry you had that experience.
Then again, twenty-five years ago I wouldn't have even entertained the idea that more liberal education classes for me would serve me and the world around me better. It wasn't until I started reading those books out of curiosity later in life that I really appreciated their value.
Too much of that stuff is indoctrination and opinion being passed off as education as of late.
It results in people who believe they are "educated" because they have learned to hold certain opinions. And judging others "education" by the opinions they hold rather than fact that they know.
That isn't to say an understanding of history, of languages etc isn't worth having, it certainly is. Some of the other stuff not so much.
Additionally, the sad reality on the ground often is a person is judged as educated by the display of indoctrination they receive, so practically speaking, at this point in time it does have some value can open doors. But that's kind of BS really imo, and I don't care for it.
I think these students are failed by the system as programming’s core concepts are quite basic, it seems to be the tooling around it that students struggle with.
Comp Sci is 'Sci' :)
It just so happens that being a good programmer is mostly an applied skill, and that you don't have to have rocket science Comp Sci chops to be a decent developer.
In fact, in 2019, a lot of development just isn't really Comp Sci.
That said, I wonder if programs should adapt and be more applied to have more of a professional kind of designation.
It's the same way with CS. It should be part of the college of science, just like chemistry. Software engineering should be a separate discipline, and be within the college of engineering. And having a CS degree doesn't really prepare you to work as a software engineer.
Unfortunately, what we have is CS departments turning out graduates, most of whom will work as software engineers rather than computer scientists, and who are therefore badly trained for the career that they're going to try to have...
Partly due to the fact 'Engineering' is a hard thing to apply in the computer world.
Partly because software R&D and Enterprise Software isn't engineering either!
Well, no. Of course not.
Theoretical computer science, for instance, might be defined as mathematics that pertains to computation.
Rice's Theorem isn't the result of any programming. Neither is information theory.
I've tried university twice and left both times before getting a degree. We are utterly incompatible, despite my grades being in the top 1% from an academic standpoint (And while attending my GPA was 4.0)
I was headhunted in 1st year (the first time) and never looked back. I've come across many 'self motivated' coders like myself who thrive in all things IT, without needing to be spoonfed.
> no theory and nuts-and-bolts fundamentals?
I've done digital and electronics and full stack engineering, written compilers, embedded systems, 3D engines and modellers, etc, etc.
I think that suffices as 'nuts and bolts'. I'm only yet to write my own OS.
When hiring, I would basically ignore the degree and look at their work: their code and their ability to communicate their understanding of it.
I think we live in two different worlds indeed! I'm more like OP and like getting down and dirty. I see problems (in the marketplace) and I make solutions - however they come whether it be JS or ASM.
It seems fairly clear then that you aren't representative.
> When hiring, I would basically ignore the degree and look at their work: their code and their ability to communicate their understanding of it.
This could well be a wise strategy. I'm not saying academic achievement is the best predictor of industry success - there are plenty of horror stories of seemingly impressive graduates failing fizzbuzz.
It seems clear to me though that for many of us, a CS degree is the proper way to start one's tech career.
> I'm more like OP and like getting down and dirty
But you're clearly quite capable at working with advanced topics 'behind the code'. This can't be said of all professional programmers. There are plenty of code monkeys out there who don't even understand basic data-structures, let alone the concepts behind compilers and rendering engines.
Also, zero professional judgement, and more likely than not, not even knowing what they are missing. Engineering curricula have their problems but at least fresh MEs and EEs IME realize that they don't know anything. Fresh CS grads come in and want to do a rewrite--in a language not used anywhere else in the company no less. Give me a self taught guy any day of the week and twice on Sundays.
I agree with all of this.
I suspect it's due at least in part to the way the software world has an attitude of move fast and break things, whereas bridge engineers and aeronautical engineers are shown disaster photos to emphasise the point that If you screw up in your professional responsibilities, you may kill hundreds of people.
You don't ask a fresh graduate to single-handedly design a bridge. If you did, I like to imagine they'd be sufficiently terrified that they'd decline, and not just because of the legal regulations.
There is no such 'culture of responsibility' in the software world, excepting a few life-critical problem domains.
I suspect universities could reduce the fresh graduate know-it-all effect if they made the effort:
* Teach students about the cognitive biases that will cause them to overestimate their own expertise early in their careers
* Related: teach them the principle of Chesterton's Fence (especially valuable in junior developers)
Also, perhaps explicitly enumerate the skills that they simply will not have on day 1 in industry -- the skills that cannot really be taught in a university -- such as:
* The ability to work effectively with with legacy systems that are large, badly written, use inconsistent style, and are poorly documented (like a boxer, much of a developer's job is simply to cope with chaos)
* The ability to communicate effectively with non-technical customers (coursework is a poor simulacrum)
> Give me a self taught guy any day of the week and twice on Sundays.
Perhaps if you're hiring them for a 6 month stint, this might make good sense.
I'm not saying a degree is a substitute for industry experience, I'm saying there's value in what's taught, and that developers are unlikely to ever learn those things on the job.
On the job, you're probably right. But if someone happens to be the type of person that sees a link about a new asymptotically fastest multiplication algorithm and ends up spending an hour reading about karatsuba multiplication then he or she is likely to catch up after too many years, and then pass the formally educated that aren't so inclined.
So if you'll take a friendly amendment I'd say:
- If you want someone for a six month stint, go self taught
- If your company is using the tournament model and you churn through juniors in two or three years on average, go with CS grads (careful of those sharp edges though)
- If you are looking to invest in employees for the long term, go with lifelong learners regardless of credentials
I'm not sure about this. It seems to me that this really downplays the value of attending a good university.
Speaking for myself, I really can't imagine 'catching up with myself' had I not gone to university.
I wouldn't have developed my writing skills. I likely wouldn't have seen what proper grown-up mathematics looks like. I wouldn't have seen how academics work, up close. I can't honestly say I would likely have studied the various dry-but-valuable topics that universities are known for. I'd probably have a much harder time reading computer science research papers.
Additionally, universities teach students how to learn independently. I don't think this should be underestimated.
> If you want someone for a six month stint, go self taught
Well, kinda. If you want someone for a six month stint, and your choice is somehow between a green-horn graduate and a seasoned developer who never went to university, then sure, you're probably best off with the experienced developer.
(Assuming of course that the problem domain doesn't require any particular technical specialism.)
There's a reason large companies run training programmes for fresh graduates: they want people with formal training and the necessary working knowledge.
> If your company is using the tournament model and you churn through juniors in two or three years on average, go with CS grads
I'm sure this happens, but I'm not sure it makes any sense. I know it's the norm for software professionals to move jobs every few years to get the raise they deserve, but I'm not convinced this is in the interests of the employers. They have spend considerable effort bringing their replacement up to speed.
> If you are looking to invest in employees for the long term, go with lifelong learners regardless of credentials
I don't follow. Credentials reflect expertise and achievement, it's just that they aren't the whole picture. Do Google recruiters discount the grades of their applicants? No, they're looking for top-flight hires, and grades are an important part of that.
Hell if you had called any of my pears on my Mech Eng Btech (termo fluids) course an apprentice we would have told you where to shove it.
I think you kind of just made the point. Why would I pay for something that isn’t practical?
And because what counts as “practicality” changes as people progress through their careers, but the foundations required to meet each new standard of what counts as practical often remain the same (or change less).
Most of us are working to increase business value for companies - either by making them money or by saving them money. They could care less about “Cracking the Code” and LeetCode.
Most developers won’t be doing that these days.
As my career has progressed, it’s moved further away and at higher levels of abstractions. These days even hardware is abstracted behind an API with cloud providers.
I assume what the parent meant was a "data structures and algorithms" course, compared with say, "How to code in Java using the standard library".
The latter is "practical" - you can take what you learn and churn out code in Java.
The former is "non-practical" - you can't make the theories you now understand function without a practical implementation. But you can recognize the implementation in any environment, and understand its implications.
The general assertion is that an understanding of the "non-practical" will serve you longer than a purely "practical" education. I tend to agree.
A concrete example: My firewall rule is set to deny all incoming TCP connections except those originating from port 80, and destined for port 80. Why is it blocking all my HTTP connection attempts?
If you understand TCP, you'll understanding that we shouldn't be filtering on source port at all. If you have only the vague sort of understanding that comes from using a technology in practice but never having properly studied it, you might have no idea.
And yet I'd still count that as 'non-practical knowledge'. It isn't something you're ever going to apply 'directly', unless you're one of the handful of people implementing their own TCP stack.
There's similar value in studying complexity theory (why does this seemingly simple code take so long?), operating system fundamentals (aren't containers and VMs roughly the same though?), and compilers (for a deeper appreciation of programming in general, and, my personal favourite, to instil a due sense of terror regarding undefined behaviour in C-family languages).
You don’t have to look far to see examples of leaders of companies who could’ve benefited from an education in humanities (e.g Facebook). Yes it’s still possible to act unethically and immorally after an education in humanities, but the hope is that it will lessen that outcome.
Ultimately ignoring ethics in technology will lead to bad outcomes.
> You either have morals or you don't. Classes don't instill them.
Morals are learned, not inherited. You can teach morals, whether in a course, or in a family. Of course, the practical side is very important here... one has to learn to resist factors that corrupt your moral values.
That isn't to say that ethics is completely subjective or whatever you feel like, but the class helped nudge me out of an "everyone who disagrees with me must be wrong" attitude.
Plenty of people learn this without having to take a class but in my case the class was helpful.
Besides morality, knowledge of impact of this or that o world around matters. That is diferrent then morality and you can't derive it only from own experience.
Lastly, there are plenty of near psychopaths and assholes in the army including marines. And it is not like various units did not had problems with bullying harassment and what on. Or if ships did not hit other ships recently because of chain or errors quite a few of them in ethical category.
I've met more sociopath types in IT than I ever ran into in the military. The military tends to get a bad rap in civilian circles, particularly the Marines, because they attract alpha males. It takes a certain mindset and ability to deal with vast amounts of mind games and BS to serve in the Marines, but to outsiders, this makes no sense. The near-24-hour chaos provided in training and in garrison teaches people to deal with chaos while making decisions that affect the lives of teammates. The yelling, hazing, banter, and heavy physicality teach you that in your chosen profession, there is no rose garden. As George Orwell wrote: "People sleep peaceably in their beds at night only because rough men stand ready to do violence on their behalf."
Bullying should be purged, near-harmless hazing, no. It teaches rite of passage, that membership is achieved and earned, not given. I don't want to work with beta males. They get people killed. Indecisiveness in combat gets people killed. When you're in combat, you're not giving a shit about the US or any other place. You're not fighting for that. You care only about the guys to your right and left. You live or die as a team.
Morals always put the other person first. Love of family or teammates is not an emotion, but an act of the will. Love is not an emotion, it's an act of the will. You will the good of the other for other, with their best intentions in mind, even if it costs you your life.
As Jesus said, "Greater love hath no man than this, that a man lay down his life for his friends."
Morals have more to do with how you treat non-members and beta males and competitors.
Not sure what all that has to do with combat. Ultimately, people in IT are not in combat. Our moral questions are about which projects to work on and whether overly optimistic estimate counts as lie. Should I fight my manger to be unethical and where is the line? How much tracking is ok and am I going to develop software that breaks the law?
If what you're trying to say is that anyone can learn to become ethical, then that's a reasonable opinion. But I don't think citing Aristotle usefully refutes the parent commenter's point about people either having morality or not having it, because Aristotle hardly settled the matter on any major dilemma in philosophy. Furthermore, Aristotle's Ethics go on about "right" education quite a bit - to the point that you can reasonably conclude people can't become ethical if it's not instilled in them early enough on in their life.
Zuckerberg studied psychology, most likely it helped him learn how to manipulate people and Facebook might not have been a success without it. Not sure if this was what you meant.
I do not believe that university fullfills a really good role when it comes to filtering for intelligence, it rather filters for familys who put pressure to preservere on kids. But they do a really good job, on forcing people through stuff, that a self-tought person might skip- because they found it useless or not applicable. Algorithm theory and the limits of computation? That is a dry topic and tough to get through without beeing forced too. Software-architecture? Cant see me using that- those small projects i worked on always worked well without. And so on and so forth.
University does one thing right, it forces you to be interested in stuff you do not know you should be interested in.
I do find the filtering out of people who go to university - either by school grades or by monetary parent background really nasty though. In my eyes, anyone who is shown to apply himself, should be able to stay at a higher education.
Front-loading on dry subjects also has the downside of scaring away people who would've otherwise done well given a different path of learning.
The timing of when you learn some things is also important; it matters not if you learned software architecture in college only to have all the knowledge become obsolete by the time you really need that skill - you'd have to review or worse relearn it by yourself all over again.
There's no way to know in advance which of those classes you won't need, though. Programming has become very specialized; it's no longer possible for a University to provide an education sufficient to prepare a student for the work they'll be doing in the "real world" because there's so much variability from one job to the next. Having a broad education, though, puts a person in a situation where they can more readily adapt to a wide variety of roles than they would without that background knowledge.
The point is, if I was only a self-taught programmer, it never would have occurred to me to take those "irrelevant" physics classes. But those classes, along with the mechanical engineering classes, math, etc., have helped improve my programming in quite unexpected ways.
There's also the simple pleasure of knowing how things work. I'm able to figure out why my car doesn't work, and when the mechanic is giving me a line of bull. Many, many features of the house I live in was the result of my diverse education. (For example, don't use iron nails to hold copper. Don't run cat5 cables through the same holes as the 125V wires.)
I think people with CS degrees working the field could probably re-cover all of the content of their degree in 4-5 months of independent study, however, there's a lot of school which is deliberative practice. Hours that you need to spend getting good at understanding concepts, writing proofs and building the skill of critical thinking in a computing context.
I think post graduation there's a tendency to compress that period and forget about the hours of practice and just being terrible at building things that it took to gain the craftsman's mind.
....you totally missed the point of those classes.
Not regarding any particular subject though, a breadth of experiences is always good because it gives you more contexts to think in and draw analogies from. Things like the behavior of ants influencing your thinking on distributed systems, issues of group communication brought up in a Communications class relevant to server architecture (connections in a group growing as a square), queue behavior in shopping centers/theme parks, thinking of Sherlock's investigation methods while debugging, lots of examples.
It's fine to study something for the sake of studying it. I have no problem with a course on basket-weaving because it's an art and worthy of attention in its own right. As a center for higher learning that explores the full human experience, it's entirely justifiable that a university should consider a course in basket-weaving.
But the academy is a human institution and subject to decay. More concrete courses like math are constantly checking themselves and anyone can work through proofs and say, "no, this is wrong," and get people back on track. Your basket-weaving course, on the other hand, has no practical moorings and can drift off into irrelevancy.
FWIW, I did a minor in philosophy, and while I found it very enlightening, they pretty much admitted it was pointless.
I think I have something to add to this. During the course of completing a Ph.D. in computer science I discovered that I actually have a huge passion for behavioral ecology. For the first years of my Ph.D. I just treated it like a side hobby and tried to learn as much about it on my own. Halfway though the Ph.D. I decided I might as well take some intro bio courses and as many ecology/evolution courses as possible since my tuition was being paid for anyways. The amount that the coursework improved my learning rate was incredible even though I was spending approximately the same amount of time as before.
As to why I think it is a combination of many factors. One of the main ones being held accountable to truly mastering the material (tests, projects, homeworks etc...).
This is just a sample of 1, but from my experience the classroom experience was a huge net benefit to learning about a subject I really cared about.
If you were just looking for a specific skill or job training then Uni may have not been the place for you.
"I've never been impressed with Ivy league or other "rarified air" educational establishments."
I did undergrad at a great but niche school and Grad school at a fairly exceptional school and there is a difference. The top schools generally have the best profs, students, facilities. It was inspiring and motivating, and the relationships and networks do matter as well.
As far as 'looking down their noses' ... this comes in two parts 1) they are doing it, sometimes without knowing it but 2) often we perceive 'snobbery' when really it's just our own insecurity. When we perceive someone to be of higher social status (ie our perception), or, when we think that they may perceive us as having lower social status, then I think we have a tendency to interpret every little thing as snobbery, when really it might be nothing at all.
Personally, I'm not insecure. I grew up military, and served for 8 years. I'm you're atypical alpha male. I have will and intent in spades, but I care deeply for other people. Let me explain...
My time in the Corps taught me that we are all equal, no matter our origins. I don't play favorites, be it education, time in position, man/woman, it doesn't matter. I believe in earned merit. Full stop. I treat everyone with dignity and respect, but merit is earned and demonstrated. I don't yell at juniors, I lead from the front. There is nothing I will not do for a teammate who tries their best. I tell my teammates even now, please, make mistakes. It's healthy. If you bork a production server, and you did your best, but made mistakes, we'll fix it together. You learn, and I'll learn along with you, because maybe I could have done something better, like documentation, or settings. Good leaders are open to correction. If your ideas are better than mine, convince me. If you're right, I stand corrected. If you're wrong, I still want you to keep stabbing forward. I encourage experimentation, tinkering, and always improving.
As far as social status, I've never been envious of those from that arena. I just don't care. I look like Shaggy Rogers if that says anything. I can afford a much nicer car than I drive, but I don't care. Ditto my clothes. It's point A-B for me. I'd rather my children have better clothes, nicer treats, and time spent together. I have zero tolerance for social snobbery, as it shows an air of superiority that is not real. If you (metaphorically) think you're better than me, let's see how things go when the power is out, the food stops being delivered, and your apps don't work. Me? I would thrive in this world should it happen. When the zombies are coming, you'll be running to my house.
I'm sure this does apply to almost everyone - given a specific curriculum and removing constraints people could learn things faster.
But that doesn't mean that without the constraints you could come up with the same curriculum and still learn things you're not forced to learn immediately.
There absolutely are schools where programming is treated as a trade, eg: https://www.bcit.ca/study/programs/5500dipma
I've worked with several graduates from this school and I can say it produces excellent programmers, particularly for low-level systems stuff.
You start off right away with object oriented programming basics and simple algorithms, with most of your first year dedicated to those, design patterns, basic maths, basic communication (English and French in our case).
Second year moves into specialisations (networking, business systems design, or software development). I did software development and that's where the Java enterprise projects come in (applying design patterns), some Android programming, some more advanced algorithm stuff (still easy on the whole, similar level to the leetcode questions at FB interviews), ...
The final year will have some side courses on introduction to law (focus on copyright), some stuff about extreme programming, some communication, a bigger project and then the second half will be an internship.
And that's it. No crazy math, no super theoretical stuff, only basic non-engineering skills with a focus on the things that are practical skills as a software engineer.
I felt prepared for the professional world after that. Maybe not the things where you micro-optimise algorithms, build low-level tools and languages. But it definitely gave me a fantastic basis to join a web development company. Enough knowledge about programming and patterns to be able to pick up new languages and be productive in them fast.
You'll see few people with this degree in the hard computer science jobs, but I do think (having seen both) that people straight from school with my degree are better at just building applications on top of existing frameworks. We had practical experience with a lot of popular tools at school, and maybe less hang-ups about not always sticking with the theoretical most efficient way if it'd take longer to implement.
This type of education exists, works and has it's place.
(Note: I actually dropped out after three years without finishing the internship and without passing some of the non-coding courses because I had a nice job offer. I did do every subject so basically have the education, just not the proof.)
Three things that I got out of it:
- engineering processes, - data structures and modelling, and - algorithms and the application
Learning to code well in a particular language you really did in your own time, and that never stops.
It was those fundamentals and learning how to apply software engineering to develop a solution to a problem that I came away with.
You could learn those fundamentals from a book, but the degree should really be an indicator that you have mastered those basics.
Given the risk of privacy and security breaches and the financial/legal consequences if you get it wrong, it's probably time there was an IEEE/AMA/Bar equivalent that signals that you have that understanding and rigorous process.
I've interviewed 100s of university grads and most of them don't know how to actually do anything useful. They have the foundations to grow into the position, but they certainly need someone to hold their hand for a while.
One great example is IBEW electricians. They do a 5 year program. 6 months class room, 6 months on a job site as an apprentice applying the skills learned. Repeat for 5 years with gradual pay raises until you hit journeyman and it jumps up to full union scale.
I think the exact same type of program would work GREAT for software engineering. Learning for 4 months in a vacuum and THEN working in the industry for the first time is a terrible idea. However, doing 6 months back and forth would allow you to apply what you learn and more importantly to learn what you don't know so you can focus on those things during the classroom segments.
I've never been impressed with Ivy league or other "rarified air" educational establishments. I've worked around people from some of these places and almost to a man, they reeked of one-upmanship, my father knows..., I know..., oh, you went to <insert no-name university> while glancing down their nose at you.
I worked with a guy like this at UUNet who went to Brown. He thought he was the cat's pajamas and everyone should defer to him because he went Ivy League. Oddly enough (sarcasm), his mistakes were often corrected by those who attended the no-name schools. He never saw the error of his ways. Daddy, after all, was a prominent attorney in the DC area. Why this guy went IT is a mystery. He would have been a better fit with the other sharks and scammers in DC or on Wall Street.