How I Tamed Claude - Emmz Rendle - NDC London 2026

Value of the Information & Strength of the Argument

The talk provides valuable, practical insights into using Claude Code effectively, based on the speaker’s extensive experience. The argumentation is clear and well-structured, with live demonstrations that illustrate the techniques. The speaker acknowledges limitations and personal preferences, which adds credibility. However, the advice is largely anecdotal and may not be universally applicable, as it relies on specific tools and configurations.

Scientific Rigor, Source Quality, Title Accuracy

The talk is scientifically rigorous in its practical approach, but it lacks formal citations or references to academic sources. The speaker mentions Andrej Karpathy’s quote but does not provide a specific source. The title accurately reflects the content, and the talk is well-organized. The speaker’s credibility as a CTO with 30 years of experience adds to the reliability, but the lack of external sources limits the scientific rigor.

The title accurately reflects the content, as the speaker shares personal techniques for effectively using Claude Code.

8/10

The talk provides practical, experience-based insights into using Claude Code for software development, with clear explanations and live demonstrations. The speaker is a CTO with 30 years of experience, and the content is consistent with current best practices in AI-assisted development. However, it is largely anecdotal and lacks formal citations or empirical evidence.

Markers derived by PSI from the transcript: the creator did not define chapters.

• 02:00Introduction: Speaker explains the talk's evolution and the rapid changes in AI agents.
• 05:00Basics: Importance of claude.md file and configuration.
• 10:00Commands: /init, /context, /clear, and managing context window.
• 15:00Workflow: Four personalities (analyst, architect, developer, reviewer) and system prompts.
• 20:00Analyst mode: Creating a requirements analyst system prompt and gathering requirements.
• 25:00Architect mode: Writing specifications and planning implementation.
• 30:00Developer mode: Test-driven development and building the system.
• 35:00Reviewer mode: Reviewing code and ensuring quality.
• 40:00Maintaining state: Using claude.md and memory files.
• 45:00Conclusion: Thoughts on junior developers and human responsibility.

• NDC Conferences — Conference organizer and context for the talk.
• NDC London — Specific conference where the talk was given.

• Anthropic's Claude Code documentation — Official documentation supporting the speaker's claims about Claude Code features.

• ndclondon.com