3 ms·
There are lots of very good and detailed examples in this article, and some very nice links for those interested in the actual low-level stuff. But I am not su
by wglb 15y ago
There are lots of very good and detailed examples in this article, and some very nice links for those interested in the actual low-level stuff.
But I am not sure where a lot of things he notes were ever "taught" in universities or formally to those of us who were in the trenches. Much of the hard-core low-level stuff was learned either on your own, or when you got into an environment where it was necessary to know.
There are some additional skills that are falling by the wayside as well. One is how to optimize instructions on a type 650 rotating drum computer. Or more realistically, how to program co-routines in an interrupt-driven environment. Or how to write a floating-point division routine if you are working on a 286 target that does not have a 287. Or what order to write items to a disk and where to place them to minimize arm movement in a real-time data-driven system.
I admit that some of these are actually less necessary now due to technology being replaced, or machines being ridiculously faster.
But I was around when those technologies were necessary and useful (well, not the 650, but almost). We built a real-time system in assembler that had to be seriously well-optomized, and we had to modify the operating system to remove hazardous a latency that was fogging our 2ms data sampling rate.
But you know, simultaneously with that were COBOL programmers who had to be schooled in the idea that writing backups to tape was a good idea.
So there always has been a gap--this article suggests that this is something new.
Having said all that, this is an excellent article, as it is a challenge to programmers who would be better, and has a forest of valuable links to learn more. (This site now bookmarked.)
- salem 15y agoI graduated 10 years ago, in Computer Engineering, and much of this low level stuff was covered in core classes, such as Microprocessors & Interfacing, Operating Systems, and Computer Architecture. If one only wanted to study "higher level concepts", or couldn't pass, you switched to computer science...