We’re gonna need to account for people who are more output productive able to put their community on their backs, legislatively.
Michael? retweeted
I don't want flying cars.
I want clean water.
I want a stable climate.
I want bees to survive.
Damn I’ve stopped building UIs in favor of MCP tools.
Still probably need some UIs though, but maybe only in dynamic forms and data displays via agent chat.
Might just be something the core harness will handle by default based on the situation though.
Ask your agents to render large data set charts using canvas instead of SVG.
Instant performance boost.
Michael? retweeted
Everyone in AI is building for everyone else in AI.
We're building for your group chat.
Introducing Charming ✨ Personal apps for us normies.
Make an app for your book club, a meal planner for your family, go wild (it's free!)
Build in Claude/ChatGPT, share like a Google Doc
This might happen at larger scale too
we've mostly gotten past the slop issue in this new world of working together with AI
the next problem is people keep accidentally undoing functionality
this is happening because everyone is more in everyone else's business. hit an issue? fix it right away without nagging anyone
the problem is it's unclear how intentional the current behavior is and what absolutely should not be rolled back
you can say tests should be this. but they don't capture the fact that you discarded seemingly valid solutions 1-4 and settled on 5. someone later (an agent) might thing "oh 3 is simpler"
any additional document also doesn't feel like it solves the problem because it's yet another thing that can drift
where is the source of truth for how your software is supposed to work?










