I've been writing c my whole career. If you are interested in kernel/driver development or firmware development you're on the right track. But once you have one language down it's a lot easier to pick up others.
At the beginning of your career I would worry less about theory and reading specs and worry more about design patterns, understanding computer architecture, and practicing writing code.
Damn don't talk yourself down like this, maintaining guix packages is cool as hell. It doesn't matter whether your internship gave you a certificate, it's work experience on your resume.
IME design patterns are useless and have heavily fallen out of favor in industry, especially in the past decade where there has been widespread realization that inheritance is absolutely terrible and should be avoided, with the exception of using interfaces.
I've been writing c my whole career. If you are interested in kernel/driver development or firmware development you're on the right track. But once you have one language down it's a lot easier to pick up others.
At the beginning of your career I would worry less about theory and reading specs and worry more about design patterns, understanding computer architecture, and practicing writing code.
deleted by creator
Damn don't talk yourself down like this, maintaining guix packages is cool as hell. It doesn't matter whether your internship gave you a certificate, it's work experience on your resume.
IME design patterns are useless and have heavily fallen out of favor in industry, especially in the past decade where there has been widespread realization that inheritance is absolutely terrible and should be avoided, with the exception of using interfaces.