1. Modular Monolith intermediate

    What mechanically enforces module boundaries in a monolith, and what happens without enforcement?

    2 min answer modular-monolithenforcementdependency-rulesownership
  2. Refactoring intermediate

    A team schedules a large refactoring project and it is repeatedly deprioritised. What approach actually gets refactoring done?

    2 min answer refactoringcontinuous-improvementprioritisationratchet
  3. Service Boundaries intermediate Multiple choice

    For a retailer, should order management, payment and fulfilment be one service or three?

    2 min answer retailboundariescouplingdecision
  4. Service Boundaries intermediate

    Two services share a database because it was faster to build that way. Both teams now block each other on every schema change. What do you do?

    1 min answer couplingdatamicroservicesrefactoring
  5. Contract Tests intermediate

    How does contract testing let two teams deploy independently, and what does it not tell you?

    2 min answer contract-testingdeploymentverificationlimits
  6. SOLID intermediate

    A reviewer rejects a change for violating the single responsibility principle. When is that a substantive objection and when is it cargo cult?

    2 min answer supabasesolidprinciplesreview
  7. SOLID intermediate Multiple choice

    Which SOLID principle has genuine architectural consequences, and which one most often produces harm?

    2 min answer soliddependency-inversionpremature-abstractiondesign
  8. SOLID intermediate

    Which SOLID principle produces the most practical benefit in a large codebase, and which is most often misapplied?

    2 min answer soliddependency-inversionabstractionover-engineering
  9. Technical Debt intermediate

    A team's backlog contains fifty technical debt items. How should they be triaged, and which category is most often mis-sorted?

    2 min answer chargebeetechnical-debtprioritisationinterest
  10. Technical Debt intermediate

    A team's technical debt backlog contains hundreds of items and never shrinks. How should debt be managed?

    2 min answer technical-debtprioritisationcost-of-inactionratchet
  11. Technical Debt intermediate

    Engineering says the codebase is full of technical debt. The business hears "we want to stop delivering and tidy up". How do you reframe it?

    1 min answer meta-skillscommunicationtechnical-debt
  12. Testing Strategies intermediate

    A team's test suite is slow, flaky and gives little confidence. What shape should the strategy have, and what determines it?

    2 min answer lineartestingpyramidflaky