John Saigle retweeted
Deterministic Simulation Testing Is For Everyone
outdata.net/blog/261120
John Saigle retweeted
"The most load-bearing question, then, is the morality of the one who wields the ring."
John Saigle retweeted
show this video to anybody that is an old school programmer that hates AI
this is one of the best videos I’ve seen all month.
John Saigle retweeted
I unfortunately can't take seriously the big AI devrels on Twitter. Popular software factory repos just don't compute for me as cred for "How to use AI". The people I trust the most are people focused on correctness whose bottom is on the line. Kernel/Inference folks, TigerBeetle, our own Tempo team etc. Basically systems folks. I believe that 90% of application layer advice out there is garbage and actively distracting you.
John Saigle retweeted
Replying to @bilskirnir3124 @thsottiaux
GrapheneOS code quality has greatly increased due to using frontier models for code review and bug finding. Our port of the Pixel 10 drivers from Linux 6.6 (QPR1) / 6.12 (QPR2) to Linux 6.18 went incredibly smoothly because we were able to find most of the issues in advance.
John Saigle retweeted
There’s no excuse for new software not to be logical, not to be deterministic.
Investing in owning your testing, to be DST-first, and to accelerate the local development velocity of your team, is probably the best technical decision you can make.
John Saigle retweeted
It’s refreshing to have access to, and be able to work with, a team of incredibly passionate and skilled (not to mention human) engineers, who want to break the code, and find bugs as much as you do.
To be clear, machines (like the VOPR and LLMs) are great at exhaustively enumerating bugs, but these things are defense-in-depth:
The principle is that you should always be adding layers, but never replace one layer with another.
For example, don’t replace human review with LLM review, but rather add another layer as defense-in-depth. (The LLM should only be a canary, if it finds anything, you know your other layers failed, and you fix them and invest in them).
At the end of the day, the most valuable software in the world is not valuable because of the “time” it took you to create, but because of the “quality” and value you added.
John Saigle retweeted
Crypto grew up in the Dark Forest, and the entire world is about to find itself there
John Saigle retweeted
Crypto’s irony is that it usually is attacked first and mocked for its operational failures
Yet the competition ends up looted more aggressively later by the same actors (🇰🇵) and reluctantly adopts the security solutions that wouldn’t exist without crypto being attacked first
SCOOP: Major U.S. banks are detecting unauthorized third-party AI agents inside customer accounts, including some attempting to take actions that appear to be independent of user instructions, sources told Axios.
The findings have alarmed banking executives, who are racing to restrict access to their systems as AI moves at a velocity faster than financial institutions can respond, multiple industry and bank executives told Axios.
Several banks are now preparing for worst-case and even “day after” scenarios, including how to rapidly secure or restore customer accounts if things go wrong, the people said.
Several bank executives told Axios they're struggling to distinguish between human users and AI agents. One executive said banks also struggle to determine whether agents are authorized by customers or potentially operating without their permission, more akin to rogue agent behavior.
Read my latest for Axios here: axios.com/2026/10/22/ai-agen…
John Saigle retweeted
There are literally zero moats left unless you go to the portfolio tab on our website those are the only companies with moats
John Saigle retweeted
So many people discovering that the whole Internet is dry tinder and the only thing keeping it from burning is the fact that teenagers haven’t found the matches yet.
John Saigle retweeted
Replying to @trailofbits
This is some work tangentially related from my coworker @johnsaigle.
It ensures lock files are present and actions use them: github.com/asymmetric-resear…
John Saigle retweeted
Replying to @thorstenball
I don’t think we want probabilistic guarantees of memory safety which require inference to imperfectly check.
We likely want a deterministic, fast, sound algorithm you can run locally —which is what the rust compiler mostly gives us today.
John Saigle retweeted
Public service announcement: there is a lot more to security than finding software vulnerabilities. 🫡
John Saigle retweeted
"Today, most tools use put Developer Experience first —remember all the 'easy-to-use' javascript frameworks, then Performance, then Safety; TigerStyle does the opposite order"
youtu.be/qIhAc9Qw_1c?si=2330…
John Saigle retweeted
Mandatory reading. gruhn.me/blog/2026-08-03/
John Saigle retweeted
Replying to @ori_pomerantz
I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That’s the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they’ve had to run the gauntlet of all of my constraints and tests.





























