This is a favorite of mine since I saw it on here previously. It validates all my experiences as a systems programmer. While others are writing code in the “garbage collected Esperanto runtime”, some of us are knees-deep in oscilloscope hell, trying to figure out why our signals are bunk.
A new takeaway for me this time: it doesn’t have to be this way. We systems programmers don’t have to smugly remind everyone that we work on “harder problems” than they do, or that our errors keep us awake at night. Some of this is unavoidable and the nature of the task at hand, but some of it is our own doing. Better languages and tools can be a huge help here.
A new takeaway for me this time: it doesn’t have to be this way. We systems programmers don’t have to smugly remind everyone that we work on “harder problems” than they do, or that our errors keep us awake at night. Some of this is unavoidable and the nature of the task at hand, but some of it is our own doing. Better languages and tools can be a huge help here.