Iracing

I raced 195 times in January. Then islet happened. February dropped to 23 races. March, so far, 16. My iRating has cratered. My incident count is embarrassing. Mae'n dda bod nôl — but being back doesn't mean being good. The numbers don’t lie My recent results read like a comedy of errors. Last ten finishes: P11, P4, P25, P28, P46, P2, P21, P15, P6, P24. Average finish: P18. Average incidents per race in March: 6.7. That P46 was a 13th Week Track Day in a Mercedes-AMG GT4 at VIR where I completed precisely zero competitive laps. The P2 at Okayama? Probably the only clean race in the batch. ...

ira started as a telemetry display. Connect to iRacing's shared memory, show speed and RPM, log to CSV. Useful but narrow. On Saturday it gained race guides, session registrations, owned content detection, and a test suite. Seven commits. One day. A different kind of application. What ira was A C program that did three things well: Read telemetry from iRacing’s shared memory at 60Hz Log that telemetry to CSV for post-session analysis Launch helper applications automatically when a session starts All local. No network calls. No authentication. The iRacing SDK gives you shared memory for free, and everything ira did was built on that foundation. ...