You're being obtuse. These are fields that use UNIX, and an engineering grad with no UNIX experience might have a hard time. Someone educated solely on Windows might have a problem being dumped in front of a mainframe.
How many would be fired immediately if they started monkying around with the inner workings of their networked CAD design programs ?
Or how about just maintaining those systems? I also know a nuclear engineer who had to do a lot of UNIX programming as part of his engineering job.
Microsoft might be good for the general purpose computing world, but you need to know UNIX if you're going to work with mainframes, supercomputers or high-end workstations.
Sorry, there are a couple of Windows supercomputers, very expensive, and very low on the list.
"You're being obtuse."
LOL - My original point was that people who are NOT being taught how to use the most common operating system in the world are being given a poor education.
EVERY profession, EVERY type of employment.
Somehow, you have decided to focus on that exceeding small percentage of engineers, ONLY engineers whose system happens too be based on UNIX, that MAY be called upon to effectivly rebuild or customize the tool they are using in their career, instead of calling upon engineers whose career and specialty IS programming UNIX boxes.
... but I'M the one being obtuse.... LOL
And remember, that there are a lot of people who are responsible for computers and networks even though their job title has nothing to do with them.
A friend and former co-worker had the job title "Missile Repair Technician" while he was a Sr Airman stationed at Whiteman AFB. However, he never actually worked on missiles. He was too busy running amd maintaining their networks! He was responsible for both Novell networks as well as UNIX networks where the servers were a bunch of big HP-9000 systems.
Mark