Is it okay to work as a systems programmer?

Question

System Programming

I'm going to go to university to be a system programmer.
Tell us about the specifics of this qualification, what are the difficulties that distinguish it from other qualifications, pluses and minuses.

Answer 1

If you enter the “system programmer”, they will show you a couple of examples of how to write in C, maybe they will show you all sorts of assemblers, explain how a computer works, talk about discreteness, algorithms, data structures, talk about graph theory, network topologies and other interesting pieces. Such knowledge is very useful for any programmer.
Just don't think that you will be taught to work at a university, and even so that you can go exclusively to the "system programmer" and you won't even notice this smooth transition.
Mom's friends will ask you to reinstall Windows.
Friends will say through their teeth "you've settled in well, you sit warm all day, you press the buttons"
Mom will boastfully tell the guests about you, and you will be
embarrassed Europe went to live, homosexual, probably"
Only if you are a complete misanthrope

Answer 2

System programmers are practically extinct as a class.
This is terminology from the 1970s.
What is the name of the programmer's specialization in the learning process - then, when you start working, it will not matter.

Answer 3

Eh, nostalgia... The book "ES COMPUTER. System programmer's guide. Programs IMASPZAP / IMGSADMP " is still on the table . And I really used them :)
Terminology, by the way, from the 90s - it was then that I worked as a system programmer. Now there is no such profession. There is anyone - a system administrator, a system architect, there are all kinds of programmers - but there are no system programmers. They died out like mammoths as unnecessary. In fact, they did what the current admins do - they installed and configured the OS, VM, system programs, they had to deeply know the operation of the computer - because they wrote, among other things, readers, headers and other crap that worked inside the OS (kernel modules - if according to the current ). Only they did not work with iron - there were special people for this ...
Specificity? Well, most likely everything is the same - assembler, knowledge of computer architecture, ability to work directly with hardware, necessarily C, pointers, memory models, etc. Development of drivers, kernel modules, OS components, possibly microcontrollers, all sorts of raspberries :) An interesting thing - if you are interested. No interactive, no UI/UX