ATechieThought retweeted
Prefer reading to watching?
50 talks from AI Engineer Code Summit, now in writing: illustrated essays, full transcripts and links to watch.
Pick a topic. Find the idea you want to try.
ai.engineer/code/2026#talks
ATechieThought retweeted
the creativity behind this website is fu*king unreal
human-md.ai
ATechieThought retweeted
I just finished talks about my software factories at two conferences. Afterwards a bunch of people came up and told me what they were surprised about. Here is a distillation of what people thought were hot takes from my two talks.
First hot take: I tell everyone to slow down. Most speakers go on about how fast they're going, but I strongly believe in pacing AI outputs to human speeds. I regularly tell AI-pilled CIOs and CTOs to chill: almost nobody is _actually_ going fast with AI. Engineering still moves at engineering speeds, and business moves even slower. The ones pushing too hard are starting to see downtime for it.
If you don't pace your AI to human speeds, everything starts breaking around you, even at small operations like my online video game. I only have about a dozen humans working with my factory, and only a few hundred active old-timer players in the community who get along well, and still, introducing AI has still been very rocky.
My agents have, at times, overwhelmed my players with features, my accountant with emails, my merge queue with tickets, and my machines with load. Agents have pissed off my admins, resulting in name-calling, they've made messes in the game, and they've launched broken OSS without permission. The list goes on.
I can get away with all this chaos because everyone involved in my operation is very forgiving. They're excited by the potential. But even so, I had to learn to slow down, real fast. And so that's what I preach.
Hot take #2: Should you buy a software factory? Do you even need one? No. You probably don't need one. Factories take an extraordinary amount of upkeep. They turn into garbage mountains unless you put a frightening amount of time and tokens into curating them. I had to burn my previous five factories down since it eventually became cheaper to rewrite them than to fix them. So I'm not out there advocating for software factories or swarms just yet. If you do want one, be aware that it is a significant commitment of both money and human leadership to keep one running.
Several people told me that I was the only one who stood up onstage, at either conference, and said Build, don't Buy. But my experience is that software factories grow to be highly bespoke to your domain. Mine is super tangled up with my game, and I think that's inevitable. Because the factory is not just building my product, it's supporting it too. It's a company in a box. And they're easy for Claude to build for you.
Third and arguably hottest take: Next year will have a lot of human/agent and agent/agent office drama, resulting from bringing in AI employees, and it will be gloriously funny, but also frustrating.
Many of you are already on this bandwagon, but everyone next year will have a personal chief-of-staff agent. Busy people, even hobbyists, will have whole entourages of helper agents. The hot take is that people will become so dependent on these little private entourages, that they'll bring them to work. Your people will talk to my people, etc. Whole protocols will emerge for private entourages negotiating work between humans, inside companies big and small.
Nearly all humans will wind up having to start working with AI employees next year, and it'll be the beginning of the biggest cultural change we've seen in a hundred years.
So that's the hot takes. Slow down. Only build a factory if you think you really need one. And focus on empowering yourself with your own agentic chief of staff (or team). Your entourage will define how you work with others, so start by perfecting how you work with them yourself.
ATechieThought retweeted
[new blog post]
Writing as a thinking tool
muratbuffalo.blogspot.com/20…
ATechieThought retweeted
This is 100% true.
Your reliability in general should be *higher* with agent written code, as measured by error rates, SLO violations, client regressions etc.
If you’re having more or equal incidents now than when you were manually writing code, that’s likely a “skill issue”.
Replying to @thorstenball
Agreed. We have shockingly few production errors these days. E.g. panic from a missing nil-check happens once every couple of months, and usually involves legacy code humans partially wrote. At this point, if I write it by hand you are going to get more bugs.
ATechieThought retweeted
This is a great and much needed public service. Thank you Cloudflare!
Introducing Zero Wire: a public vulnerability intelligence feed on @CloudflareRadar, bringing the clarity of a news wire service to critical security developments. cfl.re/4iCvSbj
ATechieThought retweeted
It's been a rough few weeks for security.
I pulled together a guide of the highest-impact actions you can take today:
ATechieThought retweeted
It’s with a very heavy heart that I pass along some gut wrenching news💔💔
The trading community lost a GIANT of a man Oct 31st
Please send your love & positive thoughts to @TaPlot’s family💔🙏
WRO #64 Because We Never Give Up, Hangin' Out with TA Plot youtu.be/zEOlhcW9xE0?is=mssl… via @YouTube
this is basically the bitter lesson at work
the smartest models will need fewer and fewer tokens, they won't need to verify their work or check it for bugs, they will just be right
maybe a hot take but i now consider adversarial reviews mostly a waste of tokens. far better to use those tokens on empirical combined with formal verification. i have updated pstack to use the interrogate skill less, and eventually i think i may remove it altogether
i have found very little value with code review in the abstract, agents tend to just get lost in the nitpicks and yagnis
Irish Olympian and European champion runner Ciara Mageean has died aged 34 rte.ie/sport/athletics/2026/…
ATechieThought retweeted
Quicksand
Quicksand is an async Python API for launching, controlling, snapshotting, and rolling back QEMU virtual machines to provide isolated sandboxes for AI agents without requiring Docker or root privileges.
github.com/microsoft/quicksa…
ATechieThought retweeted
I highly recommend cloudflare's security audit skill: github.com/cloudflare/securi…
Run it on all your software. Run it with the free models. Use it even if you used a model to audit something - it will find much more things. Works in all agent harnesses and is model independent.
ATechieThought retweeted
SlopCodeBench is the most relevant coding agent benchmark left--the top score is 16% vs. 50-75% on other coding benchmarks like Terminal-Bench, FrontierCode, and DeepSWE
summary of how it works: an agent receives a spec for a small program, like a backup scheduler or a mock HTTP server. the agent implements it, then the agent receives a new spec and has to extend the program. this repeats 3-8 times, and with each new spec there are hidden tests that check the new feature and all the old features.
there are a few reasons why I really like it:
1. it comes far closer to simulating real, long-horizon work with new and updating requirements, which is what it’s actually like to work on a codebase vs. solving a single isolated task
2. code coherence, maintainability, and extendability naturally matter more
3. it’s significantly less saturated than the other coding agent benchmarks
full results in the image (credit to @dexhorthy for the benchmark run + charts), the “core” number measures whether the main tests for the new feature pass; the “strict” number is the headline and measures whether every test passes, including regression tests for all earlier features
astra and sol are at the top (interestingly 6.1 is slightly worse than 6 although likely just noise), but given how low the scores are overall + how small the spread is, i don’t think it’s super meaningful yet in terms of determining which model you should use--opus 5.5 is still my daily driver, and i’m kind of surprised it’s not higher
the big caveat imo is that these runs all used the base harness with no customization. i personally think having a couple of core skills + agents.md instructions (planning, verification, etc) is necessary and improves performance, and that improvement is much more likely to show on SlopCodeBench than the other benchmarks
my prediction is that custom context + skills would improve performance by 5 percentage points or more and (hopefully) result in a ranking that’s a better representation of how good different models are to actually use for engineering work
do you think the improvement from proper skills/verification would be more or less than 5%?
ATechieThought retweeted
Replying to @MilesCranmer
Also on Youtube, looks like a good watch. BRB.
youtu.be/uXC7OuCas2Q






























