Note: Readability, coherent organization, and logical correctness are often more important than obfuscated "hold-my-beer"/Heisenbug code. In general, have a lo

Note: Readability, coherent organization, and logical correctness are often more important than obfuscated "hold-my-beer"/Heisenbug code. In general, have a look at the Standard Template Library or Boost examples directory. Then some unit tests for simple GNU programs similar to what you are building, CLI command source like "ps" for OS interactions, and finally an OS kernel like Linux or *BSD. There are also several online classes offered by linuxfoundation.org etc. Start with a small SBC like a pi4/BeagleBoard, and learn how to snapshot disk images (you will severely damage things while learning). There are also several open syntax formatting standards published by projects (and companies like Google), that will guide you on the local ecosystem. Expect a Hazing in some places, as some folks tend to forget they were students once too. It would also be wise to spend a few days studying security-auditing-tools, as one may learn to mitigate common ways people will try to break stuff. Detection and incident-handling is arguably more important than outright prevention. Happy coding, =)