Day 1 at @pax8 Beyond is here. 🚀 The https://t.co/MFloaTXbfh team is on the ground in SLC and ready for this morning's keynote. Come find us at booth #201 and let's talk shop. #Pax8Beyond
Updating one ticket shouldn't take seven clicks and three menus. Ask Rev.ii and you get an interactive workspace you can act on without leaving the chat. See it live 👉 https://t.co/t4bsfK5q62
Anthropic has dove an unreal job at papering the earth with enterprise contracts; every company I walk into *just* went “all in on Claude” about to onboard hundreds or thousands of employees while every cutting edge builder I know has moved to codex.
Speed of adoption compounds both ways, if you’re just catching up that cc and opus 4.6 are great, and have decided you’re decided, you’ll be even slower to see the frontier because you’re locked in to one provider’s view of the world.
If you’re always one fragile step into the future, bop around models, know how codex and cowork and ai studio are all going to intersect, etc etc etc you’ll widen the gap of adoption, and adoption > impact.
To the fast & flexible go the spoils.
(But gg Claude!)
Just wiped the Mac Mini I set up for OpenClaw.
I’m turning it into an always-on devbox to use with Codex mobile.
Have a feeling this is gonna be amazing.
It’s remarkable how often you need to be dramatically upgrading your AI architecture given the pace of progress in AI models right now.
If you’re building agents, you basically need to throw away large parts of previous work that you setup to compensate for model limitations every few quarters. The systems you built to mitigate context window limits aren’t useful anymore, and for many use-cases it’s easier just to throw more compute at a problem today in ways that wouldn’t have worked previously.
If you’re deploying agents in a workflow, you likely need to equally be rethinking your core systems at about that same frequency. The way you would deploy agents in an enterprise 18 months ago is entirely different from the best practices that you’d have today.
This is partly why everyone’s working so hard right now. Right as a best practice is solidified, models improve dramatically, and that old work is rendered obsolete. Unclear that this lets up anytime soon, which is why the it pays to be so wired in right now.
@rezoundous Still use n8n, I end up taking repeated scripts/integrations I see between multiple people's OpenClaws in our org and turn those into N8N flows for better logging/supportability.
I think that if companies are not failing at all with their AI efforts it is a sign that they are not being ambitious enough. This is a fundamentally new technology that we do not know how to use well. Achieving breakthroughs will require experimentation, which require failure.
The Forge: two teams, 10 days, one goal... ship it.
Both tied on points. Tiebreaker: one team shipped. Feature is live in prod today.
While others plan, we build.
One of the legacies our former CTO @jasonaoglesby left us is the kick-off of @NotionHQ at https://t.co/sm1a61ck14. It definitely took some change management and showing the art of the possible, but it's caught on fire in the company and can't roll it out fast enough.
I took a break from social media for a few years but am back on X because so many great conversations and news around AI is happening here. Hoping to rebuild my network and learn from the community here.