Best Resources for Learning Essential Computer Science Topics

For cybersecurity and code safety, start with learning the OWASP Top 10, focusing on buffer overflows and input validation. Also, if you're coding in C/C++, tools like Valgrind can help with memory issues.

For your gaps, consider these:
- **Testing**: *The Pragmatic Programmer* has great insights, and look into pytest or JUnit for practical testing techniques.
- **Debugging**: Forget print statements—learning tools like gdb or using IDE debuggers will save you time.
- **Error handling**: Language specifics matter, but there are also general patterns you should learn, like failing fast.

At your stage, shift your focus from learning more languages to mastering core engineering practices:
- **Testing**: *Test-Driven Development by Example* is a fantastic read.
- **Debugging**: Get comfy with gdb or lldb instead of relying on print statements.
- **Error Handling**: *Clean Code* by Martin covers great practical patterns.
- **Security**: *The Web Application Hacker’s Handbook* builds a strong security mindset, even if you’re not in web development.
- **Reading Code**: Pick a well-written repo and examine it slowly for understanding.
Overall, building a solid, non-trivial project will often teach you more than simply learning theory.

I'll break it down for you:
1. **Code testing**: As a former AWS backend engineer, I always used unit tests in Java with frameworks like JUnit. No matter what language you use, check out the documentation for the unit testing tool specific to that language.
2. **Debugging**: Instead of sticking to print statements, try using your IDE's debugger. Setting breakpoints makes it much easier to navigate through large codebases.
3. **Error handling**: You should use exceptions for serious errors. For more mundane issues, return error codes or objects. Starting with fatal assertions is a good way to get accustomed to error catching.
4. **Code safety**: Memory issues and proper handling can really make or break your applications—especially in C/C++. Be careful with things like out-of-bounds access!
5. **Reading source code**: It often helps to skim code initially to get a sense of functionality and then go line-by-line when you need to understand specific changes. Talking to the original author, when possible, is also huge!

You’re in a great position already! Here are a couple of books I recommend:
- *The Pragmatic Programmer*
- *Clean Code*
Also, make sure you learn how to use a real debugger and start with smaller code repositories when reading other people's work. The practical experience will definitely help you develop further.

For code reading, you might want to try out r/runable! You can paste code snippets or repositories there, and it’ll help explain their structure and flow. The insights it offers could be super handy when you're feeling overwhelmed.