Published

{{ r.type }}

{{ r.title }}

{{ r.description }}

🎯 Level {{ r.level }}

📘 Chapters {{ r.chapters }}

✍️ Exercises {{ r.exercises }}

📄 Pages {{ r.pages }}

👁 {{ r.views }} views

{{ authorMap[r.author_id].name }}

{{ authorMap[r.author_id].role }}

Natural Progression

Computer science topics build on each other. Skipping fundamentals leads to shallow understanding. Advanced skills only make sense once the basics are solid.

Some areas can be studied independently, but they eventually connect into a unified skill set.

Effective Study Habits

• Learn in small, cumulative steps
• Each step should include practical work
• Use spaced repetition for memorization
• Write your own summaries to reinforce understanding
• Avoid jumping topics without a clear reason
• Keep track of where you left off

Roadmap

1. Programming
   • High-level: Python, Java, C#, C / C++
   • Low-level: x86 / x86_64 Assembly
2. Operating Systems
   • System navigation (sysadmin mindset)
   • Core OS concepts
   • Windows internals
3. Reverse Engineering
   • Static and dynamic analysis
   • Debuggers and disassemblers
4. Networking & Security
   • Metworking fundamentals
   • Pentesting fundamentals

Practical Tips

• Use readability tools (e.g. dark mode extensions)
• Bookmark high-quality resources
• Ask for clarification when stuck, don’t stall indefinitely

Contribution & Style Guide

lowlevelnotes is an open, long-term project. Contributions are welcome, but are expected to meet a high standard of clarity, structure, and intent.

GitHub Contribution Workflow

1. Fork the repository to create your own copy.
2. Create a new branch with a descriptive name.
3. Make your changes — bug fixes, features, or documentation.
4. Commit with a clear, concise commit message.
5. Push the branch to your fork.
6. Create a pull request targeting the main branch.

For more details, see the official GitHub Contribution Guide .

Style Guide

This project was historically built using MkDocs Material . While the frontend has changed, the documentation style remains strict.

• All of the source files have to be written in Markdown (.md)
• Use proper Markdown syntax highlighting.
• Code blocks for readability and practical examples.
• Keep structure consistent and intentional.

Pull Request Guidelines

• Provide a clear, detailed description of what you changed and why.
• Ensure formatting renders correctly before submitting.