I'm considering diving into the OS API but I'm a bit worried about job prospects. Is there a significant difference in career opportunities if I focus on learning the OS API before mastering the standard library?
2 Answers
When learning to code, I usually pick up what I need as I go along. If I find I'm using something a lot, it tends to stick in my memory. But it really depends on your goals!
Totally get that! Learning as you go works well.
Your question's a bit broad, and to give really solid advice, it might help to clarify a few things. For starters, which OS API are you referring to? Every OS like Windows or Linux has its own. On the flip side, which standard library do you have in mind? Each programming language has a different one. Learning an OS API typically focuses on one operating system, which can limit job opportunities since there aren’t as many roles focused solely on that. In contrast, mastering a programming language along with its standard library allows you to create applications that run across various operating systems. So, if you're considering long-term projects and career paths, I’d suggest starting with a programming language and its standard library first, maybe C, and then diving into the OS API later on once you have a solid foundation. It'll open up more possibilities!
Got it! Just to clarify, I'm looking into C++ and specifically the Windows OS API.
Thanks for sharing your approach! What do you find you use the most in your projects?