Lenny RachitskyModify

2026-06-01 23:01:46

Building an iPhone app with zero technical skills | Bryce Rattner Keithley

Brought to you by:

• WorkOS—Make your app enterprise-ready today

• Metaview—The agentic recruiting platform for winning teams

Bryce Rattner Keithley spent her career in talent and recruiting and had never written a line of code. Then she used AI to build Daily Hundred, a fitness app with custom AI-generated videos of animals doing exercises, and shipped it to the App Store. In this episode, Bryce shares the exact workflow she used with Replit, Claude, Gemini, Higgsfield, and Kling; why being non-technical became an advantage; and what her journey reveals about how AI is changing who gets to build software.

Biggest takeaways:

1. You can build and ship a production iPhone app with zero technical background. Bryce spent her entire career in talent and recruiting, had never written code, and still managed to build Daily Hundred—a fitness app with custom AI-generated videos—and get it approved in the App Store. The entire process took a few months of weekend work.

2. The workflow that worked: Claude as architect, Claude Code as engineer, Terminal as executor. Bryce used regular Claude as her “friend in the cockpit” to plan what to do and how to approach problems. Claude would tell her when to use Claude Code to write actual code. She’d bring the code back to Claude for confirmation, then Claude would tell her what to paste into Terminal. This three-step dance—plan, execute, deploy—let her ship production code without having to know exactly how it all worked.

3. Screenshots and iteration are your best debugging tools. When AI wasn’t understanding what Bryce wanted, she’d either get more literal in her descriptions, completely restart the prompt (not just edit it), or send screenshots showing what she was seeing. Sometimes she’d even draw what she wanted or photograph her own starting position to give the AI a visual reference. The key was trying different approaches rather than getting stuck in one failed pattern.

4. The role of technical expertise is fundamentally changing. Bryce observed that engineers who come into technical interviews focused only on finding a working solution fastest are missing the point—“the robots can find a working solution faster than they can.” The human role has shifted to something broader: understanding the full suite of tools, knowing when to use AI versus when to step in personally, and bringing taste and judgment to the process. What got people here won’t get them there.

5. Hiring for adaptability and openness matters more than ever. In Bryce’s view, people who get territorial about what they used to do or what other people used to do will struggle with relevance. The winners will be those with “the humility and the curiosity to work with others in ways that you haven’t before” and who recognize that “people can contribute in ways that they haven’t before.” The best idea should win, regardless of where it comes from.

The Codex feature that works while you sleep

Brought to you by:

• Mercury—Radically different banking loved by over 300K entrepreneurs

Claire Vo breaks down one of her favorite Codex features: /goal. In this solo episode, she shows how Goals turn AI from a tool you have to constantly babysit into an agent that can work for hours on multi-step tasks. She walks through real examples, including eliminating Sentry errors, cleaning nearly 4,000 emails, and organizing Linear tasks, and shares the six-part framework to write Goals that actually run.

Biggest takeaways:

1. Goals enable AI to work autonomously for hours without supervision. Claire ran a goal in Codex that worked for five hours and 45 minutes—the longest she’s ever had an AI agent run successfully. Unlike standard prompts that require turn-by-turn interaction, Goals create a loop where the AI works, verifies, checks, and continues until it hits the defined outcome.

2. The difference between a prompt and a Goal is fundamental. A prompt is an instruction of what to do (“Rewrite this code”). A Goal is a description of what a good outcome looks like and how to get there (“Reduce P95 checkout latency below a defined threshold while keeping the correctness suite green”).

3. Claire eliminated hundreds of error logs by pointing Goals at her Sentry data. She gave Codex access to every trace of invalid operations, then set a goal: categorize each issue, fix it, then replay all historical examples until every error is solved. The result: zero errors remaining, and instead of bandaid fixes scattered throughout the code, she got a systematic, intelligent framework.

4. Goals work incredibly well for non-technical tasks. Claire cleaned 3,900 emails down to 68 in under four hours by setting a simple goal: categorize all emails, unsubscribe from unnecessary ones, and clean up the inbox. The AI read every email, created labels, clicked unsubscribe links, and left her with only the emails requiring judgment.

5. Strong Goals have six key components: outcome (what should be true when done), verification (how to test it), constraints (what can’t regress), boundaries (what tools and files to use), iteration policy (how to decide what to try next), and stopping conditions (when to ask for help). Product managers who’ve written good OKRs will recognize this framework immediately.

6. Working with Goals feels like managing a colleague, not babysitting a tool. You assign a task, the AI goes away for the time required (whether that’s 30 minutes or five hours), and comes back with completed work for you to review. Claire found herself “twiddling her thumbs” because so much of the work was now handled autonomously.

7. Goals aren’t token-cheap, but they’re worth it. Claire’s email cleanup used about 6 million tokens over four hours. But the alternative—manually categorizing thousands of emails or chasing down hundreds of error logs—would take far longer and be far more tedious.

Claude Opus 4.8 is here. Is it as good as they say?

Claire put Anthropic’s new Opus 4.8 model through real coding, design, and strategy tests across Claude Code and Claude Cowork. She shares where the model shines, where it breaks down, how it compares to Opus 4.7, and what builders should know before using it in production.

Biggest takeaways:

1. The voice and ergonomics are excellent. Opus 4.8 is easy to read, doesn’t have “slop tells,” is token-efficient, and feels conversational without being annoying. It talks enough but not too much, and with fast mode enabled, the experience is snappy. The writing quality is strong and the model follows instructions well.

2. Anthropic is shipping new features alongside Opus 4.8 that expand agentic capabilities. Claude Code now has dynamic workflows that let you spin off hundreds of parallel sub-agents. Both Claude.ai and Cowork now offer effort control from low to max, giving users more control over how deeply the model thinks through problems.

3. Use Opus 4.8 for greenfield prototypes and design work, but test carefully for production codebases. The model excels at one-shot features, has improved design aesthetics (no more italicized emphasis words), and is good at tool use. But for existing codebases, edge cases, and strategy work requiring numerical analysis, you’ll need careful prompting and should double-check anywhere the model expresses high confidence.

4. The model hallucinates when it gets stuck, which is a significant regression. Claire experienced straight-up hallucinations multiple times—something she hadn’t seen in a very long time with modern models. When debugging, Opus 4.8 would make up explanations based on hypotheses rather than actual data. It would confidently state things like “No, I didn’t search GitHub” or “No, I didn’t actually validate that bug” when asked to verify its work.

5. Opus 4.8 struggles to orient itself in existing codebases. When Claire asked it to rebase branches and fix conflicts in her production codebase, it required cycle after cycle of fixes because it kept shipping edge-case bugs. The model couldn’t understand the elevation at which it should be operating or how to properly insert itself into existing code.

6. The model isn’t ambitious enough for truly agentic work. Claire asked it to suggest fun things to build that would impress a 9-year-old, pushing it to explore the edges of agentic coding. While it shipped working code, the results were serviceable but not impressive—not the 10x agentic coding experience she expected from a state-of-the-art model.

7. For business strategy work, Opus 4.7 significantly outperforms Opus 4.8. Claire tested both models on the same strategy prompt, giving them access to three months of business context. Opus 4.7 delivered numbers-anchored, structured analysis rooted in real data. Opus 4.8 was hand-wavy, over-rotated on small data points, and had a harder time discovering relevant information.

If you’re enjoying these episodes, reply and let me know what you’d love to learn more about: AI workflows, hiring, growth, product strategy—anything.

Catch you next week,
Lenny

P.S. Want every new episode delivered the moment it drops? Hit “Follow” on your favorite podcast app.

2026-06-01 20:04:51

Bryce Rattner Keithley has spent her career in talent and recruiting, working with technical leaders but never writing a line of code herself. Yet she managed to build Daily Hundred—a fitness app featuring custom AI-generated videos of anthropomorphic animals demonstrating exercises—and ship it to the App Store before her software engineer friends. Using Replit, Claude, Gemini, and a relentless beginner’s mindset, Bryce proves that in the AI era, execution is no longer the constraint on good ideas.

What you’ll learn:

1. How to build and ship an iPhone app using Replit without any coding knowledge

2. The step-by-step process for creating custom AI-generated workout videos by combining Gemini images with real exercise footage

3. How to use Claude as your technical architect and Claude Code as your software engineer

4. How to navigate App Store submission requirements (including fixing rejection feedback)

5. Why being hyper-literal in your prompts unlocks better AI results

6. Why a beginner’s mind is actually an advantage when building with AI tools

Brought to you by:

WorkOS—Make your app enterprise-ready today

Metaview—The agentic recruiting platform for winning teams

In this episode, we cover:

(00:00) Introduction to Bryce and Daily Hundred

(04:48) Building with Replit

(06:16) The beginner’s mindset advantage

(11:17) Creating anthropomorphic animals

(22:55) Moving from static image to video

(27:15) The floating genie and other anthropomorphic animal generations

(30:46) Shifting from web app to App Store submission

(36:24) User feedback

(37:41) Lightning round and final thoughts

Tools referenced:

• Replit: https://replit.com/

• Lovable: https://lovable.dev/

• Claude: https://claude.ai/

• Claude Code: https://claude.ai/code

• Gemini: https://gemini.google.com/

• Higgsfield: https://higgsfield.ai/

• Kling: https://kling.ai/

• Railway: https://railway.app/

• TestFlight: https://developer.apple.com/testflight/

Other references:

• How a 91-year-old vibe coded a complex event management system using Claude and Replit | John Blackman: https://www.lennysnewsletter.com/p/how-a-91-year-old-vibe-coded-a-complex

• What Got You Here Won’t Get You There: https://www.amazon.com/What-Got-Here-Wont-There/dp/1401301304

• How Women Rise: https://www.amazon.com/How-Women-Rise-Holding-Careers/dp/0316440124

• A Whole New Mind: https://www.amazon.com/Whole-New-Mind-Right-Brainers-Future/dp/1594481717

• How to Win Friends and Influence People: https://www.amazon.com/How-Win-Friends-Influence-People/dp/0671027034

Where to find Bryce Rattner Keithley:

LinkedIn: https://www.linkedin.com/in/brycerattner/

GitHub: https://github.com/brk-bot/

Daily Hundred on the App Store: https://apps.apple.com/us/app/daily100-fitness-challenge/id6762108062

Where to find Claire Vo:

ChatPRD: https://www.chatprd.ai/

Website: https://clairevo.com/

LinkedIn: https://www.linkedin.com/in/clairevo/

X: https://x.com/clairevo

Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

2026-05-31 20:31:43

Benedict Evans is an independent analyst and former partner at Andreessen Horowitz, where he spent years as their in-house “thinker” tracking the most important technology trends. For the past six years, he’s been publishing deeply researched presentations on where tech is heading, most recently focused on AI’s transformation of the economy. His work is read by founders, investors, and operators trying to make sense of a noisy field. His most controversial opinion: AI is as big a deal as the internet or mobile—and only as big.

In our in-depth conversation, we discuss:

1. Why we’re in “1997” for AI—early, exciting, and deeply uncertain about what comes next

2. Where value will actually accrue in the AI stack

3. The anti-AI backlash, and where it may lead

4. The surprising boom in consulting and professional services at AI companies

5. Why distribution is becoming the ultimate moat as software gets easier to build

6. Why the right question about your job isn’t “What percent can AI do?” but “Is this a task or a job?”

7. Why things will probably be okay—and what you need to do to prepare

Brought to you by:

WorkOS—Make your app enterprise-ready, with SSO, SCIM, RBAC, and more

Vanta—Automate compliance, manage risk, and accelerate trust with AI

Where to find Benedict Evans:

• LinkedIn: https://www.linkedin.com/in/benedictevans

• Newsletter: https://www.ben-evans.com/newsletter

• Website: https://www.ben-evans.com

Referenced:

• Andreessen Horowitz: https://a16z.com

• AI Eats the World: https://youtu.be/niJpDnNtNp4

• VisiCalc: https://en.wikipedia.org/wiki/VisiCalc

• McKinsey & Company: https://www.mckinsey.com

• Bain & Company: https://www.bain.com

• Accenture: https://www.accenture.com

• Jevons paradox: https://en.wikipedia.org/wiki/Jevons_paradox

• Benedict’s post on LinkedIn about Excel: https://www.linkedin.com/posts/benedictevans_younger-people-may-not-believe-this-but-activity-7303217994459938816-PNqu

• The AI-native startup: 5 products, 7-figure revenue, 100% AI-written code | Dan Shipper (co-founder/CEO of Every): https://www.lennysnewsletter.com/p/inside-every-dan-shipper

• Dario Amodei on X: https://x.com/DarioAmodei

• Marc Andreessen: The real AI boom hasn’t even started yet: https://www.lennysnewsletter.com/p/marc-andreessen-the-real-ai-boom

• Frame.io: https://frame.io

• Food Marketing Institute: https://en.wikipedia.org/wiki/Food_Marketing_Institute

• Llama: https://www.llama.com

• Steven Sinofsky on X: https://x.com/stevesi

• Drake meme: https://imgflip.com/memegenerator/343699919/Drake-Hotline-Bling-Transparent-Background

• Ex-Google CEO Gets Booed While Discussing AI in Commencement Speech | WSJ News: https://www.youtube.com/watch?v=tNH43a1EI7s

• Jonathan Swift’s quote: https://www.goodreads.com/quotes/9838985-you-cannot-reason-a-person-out-of-a-position-he

• George Carlin’s quote: https://www.brainyquote.com/quotes/george_carlin_391403

• Fujitsu: https://global.fujitsu

• O*NET OnLine: https://www.onetonline.org

• Pete Holmes’s website: https://peteholmes.com

• The Seventh Seal: https://www.imdb.com/title/tt0050976

• Ericsson R310s phone: https://en.wikipedia.org/wiki/Ericsson_R310s

• i-mate phone: https://en.wikipedia.org/wiki/I-mate

• J-Phone: https://www.mobilephonemuseum.com/phone-detail/j-phone-j-t06

Recommended books:

• Three Men in a Boat: https://www.amazon.com/Three-Men-Boat-Jerome-K/dp/1512099899

• Nature’s Metropolis: Chicago and the Great West: https://www.amazon.com/Natures-Metropolis-Chicago-Great-West/dp/0393308731

Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

Lenny may be an investor in the companies discussed.

My biggest takeaways from this conversation:

Read more

2026-05-31 00:43:36

👋 Hello and welcome to this week’s edition of ✨ Community Wisdom ✨ a subscriber-only email, delivered every Saturday, highlighting the most helpful conversations in our members-only Slack community.

Read more

2026-05-29 05:35:07

I got a few hours of early-access testing with Anthropic’s newly released model Opus 4.8. I walk through real coding, design, and strategy tasks across Claude Code and Claude Cowork, and give you my unfiltered view on what impressed me and what didn’t.

What you’ll learn:

1. Where Opus 4.8 excels: greenfield prototypes, one-shot features, and fast execution

2. Where it struggles: the last 10%, edge cases in existing codebases, and hallucinations

3. How Opus 4.8 compares to Opus 4.7 on business strategy work

4. Why I’m still reaching for Opus 4.7 on data-heavy strategy and roadmap work

5. The new features shipping alongside the model: dynamic workflows with parallel subagents and effort control in Claude.ai and Cowork

6. The prompting and harness strategy I’d use to get the most out of it

In this episode, we cover:

(00:00) Introduction to Opus 4.8

(00:44) Benchmark performance and pricing

(01:53) First coding test: Building a prototyping tool

(03:00) Where it failed: The last 10% problem

(03:27) The hallucination problem

(04:23) Testing Opus 4.8 on existing codebases

(05:24) The ambition test: Building games for a 9-year-old

(07:03) Business strategy test: 4.7 vs 4.8

(08:23) The roadmap test

(09:17) Final verdict

References:

• System Card: Claude Opus 4.8: https://cdn.sanity.io/files/4zrzovbb/website/c886650a2e96fc0925c805a1a7ca77314ccbf4a6.pdf

• Introducing Claude Opus 4.8 on X:

Where to find Claire Vo:

ChatPRD: https://www.chatprd.ai/

Website: https://clairevo.com/

LinkedIn: https://www.linkedin.com/in/clairevo/

X: https://x.com/clairevo

Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

2026-05-27 20:03:47

In this 30-minute episode, I walk through my favorite feature in Codex: the /goal command. I show how Goals transform AI from a turn-based assistant that needs constant ‘what’s next?’ prompting into an autonomous agent that can work for hours on complex, multi-step tasks. I share three real examples: eliminating thousands of Sentry errors, cleaning 3,900 emails down to 68, and organizing hundreds of Linear tasks.

What you’ll learn:

1. What Goals are and how they differ from standard prompts

2. How I used /goal to eliminate hundreds of error logs in my codebase over a five-hour autonomous run

3. The non-technical use cases that make Goals incredibly powerful: cleaning up 3,900 emails in under four hours and organizing hundreds of project management tasks in Linear

4. How to write effective /goal prompts with measurable outcomes, verification methods, and constraints

5. When not to use Goals and what makes a strong versus weak Goal

6. Why Goals represent a fundamental shift in how we work with AI, from babysitting the model to managing it

Brought to you by:

Mercury—Radically different banking loved by over 300K entrepreneurs

In this episode, we cover:

(00:00) Introduction

(01:50) What is /goal and when should you use it?

(02:45) The difference between prompts and Goal-based loops

(04:06) Claire’s first five-hour 45-minute autonomous coding task

(05:05) How to manage a Goal lifecycle: view, pause, resume, and clear

(06:06) How to write strong goals: outcomes vs. outputs

(07:34) The six components of effective Goals

(08:57) Example: Reducing P95 checkout latency with /goal

(09:36) Demo: Using /goal to eliminate Sentry errors in ChatPRD

(13:18) Demo: Burning down Vercel API errors

(17:28) Non-technical use case: Cleaning 3,900 emails with /goal

(21:24) Demo: Using /goal to clean up Linear project tasks

(24:41) When not to use /goal

(26:10) Why /goal changes everything

Tools referenced:

• Codex: https://openai.com/codex/

• Sentry: https://sentry.io/

• Vercel: https://vercel.com/

• Linear: https://linear.app/

Other reference:

• OpenAI blog post “Using Goals in Codex”: https://developers.openai.com/cookbook/examples/codex/using_goals_in_codex

Where to find Claire Vo:

ChatPRD: https://www.chatprd.ai/

Website: https://clairevo.com/

LinkedIn: https://www.linkedin.com/in/clairevo/

X: https://x.com/clairevo

Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].