Reasoning About Async Rust with State Machines
The author discusses how AI assists in writing articles about async Rust, emphasizing that AI is a learning tool and not a shortcut. Each article takes 20-25 hours, with AI used to find examples, analogies, and visuals that make concepts concrete. The author retains judgment and corrections.
On AI assistance
"Bodh" in "AIBodh" means understanding. Since conversational AI first arrived, the main thing I kept coming back to it for was learning, asking, getting it wrong, asking again, until something finally made sense. That turned into a belief I still hold: used well, AI can genuinely help people learn. So I use it for teaching, but not as a shortcut. Each article still takes me 20 to 25 hours. AI is how I get through the parts of writing that are genuinely hard: finding the example where a concept is the obvious answer, the analogy that clicks, the visual that makes it concrete, the pass that cuts the jargon and the bloat. I verify the code runs, I keep the voice mine, and I cut anything that does not help you understand. The judgment and the corrections stay with me. If anything feels off in any section, let me know on Discord and I'll work on it.