Bryan Hirsch (@BryanHirsch) profile picture

Present: https://xitter.cf/t.co/5radCJsI4z. Past: Chief Digital Officer & Founder of MA Digital Service, @Whitehouse44. LinkedIn: https://xitter.cf/t.co/XUsgB5Imys RT ≠ +

Boston, MA
Joined April 2009
Photo by Bryan Hirsch (@BryanHirsch)Photo by Bryan Hirsch (@BryanHirsch)Photo by Bryan Hirsch (@BryanHirsch)Photo by Bryan Hirsch (@BryanHirsch)
Bryan Hirsch retweeted
Rex demo time: magical and automatic remote copy/paste, drag/drop, and port forwarding (e.g. open web servers running on remote machines in your local browser). Plus, showcasing some of the internal plumbing that powers this and how you can hook into it with Lua scripting. Our goal with Superlogical and Rex is for everything to feel local. I've said before: the moment any UI shows a selector between "local" and "cloud", the product has failed. The lines should blur, and we should build the foundational technology that makes it happen performantly, securely, and beautifully.
192
207
99
3,918
277,618
Bryan Hirsch retweeted
.@poteto's talk at AIE Code is excellent. If I had to pick one still from that felt genuinely original, it would be this one: "nuance tends to lead to slop" To increase quality, design API's and automated checks that remove the nuance from agents' decisions. - Ban useEffect - Ban 99% of explanatory comments (they just lead to workarounds) - Create API's that hide complexity from agents Full talk below.
130
122
27
2,843
163,196
Bryan Hirsch 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.
191
319
106
2,918
341,456
Looking forward to trying this!
Tired of walls of markdown? Try an /animatic. I'm working on two skills: - /setup-animatic, that chooses the tooling and sets it up on your machine (or a remote machine) - /animatic, that creates a video ready for upload I've been using them for a while. Here's a preview:
45
Bryan Hirsch retweeted
We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs. Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue). Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main. Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown. The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in. Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way."). This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours. All of this works on mutual trust. It ONLY works with mutual trust. Everyone at all times has to trust that they've got each others back: 1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts). 2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer. 3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly). We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago. In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.
179
196
71
4,628
299,480
“Efficiency for efficiency’s sake is not the goal,” explains Marina Nitze in today’s episode of The Government Fix. Efficiency is about a lot more than obliterating steps in a process. It needs to have an outcomes goal attached to it. 🎧 Out now! bit.ly/3VTRqIY
2
4
303
Bryan Hirsch retweeted
I re-ran an experiment @colin_fraser ran against GPT-4o a while back to see how good it was at adding long numbers, only this time I tried Qwen 3.8 27B running locally in both reasoning and non-reasoning modes simonwillison.net/2026/Oct/4…
114
29
10
475
54,190
Bryan Hirsch retweeted
Every developer needs an AI shed: An always-on machine running on their tailscale network where the majority of their herdr agents are running.
624
358
208
7,757
660,662
Bryan Hirsch retweeted
Oh my god, Firebase’s SDK started to crash ALL iOS apps that were using it, for ALL sessions, just like that, no way for any of these apps to do anything… How amateur is all of this from any SDK, but especially one from a company with as high of an engineering bar like Google…
143
200
98
2,803
609,142
Bryan Hirsch retweeted
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
74
84
23
1,571
340,897
Bryan Hirsch 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
382
390
109
4,464
626,632
Bryan Hirsch retweeted
Omarchy is a perfect fit for the iPad, because tiling already makes the most sense. What an awesome setup!
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
66
52
2
1,356
171,308
Bryan Hirsch retweeted
In 1997, a developer publicly told Steve Jobs he had no idea what he was talking about. Jobs paused and answered with the most important business lesson ever delivered under pressure. Bookmark & watch today, no matter what.
163
1,405
84
14,189
1,033,060
Bryan Hirsch retweeted
Here's a Blender model of a Pluribus themed Fabergé egg I had GPT-6 Astra build - I generated the concept image using ChatGPT Images 2.5, then pasted the image into Codex and told Astra to turn that into a Blender file Details here: simonwillison.net/2026/Sep/9…
68
15
9
152
26,940
Bryan Hirsch retweeted
Imagine a future where we could build homes like cars — one every minute. That's the vision of @BOXABL Co-CEO @GalianoTiramani Homes built on an assembly line, delivered to you. Starting at $60,000. Nasdaq ticker symbol $BXBL* Read disclaimers boxabl.com/ir

1,498
1,971
150
18,156
56,084,653
Bryan Hirsch retweeted
Ghostty (and libghostty!) now has a 100% complete implementation of the Kitty Graphics Protocol. We support every feature, every option. We are the first terminal beyond Kitty to do this. Most terminals stop at basic image placements, then give up on the long tail of other features. Ghostty covers all of them: - Unicode placeholders (so it works in tmux) - Relative placements (so images can be positioned relative to other images) - Animation - Scroll region handling (so images scroll properly with terminal scroll regions) - All transport mediums: shared memory, temp files, etc. - etc... All of these features don't impact steady-state use (CPU or memory, besides raw code size). And for libghostty consumers, you can use the compile-time features flags to disable them completely. I read the spec myself a hundred times. I read Kitty's source code to validate behaviors (our implementation is markedly different, so no GPL violation). I also utilized agents, primarily for validation. I spun Fable and Sol in a loop for 3 weeks (pausing only when their dedicated subs exhausted limits) with a prompt to find mismatches between the spec, Kitty's reference implementation, and Ghostty. And now we're done. Ghostty is the most compliant Kitty Graphics implementation (ignoring Kitty itself of course). And, this is all in libghostty, so now everyone can be perfectly compliant.
82
143
15
3,688
270,557
Bryan Hirsch retweeted
I had Claude Code for web experiment with smolvm as a code execution sandbox Fable 5 spotted that its environment couldn't run that (no /dev/kvm)... so, without asking me first, it wrote a GitHub Actions workflow to run the experiments and pushed that directly to GitHub instead!
140
26
13
294
62,282
Bryan Hirsch retweeted
PSA: If you are tired of Claude-lish or Chat-lish, tell your AI to read the Google Developer Docs Style Guide and build a skill that follows it It’s like magic. Suddenly your AI will make sense again! I’ve tried both and this is much better than the ASD-STE100 Simplified Technical English skill And friends at the labs: please invest more in AI comms skills! A brilliant agentic AI that cannot speak English is dramatically less useful and undermines the utility of RLVR developers.google.com/style
112
217
30
4,166
319,107
Bryan Hirsch retweeted
Really rough day for folks at @github :(
56
30
6
555
95,132