🎙️ How I AI: Claude Duet honest review + Why Reddit built its own AI prototyping tool

We have reached the point in the AI cycle where the novelty of a chat window is officially dead. Founders and engineering leads aren't asking if a model can write a haiku anymore; they are asking how much friction it removes from a sprint. Two recent developments highlight this transition: the launch of Claude's collaborative coding features and Reddit's decision to stop waiting for third-party tools and build their own internal AI prototyping sandbox.

The Fallacy of the All-Purpose Chatbox

For the last year, most teams have been trying to shoehorn LLMs into their existing workflows through simple API calls or browser tabs. It works for a while, but it hits a wall when you try to scale a product. The problem is that general-purpose AI tools are built for everyone, which usually means they aren't optimized for the specific context of your codebase or your user data.

Claude’s recent move toward a more collaborative, "duet-style" coding environment is an attempt to solve this. It isn't just about code generation; it is about reducing the cognitive load of switching between a debugger, a browser, and a chat interface. For a builder, the value isn't in the model's intelligence alone, but in how little you have to explain to it before it becomes useful.

Why Reddit Built Its Own Sandbox

The more interesting story is Reddit. They didn't just buy an enterprise license for a popular LLM and call it a day. They built an internal tool specifically for AI prototyping. This is a move I expect to see from every serious tech company in the next eighteen months.

When you use a third-party interface, you are playing in someone else's playground. You are limited by their UI, their privacy constraints, and their latency. By building an internal sandbox, Reddit allowed their non-technical product managers and designers to test prompts against real-world Reddit data without needing to write a single line of backend code. This democratizes the prototyping phase.

If you are a founder, take note. The bottleneck in AI development right now isn't the model's reasoning capability; it is the time it takes to get a prompt from a "good idea" to a "tested feature." Reddit realized that if every experiment requires a dev ticket, the pace of innovation drops to zero. Their internal tool bypasses the gatekeepers.

The Reality of Claude in the Trenches

There is a lot of noise about Claude being the "developer's choice." While the reasoning capabilities are high, we need to be honest about the limitations. Using an AI as a partner in a "duet" sounds great in a marketing deck, but in practice, it requires a high level of oversight. You cannot just delegate; you have to curate.

The current state of these tools is best described as an extremely fast junior developer who has read every manual but has no common sense. They can refactor a function in seconds, but they might also introduce a legacy bug because they don't understand the nuance of your specific infrastructure. The "duet" approach works only if the human pilot is actually flying the plane.

Context is the Only Competitive Moat

What we are seeing with both Reddit and the latest model updates is a race for context. A model that knows the general rules of Python is a commodity. A model that knows your specific design system, your API documentation, and your user's past behavior is a tool. This is where the industry is moving.

Builders need to stop focusing on which model has the highest benchmark score on a static test. Those numbers are increasingly irrelevant for real-world applications. Instead, focus on the plumbing. How easily can you feed your proprietary data into the model? How quickly can your team iterate on a prompt? If your workflow involves copying and pasting text from a terminal into a browser window, you are already losing.

The Infrastructure Shift

Reddit’s move indicates that the "AI layer" of a company is becoming as foundational as their cloud provider or their database. You don't outsource your core logic to a black box you can't tweak. By building an internal prototyping tool, they’ve created a feedback loop that stays within their walls. This allows for faster failure, which is the only way to get to a successful AI integration.

For startups, the takeaway is clear: don't just build features on top of AI; build the infrastructure that allows you to test those features instantly. If you are waiting for OpenAI or Anthropic to build the perfect interface for your specific business case, you will be waiting forever.

The Skeptical Founder’s View

I remain skeptical of the "AI will write all the code" narrative. We aren't there. What we have is a massive acceleration of the boring stuff. Boilerplate, unit tests, and basic refactoring are essentially solved problems. The hard stuff—architecture, security, and user experience—still requires a human with a stake in the outcome.

Claude and its peers are getting better at the "how," but they are still clueless about the "why." Reddit’s prototyping tool is a way to bridge that gap, letting the people who understand the "why" (the product teams) experiment with the "how" (the AI) without needing a translator.

The value of AI in a build environment is inversely proportional to the amount of friction required to use it.

If a tool requires you to change how you work to accommodate the AI, the tool is broken. The best integrations are the ones that disappear into the background. Reddit’s internal sandbox and the evolution of collaborative coding environments are steps toward that invisibility.

Takeaway for Builders

Stop looking for the perfect model and start building the perfect environment. If your team can’t prototype an AI feature in an afternoon because of technical hurdles or data silos, you are behind. Whether you use Claude, GPT-4, or a local Llama instance is secondary to how fast you can iterate. Context is king, and speed is the only way to find it.

Read the original at Lenny's Newsletter →