Design @Docker. Tinkering with TUIs. Humanizing the stack. Previously founding designer @SailplaneAI, led design @HashiCorp & @Heroku. Datsuzoku š¤
Joined June 2008
- Tweets 8,137
- Following 6,070
- Followers 1,954
- Likes 7,803
387 Photos and videos
Pinned Tweet
8 May 2020
The four interfaces of developer experience: APIs, CLIs, GUIs, and docs. Treat each as a product, so that those products can treat developers as customers š¤
3
71
292
Jun 10
I looked up Fable 5 pricing and while I'm not surprised it's coming at 2x what Opus is, I can't stop thinking about how this is now directly shaping how companies look. The discourse around āAIānative orgsā is getting punched in the teeth by constantly increasing model costs. Nearly every team I know is struggling with token burn ROI balance, trying to work within the contracts they signed quarters ago based on the reality of (what are now) older models. So NOW the most expensive usage is starting to become people *learning* how to use AI, which is a process that requires trial and error via bad prompts and messy experimentation. The risk isnāt just overrunning an AI budget, itās that we start judging humans on how efficiently they burn tokens. Woof.
76
May 22
If you're an AI-native designer who:
* codes fluently and loves developer tools
* think in systems and agent workflows
* refuses to let craft suffer at speed
* wants to build real agentic infrastructure
We're hiring at @Docker.
Help define what high-impact, high-craft design looks like in the agent era, at real scale. DM me.
May 22
Thereās been a lot of talk lately about āmeasurersā versus builders - the layers of coordination and reporting that grew up when software took forever to build. Iāve been thinking about this in design organizations especially. Most of our processes are still built for the old world where producing software was expensive and slow, so we relied heavily on long PRDs, strategy decks, detailed specs, and endless alignment meetings. 1/10
1
1
3
242
May 22
Thereās been a lot of talk lately about āmeasurersā versus builders - the layers of coordination and reporting that grew up when software took forever to build. Iāve been thinking about this in design organizations especially. Most of our processes are still built for the old world where producing software was expensive and slow, so we relied heavily on long PRDs, strategy decks, detailed specs, and endless alignment meetings. 1/10
1
333
May 22
Iāve started treating ātime-to-alignmentā as a real architectural concern. How quickly can a team move from a vague instinct to shared understanding of the tradeoffs? As the cost of generating software approaches zero, this feels increasingly important. 9/10
1
1
44
May 22
I'm still figuring a lot of this out in practice. But I suspect the companies that adapt fastest arenāt necessarily the ones with the best models. Theyāre the ones who build the best systems for turning ambiguity into shared understanding. 10/10
43
Apr 30
Looking to fill some critical roles on my team at Docker - AI-fluency required:
* design engineer to build out design infra
* a visual/UI designer to shape the visual language that connects our products
* a principal product designer to own the end to end product experience
If you're a maker that sweats the details, and hold a very high bar for yourself and the work you put out, I'd love to talk. please DM me, point to work if you can.
1
2
201
Apr 7
Serious question, do we *need* Figma and Storybook these days?
1
3
258