I'm not talking even knowing the algorithms, I mean a guy that writes list.contains(condition) in a loop and it brings the server to a halt because every call to contains runs through the entire list, when a hashset.contains(condition) would run in milliseconds.
* no I did not go to a top tier school and only have a CS Minor, but I did read the books to make sure I didn't have gaps in my knowledge. It's just rare in my experience to find people that know the basics who also claim they were self-taught. People get all pissed off if you ask them what a HashMap is, which should be the most basic thing in programming.
Some people just don't fit into the way academia works, and making silly judgments like yours about them does nothing but entrench the status quo.
Absolutely it can. I would even argue that is the best way to intro into programming, and even learning in general. You, of course, cannot stop after you have pasted it in. You have to think about why the author made the choices he made, but in doing that you will quickly build an intuition to be able to apply similar choices to entirely new problems. With a little experience, you won't even need to draw on other's code anymore.
The distinction you really seem to be making here is that self-taught programmers are able to enter the job market on day one, without that experience. While graduates have at least four years of experience under their belt before they are reasonably able to enter the job market. Of course the people with more experience are going to perform better. As more time passes, the skills between the groups will start to average out (with amazing and not-so-amazing people found in both groups).
There's one set of them who can write new programs, build systems, and learn technologies they aren't familiar with, but put them on a team of 30 people for a typical enterprise project, chugging along at 10 lines per day of code, and they'll be bored out of their minds.
There's another set that can't function outside of an IDE or design new systems, have no idea how anything actually works, but they can slog through corporate stuff and follow orders well enough to stay employed.
Both are called "programmers" but they're practically different jobs. It's easy for us in the first set to look down on the second, but maybe we should just admit that they're different task categories altogether.
This sounds like a case of a programmer using the wrong datatype, realizing it, and then being too lazy to fix it.
In the UK, we have the British Computer Society (BCS) who give accreditation. If your doing a CS corse without BCS accreditation everyone knows it will be a bit suspect.
However, the BCS you've probably never heard of, they aren't exactly at the forefront of anything, they are also quite stuck in the past.
In a world where dynamic or at the very least JIT'd languages are the norm, teaching Pascal or Delphi I really doubt is in the best interests of the students. Yet in 2003 that is what I was taught for first year.
So the idea that a CS graduate will be able to go in to software development immediately is a bit missleading. It's more a case of someone who has a CS degree will have demonstrated they have the aptitude to become a software dev.
tl,dr: its education, not training.
In my university, for example, I have not once ever heard about design patterns or ever seen different coding paradigms other than OOP. What I've learned is how to solve trivial or nuanced problems in poor ways in languages not really suited for it. In job interviews, I've only passed through because of things I've personally self-taught myself due to projects I've worked on. So what's the point of an education if you have to teach yourself most things?
Conversely, you don't need to be a decent programmer to get a CS degree. It's a shame that in the age of the internet and self-directed learning, degrees are so heavily weighted in the job market.