Learning Paths
Follow curated sequences through the Atlas without treating the knowledge map as one mandatory curriculum.
Personal learning atlas by Tran Trong Thuc · About this Atlas · Atlas last updated Sep 9, 2026
The Software Engineering Map describes what territory exists. Learning paths answer a different question: what sequence is useful for a particular engineering goal?
Paths are curated, not generated from popularity or page count. They may include concepts the Atlas has not covered yet because removing an important gap would make the mental model less honest.
Available content links are derived from canonical MDX placement, so learning-path data does not maintain a second list of lesson URLs.
Modern Web Systems
Build a systems-level mental model of how browsers, protocols, rendering, frontend architecture, and backend boundaries fit together.
Software engineers who want to reason across the full web request and rendering path rather than learn one framework in isolation.
8 / 16 concepts currently covered
Backend Systems
Learn the runtime, data, reliability, and distributed-systems concepts that shape production backend services.
Software engineers who want to design and review backend systems beyond framework-specific controller and ORM mechanics.
9 / 20 concepts currently covered
Cloud Architecture for Software Engineers
Connect application architecture to cloud networking, compute, identity, storage, delivery, observability, and operations.
Application engineers who need cloud architecture judgment without turning the path into provider-specific certification study.
7 / 16 concepts currently covered
AI-Native Software Engineering
Design repositories, workflows, and verification systems so humans and coding agents can change software safely together.
Software engineers using coding agents for substantial implementation who want stronger context, constraints, review, and verification loops.
0 / 14 concepts currently covered
Choose paths by outcome
Use Modern Web Systems to connect browser, network, rendering, frontend, and backend boundaries. Use Backend Systems for request processing, data correctness, async work, and distributed failure. Use Cloud Architecture for Software Engineers to connect application design to infrastructure and operations. Use AI-Native Software Engineering to design repositories and verification loops for humans and coding agents working together.