Talk: Claude Code for Developers, Sønderborg. 15 minutes + 5 minutes for questions.
Establish technical credibility, then show each tool full-screen before returning here.
My Moonlander keyboard.
Return to the original slide and finish the introduction.
Acknowledge the anxiety rather than dismissing it.
Introduce the historical interface, then show the old and current interfaces full-screen.
Public-domain Argonne/US Department of Energy photograph via Wikimedia Commons: HD.6B.030 (10693137083).
Return to the argument: programming was redefined rather than erased.
Agentic development changes where the developer applies skill; it does not remove responsibility.
The distinction is ownership, not which feature someone uses. Using a skill is different from identifying a need and creating the skill you wish existed.
This is not binary. Move one step when recurring friction earns the investment.
Set up the problem, show familiar Claude Code concurrency examples, then demonstrate my Niri workflow.
Boris Cherny describing five parallel Claude sessions with numbered tabs and notifications.
Full-screen Niri demonstration. The poster is the PDF and venue fallback.
Return to the slide and explain that the interface is incidental.
Run tests through hooks and return failures to the conversation. For web development, give the agent browser access so it can observe the UI or console error, fix it, run the dev build, and inspect the result itself. Longer loops make human attention scarce.
Explain normal notifications versus an ultra-important completion immediately focusing its workspace. Once results arrive reliably, reviewing them becomes the bottleneck.
Show Markdown wall versus a structured HTML report. Do not accept the default interface between agent output and human judgment.
Hunk split view with sidebar and inline AI notes. Source: modem-dev/hunk README.
Hunk stacked display mode and mouse-selectable menus. Source: modem-dev/hunk README.
The second screenshot is Hunk's stacked display mode, not a logical stacked-diff workflow. GitHub stacked-diff support is currently beta.
RTK token-savings report.
Shared scope does not mean loading every repository into model context. Let the agent discover only what the task needs.
Mention GLM/Grok first-pass review verbally, then a stronger model for the final decision.
Expiring usage can sharpen tomorrow's work without distracting the primary task.
Nobody needs my exact setup. Everyone can make one deliberate move towards ownership.
Agentic work lets one process cut while another sharpens.
Tesla may drive to A, but it cannot decide to go there or judge whether it was correct. Keep the user's preferred force-multiplier/enumerator phrasing.