Drake Evans (@drakeevans) profile picture

founder @withAUSD. economics & code. formerly: fraxlend author @fraxfinance, engineer at @ADP

New York, NY
Joined January 2014
Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)Photo by Drake Evans (@drakeevans)
Everyone QT'ing OP but this reply is the real way things will go. 3 Predictions: GUIs are here to stay but become custom AI harnesses over time APIs move to building blocks over pure orchestration. They are more important than ever because they are what underpins the MCP/CLI tools etc. Exportable building blocks will become paramount. They let people build their own UIs/orchestration in whatever way they want. The UI is just an opinionated configuration of core capabilities with a display/discovery/harness layer on top. More and more people will want to build these pieces into their own UI or more increasingly their own harness All of this is why you must own the metal to own your own destiny
Replying to @SamBroner
FWIW, my preference would be that every SaaS offers three great experiences with a shared data and permission model: 1. Great app 2. Great APIs/MCPs so I can bring my own agent 3. Great deep linking & exportable components — e.g. help my agent show me “just one thing”
1
1
14
2,178
An affair with a subordinate reflects incredibly poorly on his judgement, impulse control, and risk management in a way the first affair did not. This is directly related to his ability to lead NVIDIA
All the tech people rushing to defend Jensen are off base. As a VC, I get it. He's a generational founder, and there's a deeply-ingrained lesson in tech that founders are almost always the best people to run their companies. I share that intuition. But the board's call here was dead simple: 1. His credibility is shredded. Jensen said two weeks ago that his relationship with Alice Huang was "completely normal and not unusual." Ten days later he admitted the affair. Now there's a second affair, with an exec who reports directly to him. As others have said: "when you find two ants in your kitchen, the best estimate for the ants in your kitchen is not two." 2. He violated export controls and tried to quash the investigation into MegaSpeed, which could be an extremely serious crime. The Trump admin is already signaling that they are going to reverse course on export restrictions because of this scandal. 3. The politics has flipped. His relationship with Trump is no longer the asset it was. The Dems are in control of Congress now and there is furious anti-AI backlash that Nvidia will need to weather. Having been compromised by a Chinese spy and advocating for exports to China makes him totally disqualified on these questions going forward. There is going to be hell to pay over the next few years, and Nvidia needs a CEO who can walk into those hearings with legitimacy. Otherwise this cloud would always hang over him. 4. There's a business to run. The dude already wrote one apology letter. Was the board supposed to wait for him to write a second one? A third? You can't run a $4T company like this. A CEO has to be reliable first and foremost. Once that’s gone, you don’t get it back. Jensen will almost certainly have a second act. But just not as CEO of Nvidia. And anyone calling this a psy-op or a coup should just look at the Polymarket on this. Before the second affair, Jensen was only at 15% to be out as CEO. He could've survived one scandal, and I agreed it'd be foolish to let him go at that point. Easy to argue he was duped and made a mistake. But you don't get two.
3
436
No dependencies includes vendors. We've had CISOs from Fortune 500 on staff at Agora from almost day 1. When weve done diligence on crit vendors (even in auth/custody space) its horrifying what we've found. Even the supposed "best in class" are in shockingly bad shape.
126
Agreed
Let’s be honest. If Jensen had a shit partner he would have never become the superstar he is today. If she gets half in a divorce, she gets half. She married him 8 years before he founded NVIDIA. That woman made him. It’s her half anyway.
2
605
I sent this link to @withAUSD dev team in the early days. Not as a prescription (a lot didnt make sense for our use cases) but as an example of excellence and topics you should have developed a clear thesis about if you want to be elite. github.com/tigerbeetle/tiger… reminded by this @gakonst post
going to make all my out there experiments in Zig TigerStyle Zero Deps w/ DST & report back - first project is a replacement to aerospace (the window manager), codename tatami
1
228
Drake Evans retweeted
in absence of other information, always judge a plan by its outcomes. say what you want about the mandate, it was successful in 1) executing a badly necessary downsizing at the EF, 2) purging unwanted political elements, and 3) increasing ecosystem diversity at the same time. if someone had promised all of these in one swoop a year ago, we'd have called them a genius
17
15
181
12,323
I said this back in August, every task anyone does today (customer/internal) now has 2 products: Data + the actual work. Everything is a harness in the future nitter.gq/drakeevans/status/2092…
2
2
4
294
The stablecoin is the wedge, not the whole business. Drake Evans, co-founder and CTO of Agora, on AUSD, starting at the bottom of the stack, what an OCC national trust bank charter unlocks, and why stablecoin yields will compress. With @notkinsa. Supported by @krakenfx and @trycodex.
2
1
7
218
Drake Evans retweeted
AI can write the software. It can’t get you a bank charter. Our Co-Founder and CTO @drakeevans joined @openinterest_hq to talk about starting with the stablecoin, why it’s the wedge, and what a trust bank charter would mean for builders on AUSD. youtu.be/QyrVS1M5NWw
2
3
11
1,192
Democrats delivering CLARITY was not on my bingo card
🚨SCOOP: House Democrats are discussing plans to expand the Crypto Investor and Consumer Bill of Rights, @RepMaxineWaters’ amendment to the Clarity Act in 2025, into a broader crypto “market structure” bill next Congress. The proposal would fold in Democratic Clarity Act provisions originally offered by Waters in the House (which were not adopted), as well as provisions Senate Democrats were able to agree to with Republicans before the September cloture vote, according to three industry sources who have spoken with Democratic staffers. Some of the proposals under discussion are said to include giving the @SECGov more of a role in supervising the crypto markets, and a more limited role for the @CFTC. Additionally, it’s likely that further ethics provisions will be offered to restrict the crypto activities of President Trump and other federal officials. Republicans are calling this a “messaging bill.”
2
1
13
663
If your company thinks the 512gb m5 Studio is overpriced you're ngmi
1
6
352
I havent yearned for the mines (coding by hand) for years but the final vision of solar makes me miss those days. LSP near and dear to my heart because I started building one as the options were so bad back in 2020, which then led me to static analysis tools AST, CSTs etc etc. So much great learnings came from those efforts
Replying to @gakonst
Solar has an LSP! Check it out here. It's really epic.
1
7
271
Rex + cua spaces would be so nice, every session a sandbox thats either a container,vm,or full machine. Native apps + TUIs all within that nice window manager. Teleport between sessions. Wen
1
1
6
908
Drake Evans retweeted
Agora just got its OCC charter approved. That’s a major step for regulated, on-chain stablecoins. @drakeevans @withAUSD @therollupco
1
7
443
Serif fonts are so back!
Introducing Geist Serif.
4
598
The bigger problem we will have to confront is that serving your product to users is the exact thing that allows them to build it themselves (similar to distillation)
This is the most savage thing I could imagine. A competition to Reverse Engineer your competitor as open source. The internet is getting wild...
1
3
315
My agent just reads the skill file then does it anyway lmao
The skills spec is so broken
1
188
Drake Evans retweeted
forget ARR, this is it
Replying to @trycua
@trycua is like lil wayne in 2007-08, in the middle of generational run and you know its happening
1
6
390
Wait until you hear about harness outside sandbox, full session durability (w/ forking), and boxes that are "ephemeral" but you can come back to forever
My personal sense is: Cloud Agents ("ephemeral", per-PR cloud container) < Local dev < Cloud Agents ("devbox", long-lived, laptop-isomorphic) Unfortunately - many services err towards selling you the former (Cursor, Claude, Codex, Conductor). For the "devbox" style Cloud Agents - I'd recommend Claude remote-control or Paseo. I use the latter. (Cursor-over-SSH or Codex-over-SSH work too ofc) Why is ephemeral so much worse than devbox? There's just a lot of types of debugging, deployment, testing workflows that are SWE, but not exactly "writing a PR" that go much worse w/ ephemerality. OTOH - for devbox-style, the answer is always "just mimic what your laptop does". Some examples: - I want to do `terraform plan` and `terraform apply` with my agent. This means I need to give my agent AWS perms. - How do I do this with a ephemeral cloud agent? Err... I mint long-lived access keys for it - which my infra team doesn't support. Maybe I could copy my personal creds over? What do I do when I have multiple AWS accounts? - How do I do it locally? Easy, `aws sso login`. How do I do it on a devbox? Easy, `aws sso login`. Much like my laptop, I might log into multiple AWS accounts. - I want to iterate on an app that has a DB. How does this work? - Ephemeral: Maybe re-seed the DB each time? Maybe use a novel DB provider w/ forking - but no I need a real DB like Aurora Serverless. I'd rather do PG, so I guess I build some sort of seeding. - Devbox: It's just like using a laptop - long-lived DB, gets interesting state over time. [Related: a lot of the `npm run dev` local-dev stuff is very nice, doing quick preview deploys instead of exposing localhost is bad - it's just never as fast as just HMR. Devbox + tunnel for localhost + agent docs on how to use the tunnel is really sweet] A few others I won't detail: - I want my agent to read my datadog logs to help me debug an issue, how does that work? - I want my agent to set up a new Cloudflare subdomain / worker - I want my agent to be able to hit internal services on my Tailnet - I want an agent-only journal & task-list that is on a separate cadence from my repo (ie: often failed PRs that do not merge still want to write to the journal, and this would make too much PR/commit noise) - I want to build & smoke-test & deploy docker containers, and ephemeral agents run into dind issues. - I want my agent to help me zip up some files, inspect them for a while + put them somewhere else. (likely AWS access bottlenecked?) In general, the core problem ephemeral cloud agents run into is SWE involves a lot of tangential poking through platforms + long-lived access. You want a permissions model that mirrors a laptop (ie: all developer-relevant perms), not a Github CI runner (ie: only app-deployment relevant perms). [A secondary problem is: local state is more nice than it is harmful. It can be harmful for reproducibility, but far more often it's nice for journals, dev DBs, static files] [Another problem is: there's also security concerns about using 3P sandboxes, your infra team might drag their feet, and long-lived boxes are super trivial to self-host - just make an EC2 VM] If you have a phenomenal devprod team, one answer is: "they've provisioned a lot of short-lived workload identities, that you can assign to ephemeral containers". But also ugh - different engineers on different teams have different access - and might not even want all their ephemeral boxes to have complete access? How do you let people configure this smoothly? With devboxes it's easy - folks often just have N devboxes, with different configurations.
1
6
398