Most engineering stories start at day one with a clean repo. This one did not, and I think the messy version is the more useful one to read.
I stepped in as CTO at RAQTS, a sports-tech platform that connects players and facilities, during a phase where the stakes were high and there was no room to stop and rebuild. The product already existed. It already had real players and real facilities depending on it. My job was not to design something from scratch. It was to steady something in motion and keep shipping while it ran.
If you have only ever started projects, that distinction sounds academic. It is not. It changes the first thing you do, the first thing you touch, and the order you are allowed to touch things in. Here is what the job actually taught me.
The first task is reading, not writing
When you join a live system, the cost of a careless change is not a failed test. It is a facility that cannot run its session tonight because you shipped a change to a subsystem you did not fully understand yet.
