Good Stuff 64 - Vibe Coding and Woodwork

DPC went from AI skeptic to full "AI psychosis mode" in three months. The conversation unpacks his journey from dismissing autocomplete to building his own Rust-based coding harness called Tau, designed with Unix philosophy — composability, standard input/output, event-based architecture, and the ability to run shell extensions over SSH to different machines. An extended woodworking metaphor runs throughout: AI is power tools. You can be a Japanese craftsman with hand planes making beautiful YouTube content, but most work will get done with routers and circular saws. The saw stop and jigs becomes the central safety question, how do you build safely without ripping your arms off? **Key Moments:** - [01:09] "I used to be very skeptical of AI. I'm still skeptical of AI, but I'm now in my AI psychosis mode." - [03:16] "I decided I need to write my own harness. Pi was the gateway for me to understand I could control this stuff." - [06:15] "My whole worldview is infused with Unix. Composability is one of the guiding principles." - [10:33] The woodworking metaphor: "You could be a Japanese craftsman with hand tools and be big on YouTube, but most stuff's probably gonna be done with power tools." - [13:42] "The moment you start doing woodworking, you watch all the videos about how to operate a router because it can chop off your fingers in milliseconds." - [16:36] "The moment I started playing with AI, I immediately started thinking how do we isolate the development environments?" - [22:34] 300,000 lines of code in Tau vs 200,000 at Fedimint after four years with multiple people - [24:43] "Vibe coding is great for personal use. If it has many bugs in code paths you never hit, do they really exist?" - [25:46] "I think a lot of people will build their own little empires." - [28:53] The logistics guy: "He built a whole vibe-coded infrastructure for his business. He's making millions on it." - [32:50] "Boutique SaaS — like SaaS for five businesses or ten businesses or even one." - [36:40] "I'm somewhat convinced now you can't just have the software write itself. It's not a hard problem, it's an impossible problem." - [38:38] "When you create software, probably more important than the software itself is the mental model of the problem." - [43:18] "The architecture is the most important aspect of software. The code you can always fix." - [47:16] The OKR trap: "I understand you, but the OKRs say something different, and we cannot afford nine months of seven people." - [55:31] "It feels like you just got a team under you with almost infinite patience and always available." - [58:18] "It's like a kid that's never gonna grow up, an employee you wanna senior up and pass wisdom to, but you know they'll never get it." - [1:04:21] "I was getting bored of software engineering and then suddenly this new thing drops that is nothing like anything before and its all new again" **Friends of the Pod:** Mario (Pi harness creator), Perth Wood School (safety guards discourse), the anonymous logistics guy at the Bitcoin conference **Concepts Introduced:** Tau harness (Unix-style, Rust-based), saw stop as AI safety metaphor, boutique SaaS, slop empires, model character matching (like matching work to employee personalities) **Quote:** "Software engineering is more of a craft than engineering, than science. AI is very much like power tools — they're dangerous, they can do a lot for you, but the security is very tricky. The moment you start doing woodworking, you watch all the videos about how to operate a router because it can chop off your fingers in milliseconds."