Portfolio ↗

Quiz

3048 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas3048 Architecture Fundamentals91 Distributed Systems111 Data Architecture100 Cloud Architecture97 Networking96 API & Integration Architecture97 Reliability & Resilience99 Observability102 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering103 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture108 Streaming & Real-Time Data103 Data Governance & Semantics101 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture109 Assurance, Audit & Model Risk108
Difficulty Any beginner intermediate advanced

3 questions in Refactoring.

  1. Refactoring advanced

    An enterprise software vendor of SAP's shape must replace a logging call used at 2,400 sites across 1,100 files owned by 40 teams. The codemod itself takes an afternoon to write. Sequence the change so it lands once and stays landed.

    3 min answer codemodmechanical changebranchinglint
  2. Refactoring advanced

    Figma's database stack grew roughly 100x between 2020 and 2024. Rather than rewriting the application to be shard-aware in one step, the team vertically partitioned first, then introduced logical sharding, where queries still ran against a single database but were routed as if it were already sharded. Why is that intermediate step worth its cost, and what does it find that a cutover cannot?

    3 min answer figmapostgresshardingrefactoring
  3. Refactoring advanced

    Replacing a home-grown money type with a decimal-backed one fails to compile in 180 places across 11 modules the moment you try it. The team's previous attempt lived on a branch for five weeks and was abandoned. Sequence this so it lands and stays landed.

    3 min answer refactoringmikado methodtrunkincremental change