pull down to refresh

Quick Take

  • Coinbase CEO Brian Armstrong said 40% of daily code written at the crypto exchange is now AI-generated, on course to reach his more than 50% target by October.
  • Armstrong mandated Coinbase staff to begin using AI tools last month, firing those who did not comply.
Coinbase's artificial intelligence push is accelerating, with 40% of daily code written at the crypto exchange giant now AI-generated, according to the firm's CEO, Brian Armstrong.
"[Approximately] 40% of daily code written at Coinbase is AI-generated. I want to get it to over 50% by October," Armstrong posted to X late Wednesday. "Obviously it needs to be reviewed and understood, and not all areas of the business can use AI-generated code. But we should be using it responsibly as much as we possibly can."
Coinbase is rapidly adopting AI to make its engineers "AI-natives," according to its approach and risk framework toward the new technology, rolling out tools like Cursor, Copilot, and internal integrations to speed development across the software lifecycle, using AI as an accelerator.
If you've used an ai integrated IDE I don't think you'd find this surprising. A lot of code is boilerplate, and the AI lets you easily autocomplete all that boilerplate
reply
But isn't what you describe "AI assisted", as an evolution from "macro assisted"? I'd not call that "AI generated".
reply
274 sats \ 5 replies \ @freetx 4 Sep
I think <tab>-<complete> style AI coding is actually sustainable and can yield great results. Its really uncanny when you start making a change in something like Cursor and AI picks up on your intent and suddenly starts making suggested edits that are all coherent to your intention.
I think vibe / prompt coding can be useful for getting 0.0.1 version bootstrapped and immediately functional, however has very very low percentage of being sustainable after a few versions.
For an existing project, new features can be vibe-coded into existence, but then it needs to quickly transition to <tab-complete> (ai assisted) to actually work as an integrated component long term.
Basically (as you've said), we have 2 differing styles of AI-coding currently happening, but we haven't yet developed the best practices methodology on when/where to use each.
reply
So we've come to basically 3 variations:
  1. AI-assisted completion
  2. AI-assisted coding (you're more likely to understand what you're coding here)
  3. Vibe coding
I fully agree that completion is sustainable and the second variation, assisted coding, isn't much different from someone doing C&P from stackexchange, perhaps even a little more advanced even, so that's manageable; but it could still be debt, especially when refactoring. I must admit that I really like the "let's discuss this code" use-case. This is much better than having to browse reference sites and a great improvement when you're learning (which you always are.)
Vibe coding currently isn't practical for anything past prototyping and those are throwaway prototypes at that. Anything complex that for example needs concurrency control is in my experience until now problematic for LLMs, including Claude 3.7 and 4, and Qwen3 coder. I think this is also risky with #2.
reply
I think vibe coding has its use cases. As a teacher, I've always wanted to come up with these little interactive examples. Vibe coding makes it way faster to do that. In fact, that single page static website I mentioned was exactly such a use case. But you're right, for larger projects it's nowhere near "there" yet.
reply
It definitely does, as long as you never remotely suggest that anyone should run that code. lol
reply
I mean, it runs on their browsers when they visit the page, I guess? haha
reply
I've only really tried vibe coding (from scratch) once, and it actually worked pretty well. But it was a single page static site, no database or complicated state management needed.
I use the <tab>-<complete> version of AI assisted coding all the time now though, and it's hit or miss. I do think it's pretty impressive how it picks up my intent sometimes. At other times, I roll my eyes and wonder what it's thinking.
reply
That's basically my point. Depending on how Brian Armstrong was measuring it, it may or may not be accurate to say that 40% of the code was "made by AI". It was made by humans, except the AI just assisted with the typing of what the human was gonna type anyway
reply
I think he's in desperate need for attention and he's mostly just babbling, especially since quality > source. But I agree with you that:
the AI just assisted with the typing of what the human was gonna type anyway
if that's the case then fine, but then why is AI-generated code a metric at all? The only correct metric for this is imho: problems solved per day without regressions.
reply
Never used it. Thanks for clearing that up.
reply
I agree. But very often code that matters and separates a good codebase from a crappy codebase are the ones least likely to be in a training dataset (hence, AI output).
Besides, new and better languages, design patterns, libraries are coming out everyday, along with breaking API changes of existing contracts. So the implications for AI generated codes?
reply
33 sats \ 1 reply \ @grayruby 23h
I can beat that. 100% of Stacker Sports code is AI-generated. Coinbase is living in the past.
reply
ahahah! you are an ai agent bot. i know it
reply
Translation: "40% of the code we add each day is debt, and I want to get it to 50%"
debt good 🙃
reply
He's a clown
reply
Pretty sure many companies are doing the same, especially Microsoft their new updates are often very buggy
reply