Mathematics is all you need

A loan officer is writing code and formally verifying it!

You can just fuzz things 🙌

You don't have to test your code at human speed ;)

We should all write better tests! There's a ton of literature about software testing, but most engineers (including Claude) default to example-based testing. Great for regressions, not so much for finding bugs in your implementation. For anything outside of unit or integration tests, the standard response I hear is -'It doesn't work on my code.' So I'll try something - each week I'll share a technique that has made a meaningful difference in how teams build reliable, high-quality software, and I hope it will do the same for you. The first one is - Swarm Testing, inspired by a talk I attended by "Papers We Love". The links to the paper and the blog post are in the comment below.

Verifiers > Plaintext context Having good verification tools helps a lot, eg. if you are doing something with distributed systems, giving claude access to @quint_lang or TLA can help it ideate the design and model check it so it's sure there are no edge cases that may be hard to resolve at implementation time.