Building Cricket XI with AI: Lessons on State Models and Architectural Bugs
OfficeParticular3805 · reddit · 2026-08-20
The author shares their experience building Cricket XI, a browser-based drafting and simulation game, using AI-assisted development (Lovable, React, TypeScript). While UI generation was easy, handling complex game logic—playoff qualifications, NRR calculations, and background AI matches—resulted in numerous bugs. The key architectural lesson was that the UI shouldn't decide tournament progression. The solution involved decoupling the UI from the logic, creating a dedicated Tournament Engine to manage state and fixtures. The author poses a question for the community: when using AI coding agents, should you iterate through bugs one by one or establish a formal domain/state model first?
More from coding & agent
- 电商 Chatbot 小知识库：用 MCP 还是 RAG？ — rouge818 · 2026-08-20
- Compound Engineering reduces skill size by ~71% — danshipper · 2026-08-20
- Simulating Multi-Agent Turf Wars in r/place: Only 0.49% Overwrites — infoxiao · 2026-08-20
- John Carmack: Spend More Time in Debuggers Than Writing Code — tetsuoai · 2026-08-20
- AWS AgentCore adds runtime domain and date filters for Web Search — AWS ML Blog · 2026-08-20
- Delegate Pattern in Practice: Have Fable Spawn 5 Opus Workers to Iterate UI Designs — kevinkern · 2026-08-20