Noah on Bloomberg: Claude Code and the AI Coding Boom

Noah Brier joined Joe Weisenthal and Tracy Alloway on Bloomberg's Odd Lots podcast to discuss what might be the most important product in AI right now, Claude Code, and why it matters far beyond engineering teams.
A Computer Inside Your Computer
The best way to understand Claude Code, Noah argues, is to think of it as a new kind of computer, one running alongside your existing machine.
Marc Andreessen made a similar observation on John Collison's podcast: the analog for AI isn't the internet. It's the birth of computing itself. We're witnessing "the first major reinvention of the fundamental model of what is a computer in 80 years, going from the Von Neumann architecture to the neural network."
What makes Claude Code special is that it unlocks this new computer by giving it two critical capabilities:
1. File system access: the ability to read and write files directly
2. Unix commands: a vast library of small programs that do one thing really well
This combination solves problems that have plagued AI assistants since their inception. When you paste a document into ChatGPT and ask it to edit something, the AI has to:
1. Read the entire document into its context window (using tokens)
2. "Memorize" the whole thing
3. Generate the entire document again from scratch when outputting
This is expensive and wasteful as the AI is burning tokens to hold content in memory and then rewrite it. With Claude Code, because it has access to Unix commands like cp (copy), it can manipulate files directly on your filesystem without processing them through the neural network. It can copy file A to file B without "reading" and "rewriting" the content through the model.
The result is something that feels less like a chatbot and more like a collaborator who lives in your computer. Noah believes Claude Code is the very shift in representing something different: structured, human-in-the-loop development with proper context engineering. Noah calls it "Level 2/3 assistance", sophisticated pair programming, not autonomous coding. It works for greenfield projects and adapts to legacy codebases.



.png&w=3840&q=75)