AI alone is cool. But mastery + creativity + AI hits on a whole different level. Don't let anyone discourage you from pursuing excellence and craft. Keep studying the blade.
The big lesson from AI is that everything is code. A slide deck is code. Design is code. That cool promo video? Code. Excel automation? Code. The universe? Probably made of code too.
@peer_rich kitchen optimization and efficiency is one thing but people really underestimate how much the whole restaurant experience and plating presentation stuff matters tho in a product, doesnt have to be crazy good just you know enough for a user to not think about it being bad at least
OpenClaw is now on iOS + Android 🦞
📱 Native mobile apps, finally
💬 Agents in your pocket
🔔 Channels, tasks, replies on the go
Run agents from wherever your thumbs are.
iOS: https://t.co/7LHHc9htgM
Android: https://t.co/X0Wuh2uA8w
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:
1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales
Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.
A healthy team needs a mix of these, depending on the product:
- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2
Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
vibecoding was never about code
it was the first place people noticed you could stop doing the work and start describing it
every app is becoming an agent's tool
the pattern is everywhere
Eve by @vercel is a step in the right direction, but its incomplete.
a directory is a great way to structure an agent harness. the most important things you need are
1. memory
2. browser
3. tools
4. communication
5. crons & webhooks
6. recursive persistent subagents
but then there's all this other shit you need
1. a watchdog to make sure your agent isn't breaking
2. an auth registry
3. a task registry
4. an artifact system
5. a channel where the agent can request you for stuff that it needs
6. permissions
you also want one mega thread that compacts well, so the agent is truly long running.
Sam Altman is in crypto there’s no way he doesn’t know what he’s doing.
This is some weird tech elite cabal “tell you what we are doing in plain sight” illuminati shit.