Chris shares a nuanced take on vibe coding, distinguishing between building a 'program' (a personal tool to get something done quickly) versus a 'product' (software meant for broad distribution and reliability). He references a blog post by Dylan Batty on this distinction, arguing that vibe coding excels at the former but isn't necessarily suited for the latter. He's not anti-vibe coding but uses it selectively for dev tooling work.
•1m watch time
Sort: