Building at @shopify. Creator of @tailwindcss. Listener of Slayer. Austin 3:16.
Joined July 2012
- Tweets42.8K
- Following833
- Followers304K
- Likes14.4K
Starting a new model lab, we're focused on training models that put the arrow in the right place in select menus.
So far no other lab has been able to do it, but I think we can with enough funding.
People say educational content is dead but I bought this immediately.
You just have to teach the things people are craving to learn, and that’s changed.
I’ve been working on something new: aiforui.dev/
AI for UI has 28 skills and 20 lessons on building great interfaces with AI.
More than 3,000 people have enrolled so far. It’s $299 instead of $399 until early access closes on Friday.
The full course opens in 2027.
Adam Wathan retweeted
For the work I do, I can’t see why I’d develop locally anymore.
Why mess with worktrees when every thread can get its own computer?
The agent installs whatever it needs. Need ClickHouse or Kafka or Elasticsearch or Go or Rust or Python? Install it. Who cares? Zero cruft on my machine.
This is such a great listen.
21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.
@sqs and @thorstenball on how the Amp team works:
Still find prompting UI tweaks to be way too slow compared to direct manipulation like in a design tool.
What's your work flow for fine-tuning UI details in code without being the victim of the brutal agent feedback loop?
The urge to withhold information from the AI to try and get it to prove to you that it's not stupid instead of just telling it what you think it should do…
If you want to play with features like this sooner, use @paper.
Adam Wathan retweeted
No pull requests, no code review. We push to main.
Our agents read production logs, watch deploys, grant feature flags, and check their own work end to end.
Here's how we do that:
Spend more time shopping for the gym than training in the gym but do still train 😄
Easy 320 x 10 squat today, hard 195 x 5 overhead press 🥵
Relocating my gym to a different space in the house and have spent way too much time researching rolled flooring options.
Everyone does the black with white speckle thing but doing some crude mockups today and I think I’m going light greige 👌🏻
Adam Wathan retweeted
If I bought a new laptop today, I don't think I would install any local dev tools / languages at all. I’d push all my dev work, open source included, to cloud agents.
I think I could do everything I currently do with nothing but Laravel Cloud and @AmpCode Orbs.
Going to try to go cloud-only this week.
Building software in anything other than @AmpCode orbs feels like eating broken glass in comparison.
But it’s frustratingly one of those “you can’t understand why it’s better until you just use it” tools, a lot like Tailwind was.
Use it, and be ruined.
Adam Wathan retweeted
Paper Mono!
sooo excited to finally release our free and beautiful mono font
it works incredibly well for design, coding, and even prose, and it’s packed with features: variable font weight, coding ligatures, duospacing (!) for long-form text, and more.
sound on:
Seeing what they were working on here is what really made me realize what a great home Shopify would be for our team.
Incredible work by everyone involved, and excited to help push stuff like this further 🙌🏻
When I built @kotn’s first store 12 years ago, I knew how to code and it still took me two weeks just to get to something OK, years to get to something I liked.
We built the tool I wish I had back then. Here’s Canvas.
I shipped a change to a PHP 5 + Node 8 project the other night that would’ve been a nightmare without Amp and Orbs. As if I want to figure out how to install and run that shit in 2026.
With orbs it just worked, no configuration, it just figured out how to create an environment where everything ran and I could preview my changes effortlessly.
If you are excited about Codex Cloud I am begging you to please use @AmpCode.
It is so obviously the closest to what the future of building with agents (especially on teams) looks like.
Threads are the new PR, and everyone on the team should be able to see them.