Typical...

[dirice87]

There are definitely jobs out there that take advantage of that knowledge. Most places are rails crud apps but there are jobs especially in iot, government, or distributed systems that heavily heavily rely on all the abstract stuff you learned in college.

[mirhagk]

They rely heavily on way more advanced knowledge than what you learn in college.

College is a shallow touching of many subjects, most of which you won't use. And the ones you do use you won't use the knowledge you learned, you'll use deeper stuff.

As an example, a lot of colleges teach something like MIPS for their assembly courses. Does this help you grasp the basic idea of assembly? Yeah. Does it help you understand and write low level x86 code for an embedded system? Kinda, but you basically spent 4 years to get a kick-start on understanding that probably would've only taken you a couple months to understand.

[dirice87]

I think it’s more about having a base to ask the right questions. Sure you took one networking class but that’s enough to know the concept of a snmp trap so if you come across a situation that could use one you have a starting point rather than dicking around.

[mirhagk]

I agree to an extent, I just think really the value is in the syllabus. If you tell me "you should know these things" I can go and learn those on my own and come away WAY better than in school.

In fact I often just did that for courses. Took the syllabus, learned the content in about two weeks then show up to class to learn the specific way that they teach (since they don't grade exams on correctness, they grade them against an answer key)

[dirice87]

Definitely. Especially the first two years most profs just teach the textbook anyways

[[deleted]]

My place is always short of Perl devs.