miniblog.

← Back to all posts
Sep 5, 2020 at 05:59
Implementing a formal verification tool for Rust, supporting the same API as property testing libraries! https://alastairreid.github.io/why-not-both/ Requires a remarkable amount of glue code, so this doesn't feel like a mature domain yet.
Rust testing or verifying: Why not both?
Dijkstra famously dissed testing by saying “Program testing can be used to show the presence of bugs, but never to show their absence!” As if you should choose one over the other. I don’t see them as opposites but as complementary techniques that should both be used to improve the quality of your code.

Related Posts

Aug 28, 2026 at 20:47
2
Bevy has an amazing approach to code review that requires two reviews by the community before a maintainer will review and merge. "We let anyone submit PRs without vetting: why is the bar higher for reviewing?" https://shaping.systems/blog/open-code-review/
May 8, 2026 at 14:43
I'm impressed and slightly surprised that I can browse the web even when my local library's wifi blocks detectportal.firefox.com ("Download sites are banned"). It seems that Firefox only requires the website to be redirected when there's a captive portal.
Jan 18, 2026 at 00:30
3
I've been working on a search tool for a website with 9K items and a dumb implementation works just fine. I'd normally gravitate to a library or tool like elasticsearch (ES). Adding custom filters etc is trivial on handrolled code. I wonder what scale requires actual search infra like ES.