6 ms·
I agree with all your points, but just want to add that I've seen very ugly code from EE-types (I'm a EE). An outstanding board design and audio/video engineer
by jmaygarden 15y ago
I agree with all your points, but just want to add that I've seen very ugly code from EE-types (I'm a EE). An outstanding board design and audio/video engineer I worked with avoided loops whenever possible cost because they "made the code confusing." However, his FPGA code was immaculate. I chalked it up to a parallel versus sequential thought process that mirrors the differences between hardware and software.
- numeromancer 15y agoI chalked it up to a parallel versus sequential thought process that mirrors the differences between hardware and software. I don't think this is an essential difference. Programming has preferred the sequential models of computation, but more as a fashion than a necessity. Now, Turing's empire wanes as Church's empire waxes, and those parallel elements of computation that the hardware has hidden from software for so long can no longer be sequestered in silicon.
- zwieback 15y agoYes, I've seen this too. Many EEs with strong skills in low level FW design and HDLs lack software engineering skills. The computer engineering degrees try to bridge the two camps but ultimately there's only so much you can learn in a finite amount of time. I've drifted from ME to controls to FW and SW engineering over the last 20 years.