1017, We need to stop calling it AI

The podcast discusses various technical and developer-related topics, focusing on component libraries like ShadCN, which involves copying UI components into projects for full ownership and control, though it requires manual updates and maintenance. It contrasts this approach with relying on external libraries, emphasizing trade-offs between ownership and the risk of unintended changes from upstream updates. The conversation also explores the use of PNPM over NPM, highlighting PNPM's speed, security features, and improved workflows for monorepos. Design systems in React are critiqued for underutilizing modern HTML elements like <dialog> and <scroll snap>, despite their accessibility and efficiency benefits. The role of AI in development is addressed, advocating for balancing AI-assisted learning with a focus on fundamentals, architecture, and deep problem-solving. Security risks in technical interviews, such as malicious scripts in repositories, are warned against, alongside broader concerns about AI's practical utility versus hype. The discussion extends to evolving developer tooling, improvements in standards for web features like JavaScript and CSS, and the challenges of integrating new browser APIs into UI libraries. Personal anecdotes about Stack Overflow's early days and the evolution of podcasts into video content add context, while debates on AI's role in design systems and the tension between trend-chasing and foundational expertise conclude the core technical exploration.

• What if you built a custom design system using ShadCN components, prioritizing manual ownership and updates?

  • Move: Integrate ShadCN components directly into your project, replacing npm imports with local copies.
  • Why Now?: ShadCN's ownership model grants full control over updates, which is critical for security and customization in a solo dev workflow.
  • Expected Upside: Reduced risk of unexpected UI changes from upstream libraries and faster troubleshooting for custom mods.

• What if you swapped NPM for PNPM to streamline package management across your projects?

  • Move: Adopt PNPM's global store and symlink-based dependencies for all new projects.
  • Why Now?: PNPM's speed, explicit script approval, and monorepo-friendly features align with the need for efficient, secure workflows in solo ops.
  • Expected Upside: Faster dependency installations, improved security controls, and smoother monorepo management without external tools.

• What if you replaced custom JS implementations with native web APIs like <dialog> and Scroll Snap in your UIs?

  • Move: Audit your codebase for redundant JS implementations of native features (e.g., modals, carousels) and replace them with <dialog>/scroll-snap where browser support is sufficient.
  • Why Now?: Native APIs reduce maintenance overhead and accessibility risks, while modern browser support (e.g., Chrome, Firefox) makes this feasible.
  • Expected Upside: Lighter codebases with built-in accessibility, and reduced reliance on third-party UI libraries for common patterns.

• Adopt PNPM for dependency management to leverage its speed, security features (e.g., explicit approval for post-install scripts), and streamlined update management, reducing friction in monorepos and avoiding redundant package copies.
• Prioritize using native HTML elements (e.g., <dialog>, scroll snap) in design systems when browser support is sufficient, cutting down on custom JS reimplementations and improving accessibility without sacrificing functionality.
• Fully own ShadCN components by copying them directly into your project to maintain control over updates and modifications, and schedule regular audits to address security risks or bugs in manually maintained code.
• Use AI tools for self-assessment and problem-solving by engaging in conflict-driven questioning (e.g., "grilling" yourself with AI-generated challenges) to deepen technical understanding and validate solutions before implementation.
• Avoid opening untrusted repositories in IDEs to prevent potential exploits (e.g., embedded scripts stealing environment variables); verify sources using tools like Claude or code inspection before proceeding.