I had terrible imposter syndrome when I landed a sw dev job. I thought everyone could tell that I didn't belong. I was / am self-taught. Everyone had CS degrees. I thought I was a fraud. I later recalibrated to realize that I'd earned it even harder without a degree. But I had to get that spot to be able to leverage my knowledge. There are probably people who know a lot more than me getting rejected because they don't have the right credentials.
CS degrees, at least in my experience, prep you for a bunch of things that honestly don't matter too much. Like, I don't think knowing what P versus NP means really helps me at my job. I think learning to use build tools and frameworks rather than just the language itself would've been more useful.
The best professor I had in that regard at college was younger and also working at a "real" company while also teaching (I believe he was getting a master's degree). He taught us about Spring and Maven and had us make a REST API. The only downside is that this course was about making GUIs and the majority of it was about Swing which nobody really uses. I have a feeling he added the other assignment because it was.more relevant to things most folks do with Java.
It's because computer science degrees aren't really programming degrees.
A computer science degree sets you up to be a scientist, most common dev jobs are just glorified Lego sets patching libraries together and constructing queries. There is skill, knowledge, and effort in those jobs, but they are fundamentally different.
Most common software dev jobs are closer to the end user than not.
I had terrible imposter syndrome when I landed a sw dev job. I thought everyone could tell that I didn't belong. I was / am self-taught. Everyone had CS degrees. I thought I was a fraud. I later recalibrated to realize that I'd earned it even harder without a degree. But I had to get that spot to be able to leverage my knowledge. There are probably people who know a lot more than me getting rejected because they don't have the right credentials.
CS degrees, at least in my experience, prep you for a bunch of things that honestly don't matter too much. Like, I don't think knowing what P versus NP means really helps me at my job. I think learning to use build tools and frameworks rather than just the language itself would've been more useful.
The best professor I had in that regard at college was younger and also working at a "real" company while also teaching (I believe he was getting a master's degree). He taught us about Spring and Maven and had us make a REST API. The only downside is that this course was about making GUIs and the majority of it was about Swing which nobody really uses. I have a feeling he added the other assignment because it was.more relevant to things most folks do with Java.
It's because computer science degrees aren't really programming degrees.
A computer science degree sets you up to be a scientist, most common dev jobs are just glorified Lego sets patching libraries together and constructing queries. There is skill, knowledge, and effort in those jobs, but they are fundamentally different.
Most common software dev jobs are closer to the end user than not.