I much prefer lower level programming, preferably programming the hardware I designed. I know the hardware limitations, side effects, and overall the how-to behind the hardware that allows the software to do its thing. Most software engineers I know have no want to understand the underlying mechanics (they're certainly capable of it - they just don't care).
I'm currently trapped in a "devops full stack" with much of the tooling as NIH. My routine day is a mix of keeping the trains rolling on time, and getting horrid stuff like " my $database_root_password = <password> " out of SVN...
I keep applying to positions in my wider local area (Midwest). But so far, only headhunters that want to waste my time with endless "pre-interviews". Tomorrow, it's back to tickets, high-ho!
I much prefer lower level programming, preferably programming the hardware I designed. I know the hardware limitations, side effects, and overall the how-to behind the hardware that allows the software to do its thing. Most software engineers I know have no want to understand the underlying mechanics (they're certainly capable of it - they just don't care).
I'm currently trapped in a "devops full stack" with much of the tooling as NIH. My routine day is a mix of keeping the trains rolling on time, and getting horrid stuff like " my $database_root_password = <password> " out of SVN...
I keep applying to positions in my wider local area (Midwest). But so far, only headhunters that want to waste my time with endless "pre-interviews". Tomorrow, it's back to tickets, high-ho!