I’ve been building a project called Recticode. It’s a fully CLI-based platform where you practise fixing real-world style bugs instead of solving algorithm puzzles. You install it, run a command, and you’re dropped into a broken system. Examples of current challenges: a rate limiter that never actually rate limits a job queue with a hidden race condition subtle state and logic bugs that only appear after multiple operations You don’t write code from scratch. You: read unfamiliar code trace behaviour find the real issue fix it without rewriting everything I built it because most real dev work is debugging existing code in a terminal, not solving clean, isolated problems in a browser. Each challenge is small and self-contained, so you can finish one in a short session. It’s still early, but the first challenges are live. I'd genuinely love feedback from web devs: does CLI-first make it more interesting? what kinds of production-style bugs would you want to practise?…