My personal view is that good C code looks a lot like Rust where ownership is clear and a borrow checker would approve. The mindset that Rust forces you into is the same one you should be using when writing C.

The longer-term concern is that, if you’re spending late nights learning Rust, it’s probably with the borrow checker. Late nights with C, it’s probably with memory management. One of those two is a bit more applicable to understanding computing at a deeper level.

Outside of that, the key is to keep context as low as possible. The cost of a token increases a lot as context grows. My current favourite approach to that is RPI. Run the Research, Plan, and Implement phases each in their own isolated agent that produces a markdown file for the next.

This post is an AI-generated ad, isn’t it? It’s getting too hard to tell!

A pretty large accusation at the end. That no specific word swaps were given as an example outside the first makes it feel far too clickbate than real though