3 ms·
Yep, you really needed to know the intimate inner workings of the CPU and each digital chip from the keyboard input to the display output to produce code that w
by ChuckNorris89 6y ago
Yep, you really needed to know the intimate inner workings of the CPU and each digital chip from the keyboard input to the display output to produce code that would make a quality product.
It took years of experience that you could only gain through hands-on work, to know how to debug hardware that's why gray-beards are so valued in hardware vs in software where people talk of ageism.
When your hardware/low level software doesn't perform as expected you can't google/stack overflow yourself out of the problem, you need to grab the datasheets, the schematics, an oscilloscope, a soldering iron, hunch over patiently and devise a way to debug the issue out as no one else can help you.
Hardware engineering is now just as challenging as it was back then but due to the commodization of hardware along with the rise of China and the downfall of high-tech giants like IBM, Philips, Siemens, Motorola, Nokia, Blackberry, Nortel, Ericsson, etc most hardware jobs disappeared or moved overseas and pay went significantly downhill compared to software engineering(at least in Europe).
- WWLink 6y agoYou find a lot of these guys in the space industry.
- fma 6y agoI took a Microprocessors course in college (University of Florida) where in the lab you build up an entire board from scratch...including soldering each chip and component. You need to essentially program the drivers from scratch, using assembly...at the end your board has inputs and outputs like a speaker, switches, keypad, infrared remote control...everything was in assembly and you need to RTFM to know how each chip...pin out, clocks etc work. It gives you a great knowledge and appreciate of what goes on beneath the covers. It was a grueling, but satisfying class.