Skip to content

Hillel Wayne personal blog

Three ways formally verified code can go wrong in practice

buttondown.com published 2025-10-107 min read

"Correct" doesn't mean "correct" when correctly using "correct"

Read on buttondown.com → Discuss on HN (113) Archived copy

Points: 184
HN comments: 113
Submissions: 1
Cited by: 0 commenters

Software Engineering Security & Privacy 2025

On Hacker News

Submitted	Title on HN	Points	Comments
Oct 12, 2025	Three ways formally verified code can go wrong in practice by todsacerdoti	184	113

More from Hillel Wayne

All 39 posts →

Many hard LeetCode problems are easy constraint problems

2025679 points533 comments Software Engineering details

Syntax highlighting is a waste of an information channel (2020)

2025346 points171 comments Software Engineering details

How RSS beat Microsoft

2025315 points181 comments History & Retro Computing details

Unusual Raku Features

2024274 points157 comments Programming Languages details

Why Not Comments

2024261 points277 comments Software Engineering details

The many JavaScript runtimes of the last decade

2025256 points97 comments Web & Frontend details

Related posts from the same era

Ghostty is leaving GitHub

Mitchell Hashimoto20263,521 points1,051 commentscited by 3 details

Astra can read and write weights to improve Qwen

Rikiya Takehi20262,956 points897 comments details

Git commands I run before reading any code

Principal Software Engineer & Codebase Rescue20262,338 points509 comments details

Reverse engineering Ticketmaster's rotating barcodes

conduition20242,305 points714 comments details

Uv is the best thing to happen to the Python ecosystem in a decade

Dr. Emily L. Hunt20252,214 points1,324 comments details

Anthropic acquires Bun

Bun Blog20252,192 points1,072 commentscited by 7 details