Yeah I just haven’t seen this happen. I’ve seen plenty of people graduate who were pretty useless. But … I think every self taught programmer I’ve worked with had meaningful gaps in their knowledge.

They’d spend a week in JavaScript to save them from 5 minutes with C or bash. Or they’d write incredibly slow code because they didn’t know the appropriate algorithms and data structures. They wouldn’t know how to profile their program to learn where the time is being spent. (Or that that’s even a thing). Some would have terrible intuitions around how the computer actually runs a program, so they can’t guess what would be fast or slow. I’ve seen wild abstractions to work around misunderstandings of the operating system. Hundreds of lines to deal with a case that can’t actually ever happen, or because someone missed the memo on a syscall that solves their exact problem. There’s also hairball nests of code because someone doesn’t know what a state machine is. Or how to factorise their problem in other ways. One guy I worked with thought the react team invented functional programming. Someone else doesn’t understand how you could write programs without OO inheritance. And I’ve seen so many bugs. Months of bugs, that could be prevented with the right design and tests.

I’ve worked with incredibly smart self taught programmers. Some of the smartest people I’ve ever worked with. But the thing about blind spots is you don’t know you have them. You say you’re self taught, and self taught people can be better than people who went to school. In limited domains, yeah. Smart matters a lot. But you don’t know what you don’t know. You don’t know what you missed out on. And you don’t know what problems in the workplace you could have easily solved if you knew how.