mbriggs (@mbriggs) header
mbriggs (@mbriggs) profile picture

My first name is a random set of numbers and letters and other alphanumerics that changes hourly forever

Montreal
Joined December 2007
Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)Photo by mbriggs (@mbriggs)
Principles of successful "factory" building 1. Don't build a factory, don't think of it as a factory, don't say the word "factory". It's a bad analogy and it puts the emphasis and goals at the wrong parts. Just erase that from your head. You are building focused automations, and getting compounding value from them. 2. Go slow, don't skip steps. If you start feeling a lack of control, that means its time to slow down, and reorient. You should have high confidence, trust, and be deriving value each step of the way. The only way to maintain your ability to judge is to go extremely incrementally. 3. Focus on verification before any other automation. This doesn't mean create-verification-skill from @poteto (although that is excellent and you should check it out), it means taking a step back and thinking about all the ways you could be confident your app works, and getting those into a good spot. For example, the first goal should be a skill that is able to generate unit tests to the point that you are happy with them. If you aren't happy, change the skill, regenerate. Move on, generate another set of unit tests. Rinse and repeat till you build confidence, take bigger swings. Your first milestone is getting to the first atom of verification, which is a test suite you could confidently regenerate if you needed to. 4. Verification (in the broadest sense of the word) is your lever to building trust. This includes your type system, your linter, your architectural choices, infrastructure, test environments and isolation, benchmarking, and automated agent runs. Probably more stuff then that. Focus on automating building that to world class levels. Verification is an easier problem to solve reliably then "all programming work", so start by solving for that. As that gets better, trust will go up. If you can get to the point where "verification passes means my app is functional" you are in the promised land. You wont get there, but that is what you are aiming for. 5. Only trust what is trustworthy. Don't start by saying "i want to fart out an idea and have the agent build it for me" that is the end of the road. Start with something like "when an exception is caught in prod, and the fix is easy, fix it automatically". Start at the edges, as you build trust you can build on top of that. The devil is in the details, but this is my mental model of basically what has been figured out so far. Caveat emptor, I am not sitting at the pinnacle of the mountain and sharing my wisdom, it is largely based on conversations with people I trust further along then me, reading the tea leaves, and matching that to my own experience of successes and failures. Also, we're in a world right now that is changing month over month, I feel like I am trying to articulate current thinking, but the rules could all change tomorrow.
12
1
4
89
6,592
I think this is the future, if not the present, of the role. There are a lot of implications and nuance that flow out of this reality.
allowing nontechnical people to push code without breaking prod the biggest challenge in mamy teams now
38
mbriggs retweeted
the hex iOS app testflight is here it has these features: - dictate right in the keyboard, without jumping to another app - 100% free & on device - music keeps playing as you talk - speak one language → pastes as another leave feedback below testflight.apple.com/join/zk…
iOS keyboard dictation without opening the app coming soon to a hex mobile near you
239
26
32
752
90,484
mbriggs retweeted
The iPhone Duo is the best iPad Apple’s ever made.
297
185
59
6,595
452,637
I wonder if jQuery is set for a comeback
1
168
The current dev machine to benchmark against is the iPhone Duo
44
“And some will build what you never attempted, because nobody told them it was hard” They are going to build it because they understand it better then us, had the idea, and never had the resources to hire us. Or maybe we just weren't good enough, and we blew it. I think ambition of vision is underselling what democratization of software means.
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.
4
3
968
I feel like the sasspocalypse is going to happen but for real this time
39
Anthropic make great models and mid software
34
I don’t think any of us really know what we’re doing yet, but I think all markdown introduces tradeoffs and should be justified. That doesn’t mean don’t check in markdown, it is that you must be able to articulate tangible value that can’t be derived from the code, git, slack, notion, etc
I was wrong. I deleted all ADRs from our codebase. 🔄 49% got superseded 3️⃣ days until superseded 🔜 7% were superseded that same day AI has made "leave it better than you found it" fiscally viable! Your codebase today is your ADR. Old patterns should be short-lived.
47
I was wrong. I deleted all ADRs from our codebase. 🔄 49% got superseded 3️⃣ days until superseded 🔜 7% were superseded that same day AI has made "leave it better than you found it" fiscally viable! Your codebase today is your ADR. Old patterns should be short-lived.
63
19
18
492
96,784
Hot damn I’m seeing first-hand how AI makes non-developers build production software: The personal trainer at my gym has been talking for 3+ years about building a scheduling + workout app one day. Nontechnical. He now has his app!! GitHub + Cloudflare BE&DB + Resend. All built with Claude They guy spent 3 months on it, and has not slept as much as before since getting hooked on building software with AI
263
75
43
2,434
219,570
I'm thinking the duo folio is the way to go if you rarely use the front screen (aka the correct way to be a duo enjoyer)
24
Why aren't custom keybinds a normal part of ADEs?
45
Weird how half the internet seems to have gone down this week due to every major tech company botching server upgrades
1
1
337
mbriggs retweeted
Rewrite it in Rust stopped being a meme the day it started costing $60
13
10
414
12,752
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.
196
209
101
3,927
284,299
Hot take: your AI workflow matters way less than the thing you're building. We've all burned more time tuning the setup than it would've taken to ship. Stop sharpening the axe. Cut the tree.
2
1
1
13
562
The iPhone Duo is not a phone, its an iPad mini you can fold in half and talk into. If that makes you be like "Oh wow, cool, now I don't need a phone!" you are in the target demographic. If you are like "But don't you miss having a phone?" you are not.
1
184
mbriggs retweeted
the problem with markdown is that agents write it as data and read it as code
93
79
20
1,797
111,348
mbriggs retweeted
software factories feel like a temporary problem. the models will learn to build them for you the more interesting question to me is how to build a workspace where agents can collaborate with you
591
345
189
7,573
572,675