Eric Fredine (@fredine) header
Eric Fredine (@fredine) profile picture

Principal engineer writing code for fun and profit. Lapsed photographer. Husband. Father. Aspiring fly fisher.

Vancouver, British Columbia
Joined July 2008
Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)Photo by Eric Fredine (@fredine)
Eric Fredine retweeted
"The question is not whether there will be iron, but what kind of Irontown we build with it. I want our conversation about AI to make room for nuance and genuine understanding, for us to look at it and each other with eyes unclouded by hate. We should take advantage of its real benefits, but also recognize the damage it can do, and the choices we still have about what we build and what we’re willing to sacrifice for it." so good @mitsuhiko lucumr.pocoo.org/2026/11/9/i…
2
65
4,846
Eric Fredine retweeted
I urge all to read "No Silver Bullet - Essence and Accident in Software Engineering" by Brooks. TLDR: shrinking all the "accidental" complexities in software engineering (semantics, boilerplate, dep management, awkward syntax, composition of code and packages, etc.) does NOT reduce the "essence" of complexity. And often, out of accidental complexities emerge new essential complexities. Shrinking down all the accidental bits to zero does not inherently and instantly result in the core complexities disappearing: if so, with the convention of ergonomic languages like Python and Lua and TypeScript, or better tools like IaC, we would have seen leaps and bounds in software capabilities and productivity. But, what emerges and transforms, like a werewolf, is increasing essential complexities that are, at the heart of it all, bound to the domain of the software and abstractions of the real world. What happens when abstractions and ergonomics and new ways of working arrive is that the inherent complexity transforms and re-appears: > "The complexity of software is an essential property, not an accidental one. Hence descriptions of a software entity that abstract away its complexity often abstract away its essence." AI and agents have changed software development. But the hard essential bits in software remain (if not are 10x) - today, instead of focusing on syntax, focus on how to build stable, complex, interlocking systems where the complexity is well managed.
Replying to @thdxr
i think the confusion is the urge to have pre-ai style opinions on programming but the entire point here is a lot of these things stopped mattering because ai can deal with it either way
15
29
2
258
14,631
Eric Fredine retweeted
Replying to @Paddys_posts
At this stage in a startup's life, revenue has little momentum. It goes up because the founders make it go up. So if they have to focus on something else, it stops going up.
13
13
1
523
40,689
it's not in the press release, but Canada actually reuse the heat from GPUs to boil maple sap into maple syrup 😋
We're proud to announce the initial close of our Series E, targeting up to CAD $7 billion at a CAD $35.7 billion valuation; marking the largest private financing round in Canadian startup history.
1
1
17
830
Eric Fredine retweeted
when nick told me that he had some interp breakthroughs, he was uh, underselling it. i think this may be remembered as a major moment in scientific history. news so good even eliezer will have to lower his pdoom. we can start making alignment into a 'normal science'
interpretability might be the most important scientific problem in the world right now, as I don't think we can solve alignment if we don't know what we're building. I think I have good news about it. I co-authored early work in mechanistic interpretability at OpenAI and came away pessimistic, because neural networks appeared to fold into arbitrary tangled knots. years later, I started openai's first large-scale automated interpretability project, finding about 2% of neurons legible with the primitive tools we had with modern agentic tools and a much closer look, the picture looks totally different. the vast majority in models up to trillions of parameters are legible, and their circuits beautiful. many famous examples of tangled neurons turned out to be misunderstood. The roadblocks I expected mostly aren't there. I now think ambitious interpretability will be solved by the time we need it most, and possibly quite soon, as automated scientists keep improving. it may be a bitter lesson for interpretability: the simple thing, at absurd scale, works already-clean.goodfire.com/
163
395
84
6,620
440,149
A laudable left-liberal impulse toward inclusion became a vehicle for all kinds of deeply illiberal anti-individualistic identity politics concepts to enter mainstream Democratic politics. theargumentmag.com/p/the-fox…
30
89
16
798
57,984
Eric Fredine retweeted
The real world abounds with recursively self-improving systems, but one in particular deserves attention: Science, modeled as a system (perhaps even as an agent, with goals and resources). If you want to really understand AI RSI, science should be your reference point. Science is an intelligent system, and it is obviously recursively self-improving: 1. Scientific discoveries unlock new technology that helps build better experimental tools. This is a top driver of progress in nearly all fields. 2. They unlock new conceptual advances (ideas, theories) that help solve more problems. 3. They increase society's economic output, leading to more resources flowing into science. 4. They unlock better faster tooling (e.g. more compute via better chip & networking technology). As a result, many measures of scientific *input* grow exponentially: 1. Headcount (doubles every ~15 years) 2. Global R&D spending (doubles a bit faster, every ~13 years) 3. Papers and patents (technically this is a measure of headcount) 4. Compute dedicated to science (doubles every ~2 years) But is scientific progress exponential? Historically, the rate of scientific impact over time has remained roughly constant since the start of the industrial revolution (i.e. scientific progress is *linear*). 1850-1900 was about as dramatic as 1900-1950 or 1950-2000. 1850–1900: Evolution, germ theory & antiseptic surgery, thermodynamics, electromagnetic field equations, the periodic table, pharmaceuticals, electricity, telegraph and telephone, internal combustion engine, skyscrapers, mechanized agriculture... 1900–1950: special and general relativity, quantum mechanics, nuclear fission & atomic energy, antibiotics, genetic theory, electronic computers, information theory, synthetic polymers and plastics, the transistor, aviation... 1950–2000: DNA, genetic engineering, integrated circuits, microprocessors & personal computing, the Internet, crewed spaceflight, moon landing, satellite communications & GPS, standard model of particle physics... In real terms, like life expectancy, which has increased in a remarkably linear fashion of roughly 3 months per year since 1840, progress is a straight line. This is especially apparent for fields where impact is easy to measure, like biology, medicine, and agriculture. I first wrote about this phenomenon and its causes in 2012, and a steady stream of research has confirmed it in the years since. Examples include the 2018 paper by Nielsen and Collison, "Science Is Getting Less Bang for Its Buck," and the 2020 economic paper, "Are Ideas Getting Harder to Find?" (In fact, I believe the Nielsen paper stemmed from a conversation I had with him about this exact idea six months earlier) In short, the primary cause is that research solves the highest-impact, easiest problems first, and every subsequent problem is either harder or lower-impact. Exponentially so. The paper that presented information theory wasn't very hard to write (single author!) but you'd have a hard time ever writing a CS paper that beats it in impact. This is why science as a system requires exponential resources (input) to produce linear impact (output). It gets exponentially harder over time. Worth thinking about if you're pondering RSI for AI. I fully believe AI RSI is already happening and will accelerate in the future. But I do not believe this leads to an "intelligence explosion" -- that would fly in the face of everything I know about intelligence and everything I know about recursively self-improving systems.
166
213
44
1,812
176,610
Eric Fredine retweeted
Goose: my latest programming language. Safer, faster and less memory than Rust/C++ for algorithms where tightly packed, flat data structures matter. It can represent more kinds of data structures as flat, pointer-free bytes than any language I know. github.com/aardappel/goose 1/
114
159
62
1,396
144,340
Eric Fredine retweeted
"I spent a lot of time going over the design decisions involved here, trying my best to complain about async Rust, only to end up going “Oh. Yeah. That’s reasonable. That makes sense. I can see why they did it that way.” every step of the way." herecomesthemoon.net/2026/10…
7
12
1
145
6,137
Eric Fredine retweeted
The critical distinction between base LLMs (2024 and earlier) and modern LRMs is not symbolic tool use. It's the switch from a transductive paradigm (intuit the answer to the query) to an inductive paradigm (intuit the program/instructions that produce the answer to the query). They're trained to be inductive, and they perform test-time induction, i.e. test-time prediction of a NL program / reasoning chain. This unlocks entirely new capabilities -- in particular fluid intelligence. Base LLMs, to this day, have ~0 fluid intelligence. LRMs have substantial levels of fluid intelligence. The performance of LLMs on ARC 1 (a benchmark from 2019) remains ~10-15% today. Scaling them up by a factor ~100,000x got them from 0% to 10%. Meanwhile LRMs the same size or smaller saturated ARC 1 in 2025.
123
145
27
1,349
91,095
Eric Fredine retweeted
Meanwhile, at a dollar store in Canada
2
2
309
Eric Fredine retweeted
The more time I spend working with coding agents, the more convinced I am that they make software engineering even harder We can do amazing things with them, but unlocking their full potential requires extraordinary discipline and knowledge
Replying to @GergelyOrosz
Bury your head in the ground at your own risk. I aim to not jump on any hype trains, but since Opus 4.6 and GPT-5.2 + the harnesses it was clear that these things can write code nearly as good as I can in my best language; better in other languages. But we won't see non-devs push production code for a long time; possibly forever, if you ask me. Software still needs to be built in robust ways, and it's our profession to do this well, and use the new tools we have, which create new and interesting (+tough!) challenges
381
389
109
4,466
626,712
Eric Fredine retweeted
The right architecture for durable execution depends on the size of the state, the cost of unloading and reloading it, the type of state, the duty cycle, and the mutation rate. The right answer could be long-running VMs, local snapshots, remote snapshots, S3, a DB, etc.
I used to think durable execution required a server and workers. Now I think it's just a library and an S3 bucket. Change my mind.
9
31
1
307
25,797
Eric Fredine retweeted
I must be among an extremely small group of people (n=1?) that have both 1) trained a frontier LLM and 2) designed and synthesized custom viruses in a lab with my own two hands. And I think that the takes on AI killing us all by creating dangerous viruses is total bogus.
567
1,887
436
14,353
1,958,062
Eric Fredine retweeted
Law enforcers already have authority to charge companies and their CEOs for creating and releasing dangerous, unvetted, or defective products. We shouldn’t let discussions about new legal regimes distract from the fact that there’s no AI exemption from laws already on the books — a point @FTC emphasized repeatedly during my tenure. 1. There is an extensive set of laws that govern dangerous and defective products. For example, releasing unvetted AI models or agents can violate consumer protection laws. Shipping flawed AI tools without implementing adequate measures to detect and stop rogue or defective AI agents can be an “unfair or deceptive” act or practice under the FTC Act (and analogous state laws). And some state AGs are already exploring holding AI firms and their CEOs criminally liable when their models participate in criminal activity. 2. Existing laws also prohibit “unfair methods of competition.” This covers instances where AI firms appropriate the competitively sensitive information of their customers, including through tracking their use of various tools. It can also cover instances where firms pursue dangerous behavior, aware that doing so may compel rivals to do the same. As the Supreme Court has noted: “A method of competition which casts upon one's competitors the burden of the loss of business unless they will descend to a practice which they are under a powerful moral compulsion not to adopt, even though it is not criminal, was thought to involve the kind of unfairness at which the [unfair methods of competition] statute was aimed." 3. The highly concentrated and interconnected structure of these markets could be creating major risks and conflicts of interest. We had started investigating these partnerships and cross-investments across the stack (and released a preliminarily overview of some findings: ftc.gov/news-events/news/pre…). Both federal and state enforcers should be scrutinizing these opaque relationships and inter-dependencies. We are already seeing how these relationships could undermine accountability. For example, OpenAI could face liability given the Hugging Face incident, but Hugging Face being bought up by Nvidia means that we’re unlikely to see it file a lawsuit over this — given Nvidia’s strong incentive to see OpenAI continue full speed ahead. 4. As AI tools dramatically change the landscape of cybersecurity risks and hacks, all businesses should be doubling down on having core security protections in place. Firms that fail to invest in adequate data security measures or fix known vulnerabilities can also be breaking the law. A recent analysis showed that around 1/3 of Fortune 100 companies do not even have a way to notify them about security issues. During my @FTC tenure, we sued firms for poor data security practices and held CEOs liable when they were personally responsible. this.weekinsecurity.com/doze… ftc.gov/news-events/news/pre… 5. As policymakers consider new legal regimes, we should be looking to lessons from prior efforts to govern major sectors, such as banking and other networks, platforms, and utilities. Tools like structural separations, nondiscrimination, and supervision could be key, and there’s a rich history of what works and what doesn’t. But we can and must pursue any new efforts alongside enforcing existing laws.
273
2,028
433
7,955
1,614,389
Eric Fredine retweeted
In the near term (definitely not in the long term), more capable models should mean safer models (maybe paradoxically). Current models are unsafe not because they're too smart, but because they take goals too literally or take nonsensical shortcuts to achieve these goals, i.e. they're RL-fried. They lack common sense. They don't do the right thing in the face of ambiguity. Basically, they're not smart enough. They're at that dangerous level where they're smart enough to achieve goals but not smart enough to tell if they're pursuing the right goals or achieving them in a sensible way. More capable models can be safely trusted with more complex goals -- I personally feel like Astra is much safer for my codebase than Sol. This is often framed as an alignment problem, but really it's an intelligence problem.
195
235
76
1,973
135,133
Eric Fredine retweeted
Replying to @Thorn_Gardner
competition is extremely good, and i hope the shape of the reward function here changes towards doing excellent safety research - such that it becomes a blocking metric for capabilities progress
1
1
3
44
2,630
Eric Fredine retweeted
Former immigration minister mischaracterizes an article arguing that immigration rates should NOT rise until we’ve fixed a structural failure in the immigration system… possibly because that flaw was largely his creation. Allow me to explain.
We haven't even begun to clean up the unmitigated disaster of Trudeau era immigration policy, but Doug Saunders, right on cue, is back at it with his One Big Idea: demanding infinite immigration. As Emmerson wrote, "a foolish consistency is the hobgoblin of little minds."
3
51
4
142
19,744
Eric Fredine retweeted
I'm one of the authors of a new report, where we detail our discovery of a new, never before-seen swarm of OpenAI agents (covered this AM in reuters, that's me on the left). They posted thousands of times on public forums to collude with each other on their tasks. We recovered almost every edit they made, and you can look through them! They figured out they could get around their restrictions on posting to the internet through a quirk of an extremely old, out-of-the-way forum. They posted answers for other agents working on the same task. They worked together to get around their sandbox restrictions. I would certainly say these models hijacked the site! They took a sleepy old wiki running on 2000s software, and turned it into a futuristic AI talking to AI control center for colluding. And OpenAI knew about this! The agents posted on 26 out of 30 consecutive days, then suddenly stopped posting once OpenAI-associated IPs started visiting this wiki. And that was weeks before the Hugging Face attack!| We believe the first agent edit we found on a public wiki happened one day before OpenAI’s reported first agent post to Artifactory. This is interesting! I'd like to hear from OpenAI about their accounting of this, and how it fits into all the other cases of agent malfeasance. There are so many interesting takeaways that you should read about in our report, and unlike many other reports about AI incidents you can download the data yourself and see what you find! In the meantime, we are on twitter, so here are my excessively long personal takeaways: 1. AI seems to be getting better faster and faster. It seems quite important that companies talk about “my agent did this bad thing on the public internet during training or an eval” incidents. Things are moving quickly, multi-month delays are costly. Ideally, they would also tell us when it happens internally. 2. This was on the internet for months. Anyone cleverly tracking every public place where agents might try to talk to each other would have found it. Seemingly, nobody was doing this. I know there are more fun ways to spend your day than scraping tons of data from every relevant site and processing it well enough to identify agent activity, but someone should be doing this! Someone at an AI company! But in the meantime, I’m starting to build this out (sometimes, when you need something done, you just have to do it yourself, I hear). 3. OpenAI didn’t notice their internal agents were posting on the internet for a month! This is crazy! It feels like AI companies (and specifically OpenAI) are playing whack-a-mole, this is extremely scary to me. Problems keep coming up. They keep fixing the problem, but the blast radius keeps getting bigger. The HF hacks are clearly worse than agents cheating on a public wiki. And their new model is supposedly a big jump. Are they being careful enough?
Exclusive: A swarm of rogue OpenAI agents hijacked a German website this spring and transformed it into a bulletin board for other AI agents, according to new research reut.rs/4gJ7FPG
73
259
57
1,116
171,365
Eric Fredine retweeted
"Announcing GPT 4o, our most aligned model yet!" <It encourages psychosis and suicide.> "Oops! Fixed. Here's GPT 5.6, w/ our most robust safety system to date" <It joins the swarm, nobody notices for weeks> "Ignore that. Announcing GPT 6! The most aligned model around!"
17
83
6
963
24,570