I'm really fascinated by Systems Programming after enjoying my Operating Systems and Programming classes in college. I recently picked up the 'Operating Systems: Three Easy Pieces' book, but I'm struggling to find practical ways to apply the theory I've learned. I'm curious about what kind of projects people usually build in this area. Do most beginners start with tutorials, or do they dive right into the theory and try to replicate what they learn? If anyone has some personal experiences or paths they followed to get started in this field, I'd really appreciate it!
1 Answer
When you’re starting in Systems Programming, it really helps to narrow down what interests you the most. Systems programming covers a lot of ground, like operating systems, low-level tools, compilers, device drivers, and game engines. Pick one area to focus on. For instance, if you're drawn to driver development, you might want to choose a platform, either Windows or Linux, and find beginner tutorials specific to that. There are lots of resources out there for writing drivers or even for working with embedded systems.
Do you think it’s better to specialize in one area rather than being a jack-of-all-trades? I like a few of the topics you mentioned, but I’m worried that not specializing might be a disadvantage in the long run.