SHIP FAST

“Show the engineers, not just tell. And the worst thing any engine leader could do is just be like, I decree you must use AI. Come on. No one's gonna listen to you.”

“I had landed I was going to the East Coast. I landed, for my flight, got into an Uber, hopped on, like, an entire team, all hands, like, speed run. We call it it was, like, basically, cursor speed run. And I was in the Uber using cursor, putting up the PR. And the goal of the speed run was every single person would just pick up the most trivial thing. It could be like copy change, a bug, whatever, and just put up the PR. And we ended up, I think, in fifteen minutes I think a 100 people had joined. In fifteen minutes, we ended up putting up, like, 70 PRs. And we broke GitHub too, which was cool because we learned, like, our infrastructure needed improvement.”

“We're calling something the Enso Drop. Now the name might change actually in the next couple of weeks, but this is what we have internally so far. We're in a very unique position that we have so many protocols that use our protocol. So we have 125 plus, I believe it's even 130 plus now. You can access over 250 plus on-chain protocols. Now, we interact with their contracts and we get air drops. So we're able to now start offering to the users that secure the Enso Network by delegate staking them their ability to claim other air drops. Now, I believe this is one of the largest mechanisms in the whole space if you're able to get access to over 370 plus potential air drops.”

“Now, how to flourish and create the ideas? I think you can't. You've got to keep them far, far away from the crypto industry. You've got to keep them further away from crypto Twitter as possible because they will just recycle, recycle, recycle. They need to really come up with their own innovative ideas. I was on crypto Twitter back then, 2016 I was like, oh, let's do decentralized roulette table. Roubette nowadays pretty much to some degree. I think keep them far away from crypto Twitter for as long as possible and just have really good mentors that can support them on their developer journey.”

“Brutally honest, we need products that people want. You know, the same money that cycles through DeFi, it's all the same people. Like you see money going TVL up or TVL down there, that's because this is backroom agreements of, hey, I want this APY or I want this extra yield that's not public and I'll put $500 million in your protocol. It's just the same people using it. So I think what we need to do for more people to use crypto is one, give products they actually want to use and two, make it seamless. Like they shouldn't need to care about chains.”

“Cursor has, like, great analytics. Right? And so you go to the admin panel, you look at the analytics, and, you know, awesomely, they let you download into CSV. I was like, what if I just use cursor to figure out what my team is doing in terms of using cursor, but not in just, like, from a vanity metric point of view of, like, lines of code committed by AI. I think that's, like, kind of misleading, actually digging more into, how they're using Cursor and how do we sort of, like, replicate power users.”

“One of the things I really like to do is to ask the model to introspect on its own behaviors. So sometimes when I notice that the model does something unexpected, like, for example, there's, like, situations where the model will make a front end change and run tests, but not actually use the UI. It's actually pretty useful to ask the model to reflect on why I did this. And sometimes they'll say that, hey. There was, like, something confusing in the system prompt, or I didn't realize that, the front end verification was, like, part of this task.”

“I'm prompting, reviewing, troubleshooting, and shipping in real time, all through natural language.”

“I think the real value capture will be the fat engine thesis, which I've just made up on the spot is Enso. If you're able to be that connectivity glue and that one tool that abstracts all of it away, it's the superpower if you have tens of millions of apps that are building atop of you. We could in theory dictate in the future, if base doesn't give us incentives, we won't route people to base. I'm not saying that we will do that, but these abstraction layers will ultimately have to control over the chains. I think ultimately, the more higher that we go up in the stack, the less control that the chains will have, and these abstraction tools will actually have a lot more control than they will, because you can just direct it away from them.”

“We have a project called Onplug. They built their MVP without Enso. I believe it was seven months. Then we approached the team and said, hey, you're building really cool stuff. Like you're building Zapier, drag and drop automation and crypto, and it's never been done before. Why don't you just use us and get access to all of Onchain through one tool? They were able to rebuild all their integration suites in a day and a half. They reduced the development timeline from seven months to a day and a half.”

“I'm using AI to build an entire B2B visitor ID to outbound system in under 10 minutes, something that would normally take developers weeks to ship.”

“For Cloud Code, what we do is we actually ship almost all of our features in Research Preview. We clearly brand this when we ship something so that users know that this is an early product. This is just an idea. This is just something that we're trying to get feedback on and iterating on, and that this might not be supported forever. And what this does is it reduces our commitment for shipping something. We can just get something out in a week or two.”

“Enso has been around four and a half years. And we've never had one exploit. You know, not one. We've handled over $17 billion. We've done, I believe as of to date, there's 10 audits publicly. So the way that we kind of view this is our view in the future should be never write a smart contract again. A developer that is in the Web2 world that wants to interface on chain, they don't need to understand smart contracts and they do not need to write smart contracts to interact with smart contracts. If you write a smart contract that interacts with another one, that's creating another layer of security issues.”

“It's pretty important to build products that don't necessarily work yet so that you know, okay, what is missing, for this product to work? And then with the newest model, you can just swap it into the prototype you've already made and see, okay, does this new model close that gap?”

“This isn't theory. This is why context matters when you're doing this type of planning.”

“The nuclear option is I threaten it, and I say, Claude, if I'm using, like, Claude Opus for 4.5 high, like, okay. I'm gonna stop using you, Claude. I'm gonna switch to Gemini, and then it gets its shit together.”

“When people think about quad and quad code, this is one of the things that people bring up the most where they just really love that quad is like it's it's like lighthearted and fun, but it also is extremely competent at your task. People really like, like, Claude's low ego. And so if you tell it, hey. You did this thing wrong. It's, like, truly sorry. It's like, oh, shoot. Like, thanks for telling me. Like, let me fix it. Let's work together.”

“Then the review time, like, all my devs complain. Review times take too long. We found some solutions, actually. I think we were doing average of, like, a hundred and fifty hours, like, was the cycle time for a PR review because there was so much. We reduced it by 10 x down to, like, fifteen hours or so, roughly.”

“The technology is already here... cutting AI token costs.”

“I invented this role called super builder. And the single job single most important job of a Super Builder is to create more Super Builders. So we we hired our first Super Builder and they, we we talked about some ideas and one of the biggest things because most of our company uses Slack. We're all in Slack. And Slack, you know, I'm strong it's like strong believer is just a bunch of humans pretending to be systems. Right? And the cost of writing something in Slack is zero, but the cost of answering something in Slack is enormous, and most of it is noise.”

“Last night, I was work where we have this code with cloud conference coming up, and there's a few talks that I'm giving there. I have my Google Drive connected. I have Slack connected. Alex, who's our product marketer, put together a draft of what the points that we that he thinks we should cover are. And so I just, like, fed this all into Cowork. I told Cowork the narrative that I want to tell, and it actually just worked for an hour. It it walked through Twitter to see what we launched. It looked through our evergreen launch room. And it synthesized all this together to this 20 page deck that I woke up to this morning.”

“Mission means that teams are willing to make sacrifices that hurt their own goals and their own KRs in service of Anthropic's goals and Anthropic's KRs. And people are very happy to make those trade offs. So, like, an extreme example is if Cloud Code failed, but Anthropic succeeded, I would be extremely happy. And, like, we're like, the whole team is very willing to make decisions that follow that chain of thought.”

“One of the largest DeFi launches and chains of this whole cycle, they had had an incentive mechanism for depositing funds on Ethereum, and those funds needed to be migrated from Ethereum to Berachain and then executed into all of the brand new protocols that didn't exist up until the chain was live. And somebody has handled all of that execution underneath. And these executions were not just swapping from token A to token B, we were bridging, then lend, then borrow, leverage loop, then enter into one-sided LP, so forth and so forth, right? This was handled fully by Enso. Not many people know this. They assumed this is Royco, they assumed it's Boyco. That really is just an interface. It was all of Enso's logic underneath. And we safely and securely moved over $3.1 billion into over 80 plus unique different DeFi combinations.”

“Just do things. I think there's a lot of value in, like, first principles thinking. And if if you, like, if you know what you're optimizing for and you have, like, strong first principles, then you can normally deduce what the right, like, course of action is and be able to clearly articulate that to all the stakeholders. And then you should just, like, do it. Like, I think jobs are fake. If you understand the constraints, you can figure out what you can do and then just, like, try to do it quickly, learn from the mistakes, and apologize or fix them if you did something wrong.”

“I think now with AI and with how much that has accelerated engineering and with how quickly the model capabilities are improving, the timelines for a lot of our product features have gone down from six months to one month and sometimes to one week or even one day. And with that, we actually need to make sure that products ship quite quickly. And what that means is as a PM, there should be less emphasis on making sure that you're aligning your, like, multi quarter roadmaps with your partner teams and more emphasis on, okay, how can we figure out the fastest way to get something out the door?”

“I would also push listeners towards focusing on bringing your automations from, okay, this is a cool concept to, like, hey, this actually works a 100% of the time. Like, sometimes I see users trying to automate something, getting it to, like, 95% accuracy, and then giving up on it. And this if an automation doesn't work a 100% of the time, it's not really an automation. And that last five to 10% does take more time.”

“On our team, we're pretty focused on hiring engineers with great product taste. This this way, we can reduce the amount of overhead for shipping any product. Like, there are many engineers on our team who are fully able to end to end go from see user feedback on Twitter through to, like, ship a product at the end of the week with almost no product involvement. And this, I think, is actually, like, the most efficient way to ship something.”

“The trick here, why Slack, is because Slack is how things go viral within your company. If you have pulled out the magic into some separate tool that others can't see, it doesn't happen. And so by getting things into Slack, people just like, holy shit. This is possible. Let's go.”

“Letting the agents work in parallel... reviewing what got built.”

“So we immediately looked into this when we saw it. We realized that this was the result of human error. There is, a human working with Cloud to write a PR. This was just an update to how we release our packages. And it actually went through two layers of human review. And so the this was a result of human error, and we've hardened our processes to make sure that it doesn't happen in the future.”

“Where did we all individually learn about how to build code? The reality is, it's YouTube. That's where people go and they watch it. How many Web3 companies do you see that actually have, not all, like, wait, let me rephrase. Every Web3 company has YouTube videos and they have zero distribution, right? Zero. Where do people go to learn? They go to YouTube, they go to Code Academy, they go to Udemy, they go to coding boot camps, coding tutorials and so forth. So we're fortunate that we also know people inside of the Web2 developer relations communities that have a large, large, large YouTube communities.”

“I was on a call with with, like, a a user of our product. Right? And they're like, hey. It'd be cool if you, like, changed x, y, and z. And what literally, while I was on the call, I just put up a PR and pushed it. And they're like, before the call ended, it was thirty minutes. I was like, just, you know, reload the app. It's fixed.”

“I love food and wine. I really do. And, like, I've done, like, sommelier training, etcetera, etcetera. With my friend in New York, we went to some, like, champagne tasting. And so, like, I just took notes. There's, like, this whole notebook. Effectively, then I just, like, popped this right in. And I said, here are a bunch of champagnes that I tasted. Figure out from my notes, like, what are my taste preferences?”