986: Does Code Quality Matter Anymore?

What It Covers

Wes Bos and Scott Tolinski tackle listener questions across five topics: whether AI-generated code makes quality irrelevant, modern CSS navigation techniques using popover and dialog APIs, building a personal second brain with Obsidian and vector search, browser compatibility tradeoffs, and choosing JavaScript full-stack frameworks as a Rails developer.

Key Questions Answered

• •Code Quality with AI: Well-organized, DRY code becomes more critical as AI-assisted projects scale, not less. AI tools use TypeScript LSPs to crawl codebases by following function references, meaning messy or duplicated code actively degrades AI comprehension. Projects that start clean maintain AI effectiveness longer; codebases with drift and duplication cause compounding errors as context grows.
• •Obsidian + Vector Search Setup: Wes built a functional second brain by migrating ten years of markdown notes into Obsidian via Claude, then connecting QMK (Toby Lütke's tool) for semantic vector search. QMK vectorizes sentences mathematically, enabling fuzzy retrieval — searching "coat measurements" surfaces notes tagged "shirt size" — without requiring exact keyword matches across the vault.
• •CSS Navigation with Popover/Dialog: Using popover and dialog APIs for hamburger menus is viable but not yet production-ready for broad browser support. The recommended current approach remains JavaScript class-toggling for compatibility, while using `@starting-style` and `allow-discrete` CSS properties to animate display-none transitions represents the forward-looking standard to adopt progressively.
• •Browser Support Strategy: Rather than applying blanket rules like "support last two major versions," teams should pipe actual traffic data into caniuse to make per-feature decisions. Old iPads running outdated Safari represent the largest real-world compatibility risk. Tools like Sentry's root cause analysis AI can identify which specific browser versions trigger production errors, enabling targeted fixes.
• •JavaScript Framework Selection for Rails Developers: When choosing a JavaScript full-stack framework, prioritize web-standards-based tools (using native Request, Response, Fetch APIs) because code becomes portable across frameworks like Hono, SvelteKit, and others without full rewrites. Avoid alpha-stage frameworks for production; favor ecosystems large enough that AI coding tools have sufficient training data to assist effectively.