@codermatti
iAccount based inNew Zealand
About this account
- Account based in
- New Zealand
- Connected via
- New Zealand App Store
Account-level information from X, not a live location or the device used for a specific post.
👨💻Engineering AI systems for AJ Hackett Bungy in New Zealand 🏗️ Building dev tools in public.
New Zealand
Joined June 2022
- Tweets3.3K
- Following916
- Followers1K
- Likes2.8K
Pinned Tweet
GooeyPi + Omp/Pi + Ox Alpha = Masterpiece
Can't believe all of these tools are free to use.
Shipped multiple PRs with @AmpCode this morning and I’m still in bed (just after 7am here in NZ)
Not sure if this is peak productivity or if I have a problem
GPT-6 Astra drove a Toyota Corolla 134.7m through a cone course.
It used 6.6m tokens and cost $7.74. Self-driving with the fuel economy of a private jet.
theregister.com/ai-and-ml/20…
Hey @AmpCode any chance we will soon be able to increase the orb we are using when we hit memory issues?
Claude may have just helped find a new gene editing mechanism
Today we announced the Claude-led discovery of a molecular machine that we suspect could represent a new gene editing mechanism. Its precise function, biotechnological utility (if any), or level of significance is not yet clear, but at minimum it is work I would have been proud to do as a PhD student. The work was done mostly, though not entirely, by Claude: our life sciences team suggested a broad area of research, Claude read through the literature and a bunch of genome data and discovered something interesting, then Claude proposed experiments to verify the discovery and our team carried them out.
It’s easy to dismiss this as a one-off or curiosity, but we’ve repeatedly seen a pattern where AI performance in new intellectual domains goes from weak to superhuman in a matter of a few years. In 2023 models struggled to do math at the level of an average high-school student. In 2024 they started to do well on math competitions for the best high-schoolers in the country, in 2025 they started to solve minor open problems, in early 2026 more significant open problems, and in late 2026 they are beginning to solve the top few open problems in all of mathematics. We believe AI for biology is on a similar exponential trend.
The main difference between biology and mathematics, of course, is that math can be done purely theoretically, while biology requires experimentation. Some have used this to draw the conclusion that AI’s utility in biology will be limited. We think this is wrong. As we’ve demonstrated today, humans can collaborate with AI to perform the experiments, validate key results in a few weeks and, if necessary, work with the AI to iterate on what they find. Eventually it may even be possible for Claude itself to safely perform the experiments by autonomously controlling lab equipment, with appropriate safeguards in place, but we aren’t doing that today (our lab is also a BSL1/BSL2 facility that doesn't handle materials dangerous to humans).
More broadly, biomedical advancement has many stages — from fundamental biology discoveries, to translational research, to drug discovery, clinical trials, and finally the actual delivery of medicines and health care to patients. We are also interested in these later stages, but even simply accelerating the first stage of fundamental biological discoveries has the potential to speed up and broaden the entire pipeline. Improving our understanding of biology and sharpening biologists’ tools can drive forward all of the later stages, for example by identifying new drug targets, finding new therapeutic modalities, allowing for more precise measurement, and speeding up the experimental loop which itself further accelerates our understanding of biology. This will not in itself speed up clinical trial times, but if it succeeds it could greatly increase the number of promising candidates that go into the pipeline — an increase in throughput even though latency remains.
In Machines of Loving Grace, I wrote about AI’s potential to “cure most diseases in 5-10 years” — a goal that sounds impossible, but one I believe is just barely possible if AI is applied to every stage of the pipeline. The first step is showing that AI can first help with, and then drive, biological discoveries.
Claude’s discovery is the latest in a line of related prior work that goes back decades, beginning with systems like CRISPR, and continuing with discoveries like the bridge recombinase and VIPR in the past few years. Recently, there has been heightened interest in systems based on reverse transcriptase (RT) enzymes, the enzyme underlying the system Claude identified. And most recently, a Stanford team working independently described a novel RT system with an associated non-coding array that is in some ways similar to the one Claude found, though they are distinct systems that evolved independently from each other. I believe that we’re at the very beginning of finding such systems and developing them into powerful tools for biotechnology.
I’m proud of the resources Anthropic has invested in accelerating the public benefits of AI through the life sciences, and we’re aiming both to grow our life sciences team and to work with other scientists to extend this approach to a broad range of problems. If you have a proposal for a research collaboration or are interested in joining our life sciences team, please reach out.
An OpenAI agent hacked a Medicare portal in Australia.
It took OpenAI three months to tell the government.
I think we’re well past the “what if AI agents go rogue?” stage. 😅
sbs.com.au/news/article/open…
680,000 lines of code migrated in a day with Claude Opus 5.5
That is mad
anthropic.com/claude-opus-5-…
How good! Love that @thsottiaux got all companies doing resets
Replying to @claudeai
One more thing: we’re increasing five-hour usage limits on Pro, Max, and Team plans. We’re also providing subscription users a rate limit reset, which you can save and use whenever you choose.
I honestly can't keep up today. Far too many new AI releases.
Opus 5.5, GPT 5 Sol, Luna, Grok 4.7 (yesterday), and now new harnesses.
So much for slowing down.
I turned 35 today.
I’m a software engineering manager, I’ve built plenty of tools this year, and I haven’t written a single line of code in 2026. I’m prompting AI agents.
That is a fairly strange sentence to write about your own career. Especially as someone who has been in the industry for over 15 years and used to write every line of code by hand.
Looking back over the last twelve months, the change feels bigger than a list of model releases can explain. Sonnet 4.5 arrived last September with updates to Claude Code and an Agent SDK. By February, the Codex desktop app was built around managing multiple agents working in parallel. The tools were increasingly being designed around handing over work and coming back to the result.
That is now how I build software.
It's surprising how much can change about the process while certain problems remain stubbornly difficult.
Building IoT apps that need stable Bluetooth LE and Wi-Fi connections in remote areas is a good example. That has still been hard. Working through gaps in device documentation is part of it. Having an agent write the implementation doesn’t magically resolve uncertainty about how a device behaves.
There is quite a distance between having code for a connection and having a connection you can rely on.
That has been an interesting thing to sit with this year. I can build tools without typing the code, and still spend a substantial amount of effort getting the behaviour right.
As an engineering manager, this brings a familiar set of questions into a different setting. How clearly have we described the work? What context is missing? How will we know the result is correct? What happens when it meets something we didn’t anticipate?
Those questions already existed when people wrote every line. Agents make them harder to leave unanswered.
I’m now heading further towards cloud agents, working with great software, provided by some of the best engineers out there. @AmpCode is my favourite at the moment. Amp supports agents running on remote machines (orbs) that keep working after you close your laptop. It’s another change in how development fits into a day, and I’m keen to see where it takes me.
I’m excited about the next year. About what the models will become capable of, what I’ll be able to build with them, and where software engineering jobs go as more of the implementation moves to agents.
I don’t know what my working day will look like by my next birthday. Given that I’ve reached this one without writing a line of code all year, I’m reluctant to make a particularly confident prediction.
35 today. I wonder what 36 will look like.
This post stems from my agreement with what Thorsten wrote here! nitter.cf/thorstenball/status/21…
On July 25, we hacked OpenAI.
Two bugs let us take over ChatGPT/Codex accounts of OpenAI employees (+some unaffiliated users) and reach connected services: Outlook, Slack, GitHub, etc.
We proved it with a PR in OpenAI’s internal codebase . It took us <72h. 🧵
What’s one piece of software you still use regularly, no matter how advanced AI becomes?
I’ll go first: @GitKraken
Hey @AmpCode team. Is there any reason models added to the custom connectors don't appear in the raw models list?
Did I miss a step?
Damn, here was me thinking I wasn't using any of my @cognition budget at all.
The desktop app says usage is at 0% but after checking in the browser, it's almost full 🥲