Sometimes. Certain models could be really challenging. What sometimes helps is to take a fresh session, ask it to ask a sub agent how it would run (basically it's session plan), then ask - where does X or Y come from. Sometimes it turns on phrasing, planning docs, word choices.
If you want a fantastic resource for shipping safer Rust you should read @matthiasendler 's https://t.co/mf5rZ1xPr1, then, make your agents read it and capture it into lints, skills, etc and ensure that wherever possible, these rules are enforced.
@gmathis1995@matthiasendler This kind-off drifts and can become a problem from time to time (and crash velocity), sometimes I have to jump in and go clean up overly prescriptive AGENTS.md. It requires a little bit of vigilance, but providing flags like "--test-changed" (git,dep checks), helps.
@gmathis1995@matthiasendler Both. I copied the xtask pattern that projects like rust-analyzer use a long time ago and have a single set of gates that run locally or in CI (I didn't want CI to drift, and I just couldn't get myself to learn all the DSLs), so one "cargo xtask test --full", everywhere
@gmathis1995@matthiasendler We used `syn` to turn some of it into targeted checks. One useful lint flags direct indexing and split_at calls that can panic, suggesting get or split_at_checked instead. The nice thing is that agents don't mind wrestling with `syn` and building out that code.
Just over 11 years ago I was looking for a good holiday project, it came down to learning Go, Swift or Rust - when I read up about it Rust just made deep, deep sense to me - so I dove in.
It was a challenge to master, but it paid off every time over the years. Publishing software without lying awake at nights, reasoning about old stuff, building software on tiny things and big things. I never looked back.
Great to see the momentum gathering around it in this AI age, as well as this cyber security tide that is on us.
It's not perfect, and there's foot guns aplenty, but if you spend the time to learn it - it is the gift that keeps on giving!
@swagitda_ Hearing @joshcorman speak about OODA loops and DevSecOps literally changed my career (and subsequently life) for the better almost 10 years ago. Great to see this reminder, very well written article.