
"Finding bugs without running or even looking at code" by Jay Parlar
About this video
Jay Parlar's Strange Loop talk shows how model checkers such as Alloy can find complex bugs in a system's design without running or reading any code. He walks through modeling architectures and checking every possible sequence of operations, including a real security bug and a UI feature-interaction bug.
Why it appears in the archive
HN commenters point to it as the best practical introduction to Alloy and to lightweight formal modeling.
AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.
From the Hacker News discussion
There was a fantastic talk at strangeloop this year on Alloy: [VIDEO] . The speaker used it to find a serious security bug in their live code and a feature interaction bug in their UI that had meant they had been writing broken code for the past _year_. (full disclosure I'm referenced towards the end)
Read original comment ↗I was exposed to alloy by this wonderful video: "Finding bugs without running or even looking at code" by Jay Parlar [VIDEO] I believe the general idea could be applicable in practice for core parts of most businesses software. So now I'm very interested in real world accounts of using alloy like this. Anyone have other posts like this one or experiences to share along these lines?
Read original comment ↗There's a great talk from StrangeLoop[0] where a presenter uses Alloy modelling in exactly the same manner: - generate a couple examples - see something wrong - add a rule - repeat [0] [VIDEO]
Read original comment ↗There is a talk that gives a good overview on Alloy and how useful using something like this is: "Finding bugs without running or even looking at code" by Jay Parlar [VIDEO]
Read original comment ↗