Ask HN: What should a systems/low-level software engineer know?

Post by johnNash04 » Wed, Jan 23, 2019, 1:16 AM UTC

lsofzz wrote: post #60

__d wrote: post #25

You should learn C. Ideally, you could learn C++ as well, but I think it's best to learn C first. And then treat C++ as a completely separate language. Rust is a good thing too, but it's a little too soon for it to be broadly useful. Then you should learn Unix. From an understanding point of view, I think it's probably better to learn something like FreeBSD, NetBSD, Xv6 ... Linux is very pragmatic, and very general,…

Nice points. I've prepared what I believe is a good non-exhaustive list without getting very specific. I could be wrong .. - Embarrassingly low-level (chip developers): OS, C/VHDL/Verilog, MA, DS, GPH, EE, Apathy, SE - The in-betweeners (kernel, device, storage developers): OS, C, MA, DS, GPH, Apathy, Crypto, SE - Low-Low-level systems: OS, C, DS, GPH, Apathy, Crypto, SE, FTDS, MSG, NW. - Low-High-level systems: C/Ru…