Collab Coding, Not Vibe Coding a Dashboard in Golang

There's a difference between *vibe coding* — pasting prompts at an LLM and shipping whatever falls out — and *collab coding*: working with the model the way you'd work with a sharp engineer who hasn't seen the codebase yet. In this build, Goju does the latter. He pairs with Claude to build a real working dashboard in Go (Bubble Tea + Lip Gloss), keeping the model honest at every step: reviewing the diffs, pushing back on the wrong abstractions, and steering the design instead of rubber-stamping it. The result is a dashboard that actually does what it's supposed to — and a concrete demonstration of what disciplined AI-assisted dev looks like when you don't outsource your thinking. 🔍 Topics covered: - The real distinction between collab coding and vibe coding — and why it matters - Building a TUI dashboard in Go with Bubble Tea and Lip Gloss from scratch - Where Claude shines as a coding partner, and where you still have to drive - Catching and correcting the model's bad calls in real time - What disciplined AI-assisted engineering actually looks like end-to-end 💬 How do you draw the line between collab coding and vibe coding in your own workflow? Share your rules in the comments. 🔔 Subscribe for honest tech analysis: https://youtube.com/@gojutechtalk 📺 Related: Chamath Palihapitiya Says AI Coding Is All Hype — And I Agree https://youtu.be/3EOpf7gTeaQ 📺 Related: The Dangers of Over-Reliance on LLMs and AI https://youtu.be/U1Dhfij4Uy0 📺 Related: The Problem With Today's AI (In Simple Language) https://youtu.be/Cl7x2OhbPwU #CollabCoding #VibeCoding #Golang #BubbleTea #LipGloss #ClaudeCode #AIAssistedCoding #PairProgramming #TUI #DashboardBuild #ClaudeOpus #AnthropicClaude #SoftwareEngineering #DeveloperWorkflow #LiveCoding #GojuTechTalk