Raw capture — raw/eng-atlas.md

url: https://eng-atlas.dev/ title: The Software Engineering Practice Atlas author: Unknown (site is unsigned) date_fetched: 2026-08-01 date_published: unknown

The Software Engineering Practice Atlas is an attempt to gather the craft of building software in one place. The practices, principles, patterns, and metrics that experienced engineers, product managers, and leaders reach for are scattered across countless books, talks, and blog posts. This collects them into a single map you can wander through, rather than stumble upon one article at a time.

Scale: 4,654 entries, 5 practice maps, 25 field guides.

The Five Maps

Each map is a board of cards. Pick the one that matches the work you are doing.

1. Engineering (1,512 cards) — Designing, building, releasing, and operating software. Ten quality attributes × the software lifecycle. 53 min guide.
2. Engineering Management (331 cards) — Growing people and running teams. Nine responsibility lanes. 23 min guide.
3. Product Management (414 cards) — What to build and why it matters. Ten responsibility lanes. 31 min guide.
4. Project & Program Management (284 cards) — Coordinating delivery across teams. Seven responsibility lanes. 26 min guide.
5. Research (2,113 cards) — Applied and scientific research: framing, experiment design, and transfer. Ten stages, from framing a question to stewarding a program. 29 min guide.

Domain Guides

Each domain guide walks the same quality attributes as the engineering guide, but only where that domain genuinely reshapes them:

• Distributed Systems (20 min, 7 chapters, 299 cards)
• Data (16 min, 7 chapters, 197 cards)
• ML / AI (12 min, 8 chapters, 133 cards)
• Web (12 min, 5 chapters, 181 cards)
• Mobile (14 min, 7 chapters, 119 cards)
• Backend / Services (15 min, 7 chapters, 291 cards)
• Enterprise (14 min, 7 chapters, 229 cards)
• Cloud Infra (15 min, 7 chapters, 246 cards)

Additional research domain guides: Machine Learning and AI, Data and Statistics, Algorithms and Theory of Computation, Formal Methods, Systems Performance, Databases, Security and Cryptography, Human Subject Research, Robotics, Computational Science and Numerical Simulation, Optimization, Information Retrieval.

Card Format

Every entry says what it is, why it matters, how to apply it, and — the part most references skip — when not to use it. Cards link to related cards, to their sources, and to articles crawled from engineering blogs.

Honest Limitations

Depth varies between entries. Most content is AI generated and has not yet been copy-edited by a human, and some domains are less balanced or complete than others. Treat it as a map to explore from, not gospel, and verify before you rely on it.