I'm leading Scale on @base again.
New vision. Building at Scale.
The @pzeroai build taught us what agentic systems take. We are not keeping that to ourselves.
It goes in a private builders lounge in the Scale Discord. Deep insights. Group calls. One to ones. Private repo access. Grok bot strategies.
I want the next builders on Base in that lounge.
We lead the agentic era from there.
Most DEX tokens pay you to sit in a pool.
We did that for a long time. It does not give anyone a reason to care about the venue. It gives them a reason to leave when the emissions lose value.
What we are building now is the other way around. You buy SCALE to get through the door. Behind it is a gated Discord on a live venue. It teaches you how to build with agents. We help you run your protocol agentically.
Lockers feel this too. Five people buying that door eat a week of emissions. That is demand the farm never created.
Building at Scale. That is the whole sentence.
7,000 SCALE. That is the door.
@mattpocockuk Those old school Java devs knew a thing or too about building software. I went back and studied loads of it a couple of years ago and it totally changed my game.
goated.
@GergelyOrosz I've been saying this for a while. Waterfall is actually better with agents. The only reason it failed is that humans can't hold that capacity all at once.
@DavidKPiano I always say my epitaph will just be a simple checklist:
โ Life
Pretty sure Davidโs will just be a clean state transition:
living + END -> final ๐
What is an implicit state machine?
Your apps are full of state machines, which is the logic that says "when we're in this state, and this event happens, now we're in this state" (given, when, then).
Sometimes those state machines are clearly mapped out (switch statements, reducers, tables/maps, libraries like XState for the more complex ones, etc.) and the logic is explicitly enumerable.
And sometimes it's not. The ad-hoc logic is spread all over the place. That's how developers typically code, and that's how agents typically vibe-code (they learned from you). Those are implicit state machines.
What's wrong with implicit state machines? It's not clear what state transitions are possible, so you might have "allowed" states that should have been impossible without knowing it. Agents make the same mistakes.
You can get all tests passing and your code review agents (even the well-funded ones) can say "LGTM" and you can *still* have very bad bugs because an implicit state machine allowed unexpected or illegal behavior. (Remember the Apple FaceTime bug?)
So yeah, making your app logic explicit is important.
@elonmusk@bot How do you win back trust?
There is no way we can build business processes that can stop working at a whim.
Best product ever invented, Engineering is NOT the problem.
@mattpocockuk Software workplace suits better imo. Build tools and systems that act together to form a workplace with human and AI actors doing their thing.
@flashgorshon I came to this realisation and have gone all in on local this weekend. It's progressed way beyond the last time I looked into it 9 months ago. My goodness ๐ช๐ป
@elonmusk I've been a hardcore cursor user for ~two years and dropped my ultra sub this month. The unified model and grok usage in the same month is too much, we cant trust the direction.
Grok bot is incredible, possibly the best product ever built but it now has zero trust.
@elonmusk I think you dropped the ball here Elon. I know you needed to save cost but rugging usage has me nervous for the future. Why would we build business tools that can be changed without warning at short notice?