>>11782934For reference, I want to say that I'm not in CS, and I've worked in aviation for a while before grad school
>CS people know nothing about control systemsControl systems are not "hard" at the undergrad level. I agree that it's the biggest hurdle, but it's not a "big hurdle" after some practical experience and hitting the books. The worst CS students are code monkeys. The best CS students are either in grad school or engineers like the rest of the people, learning what they need on the job.
>low levelCS programs usually suck, but their OS and embedded classes are usually good, when offered.
>It’s not something you can learn in a month too.you can't learn control in a month, but it can be done within a semester or two given a wee bit of background
>Plus they don’t know about DSP (kind of similar). this is false - half of the programs out there do have DSP, but even when they don't, DSP itself isn't more than 2-3 months of introductory "match the transforms and linear systems to the physical phenomena" + some calculations in undergrad. DSP is not hard.
>Without this knowledge they are very limited on what they could do. ...have you worked on avionics before?
>They probably couldn’t even check the code simulink poops out because they would have no idea what’s happening.Anon I think you're starting to overvalue your EE degree. Does it make your peepee soft to hear other people can learn this on the job? Simulink is important but it's not hard to learn.
>This doesn’t even go into the low level shit that they probably don’t know much about. I bet they never made a kernel module.Most of the CS grads I've worked with are those who wrote baby OSes from the pintOS standard, which is generally standard in CS from my understanding.
>Not to say that they even SHOULD or it’s bad....but the ones in the field do...
Dude, I get it, CS programs suck, but if you've worked in these companies, there is a reason you see a few there.
