AI-Generated Podcasts
Deep dives into software engineering topics — generated by AI, curated by a human.
Video Teaser
React Do's and Don'ts: Fiber, Reconciliation, and the Hooks Nobody Uses Right
Most React developers write code that works but re-renders 10x more than it should. Understanding Fiber, reconciliation, and when useMemo actually matters changes how you think about performance.
Building an AI Chatbot for My Portfolio — Zero Dependencies, One Hour
How I built a conversational AI agent with Claude Haiku, a single Next.js API route, and zero npm dependencies. Rate limiting, markdown rendering, syntax highlighting, and privacy guardrails — from idea to production in under an hour.
Build a Multi-Step Form with Web Components, Zero Frameworks
A real-world multi-step form with validation, i18n, and event-driven architecture — built with Lit, native HTML validation, and 5 dependencies. No React. No state library. No form library.
Kill the Java BFF: Why Small Teams Should Go Fullstack with Next.js
If your small Scrum team runs a Java Spring Boot BFF alongside a React frontend, you're paying double. Here's an honest architecture comparison — including where Java wins.
The Rule of Least Power: Stop Overengineering Your Frontend
The W3C told us in 2006: use the least powerful technology that works. Most frontend teams do the opposite. Here's how HTML, CSS, and native APIs can replace half your dependencies.
Forget Best Practices, Invent Your Own
"Because it's a best practice" is not an argument — it's an appeal to authority. Why following blindly is dangerous and how to build your own practices.
Smart vs. Dumb Components: The Split That Makes Code Maintainable
The most impactful architectural decision in frontend: separating what fetches data from what renders it.
AI-Assisted Development: How I Built This Website
A hands-on look at using AI as a development partner — from Figma design to production code with Claude.
YAGNI Over DRY: Why Duplication Beats Premature Abstraction
Most developers learn DRY early and apply it everywhere. But premature abstraction kills more codebases than duplication ever will.
Practical Guardrails for Scaling Frontend Teams
What actually works when leading frontend teams at scale — from code review as mentorship to hiring engineers who think, not follow.
Every npm Package Is a Liability
Reduce your Node dependencies for maintainable apps. Every package you add is a liability — learn when to use them and when to write it yourself.
Micro-Frontends: When They Make Sense (And When They Don't)
I designed a micro-frontend architecture at AXA Switzerland. Here's what I learned about when this pattern helps and when it's just complexity for complexity's sake.