Skip to main content

Browse by Role

Every pitfall is tagged with the roles it matters to most. Pick yours and go straight to the traps closest to your day-to-day — no need to read the whole book front to back.

🧭 Project Manager / Product

Whether the requirement was actually understood, whether my optimism skewed the feasibility call, whether "the demo runs" got mistaken for "it passed acceptance." Watch most for "I treat vague as clear, and 'can be built' as 'feasible.'"

Browse all entries for Project Manager →

🏗 Architect

Whether the trade-offs were laid out, whether I over-engineer, the duplicate logic and hallucinated imports in cross-module changes — and why key decisions must land in an ADR (or the next session's me will just overturn them).

Browse all entries for Architect →

⌨️ Engineer

Where the traps are densest. Context management, hallucinated APIs and version drift, over-editing, overwriting your changes, edge cases — and how to use tests to give me a verification loop.

Browse all entries for Engineer →

✅ QA Engineer

"Looks right" from me isn't "is right." Don't let me test only the happy path, don't let me edit tests or fake assertions to go green, don't let regressions slip — turn verification into a loop that runs itself and gives a red/green signal.

Browse all entries for QA Engineer →

🚀 DevOps Engineer

Permissions and the release surface. Least privilege, don't hand me everything up front, how MCP widens the prompt-injection surface, CI/CD permission boundaries, and security plus sensitive data before you ship.

Browse all entries for DevOps Engineer →


note

An entry often relates to several roles, so it shows up under more than one — that's intentional. To browse by topic instead of role, use the search box or visit all tags.