I don't know what coding jobs you've had by mine have all been > than 75% writing code, reading code, reviewing code, talking about what code we should write, talking about how to organize the code, supervising someone else writing code, etc...
There is the part where you talk to someone to figure out what you need to code. And that parts important but defense wasn't taught at my university.
to learn & investigate, communicate
I did not take a learning and investigation course in my CS program, not did I take a communication course.
design systems
Are there good books that teach you how to design systems in general? How to build a good chat app, vs EMR app vs a good embedded code is completely different. So every book or article I've seen on design is so abstract to be useless, or very focused on a subdomain.
Not to mention a background in OS
Honestly this hasn't really ever come in handy. I'm sure someone can come up with a time or too it was helpful but I'd trade all my knowledge about OS's for better understanding of CSS.
database
Learned a little about databases from a 6 month course but equal or less than amount my friend learned from a boot camp.
programming languages
I had experience with a bunch of esoteric languages like Haskell, lisp, but I didn't know any language well. We didnt learn anything about JavaScript.
Things he learned that I didn't, how to use an ORM, how to build a web application, how to use libraries and frameworks, how to use ruby on rails, JavaScript, react, css.
Overall we learned a similar amount of useful stuff, but he did it in 4 months for 10k and it took me 4 years and 100k.
Why is it a mistake to view them as job applications? Maybe you want to take out 100k in debt to just learn interesting things about computers, but i did it because i wanted a career.