go podcast()

In this episode, we dive into the dangerous "pre-launch purgatory"—that final stretch after reaching V1 but before the first paying customers arrive. It’s a period where the temptation to start over is at its peak, armed with all the lessons learned during the build. We discuss how to resist the urge to refactor your SaaS into oblivion and why shipping "imperfect" code is the only way to get the feedback you actually need.In the second half, the conversation shifts to the challenges of maintainership. My co-host shares the hurdles he’s currently facing with his open-source project, Andurel. When you’re building in a vacuum without a clear signal from users, how do you decide which features matter? We explore the shared struggle of finding a "North Star" when the feedback loop is quiet and the roadmap feels uncertain.

A deep dive into using WireGuard for private networking and the tradeoffs between giant shared networks and per-team setups. Conversations about telemetry, databases, and simplifying credentials through private networks. Practical advice on validating real customer interest versus social engagement and using personalized outreach over automated spam.

Pasha Zvideryski, a software developer who built Uncloud after work in infrastructure at Canva and JetBrains. He talks about simplifying deployments by bridging Docker and multi-machine setups. Discussions cover push vs pull deployment models, Compose-format production deployments, WireGuard mesh overlay networking, Caddy-based ingress and rolling updates, and Unregistry for image distribution.

A lively conversation about practical LLM uses in engineering workflows. They cover rapid prototyping, debugging production logs, and using LLMs for codebase exploration. The discussion tackles team impacts like review load, apprenticeship risks, and three-way pairing with LLMs. They debate tool preferences, CI integration, testing safeguards, and when to handcraft code versus relying on generated output.

They discuss worrying patterns in AI-generated code quality and the need for heavy refactors after LLM intervention. They debate perceived declines in model performance, benchmarking challenges, and risks of non-deterministic code. They compare Caddy and nginx, covering on-demand TLS, load-balancing features, DNS quirks, deployment strategies, and multi-provider tradeoffs.

Andy, the creator of the Fyne toolkit returns and talk about a new visual designer for Fyne apps and a service to make building to all platform very easy. We talk about the state of Fyne, AppTrix Andy's product and how it's now possible to use a visual designer to create Fyne UI if you're more of a visual person than defining the UI via code.Links:Fyne websiteAppTrix

We give an update on our respective projects and  talk about the difficulties of changing license from MIT to LGPL once there's contributions to the project.

This week we talk about multiple in-the-news topics like the SalesForce announcement that Heroku is in ~maintenance mode and we surface the big observability topic as I'm preparing to implement something basic for StaticBackend and since Morten already have this in his open source project we duscuss about ways to add this after the fct and some parts of tracing your system.

This week we're talking about the tools we're using in our day-to-day as Go software engineers.  Which tools we like, of course there's always the story driven aspect of go podcast(), so there's a couple of tangents here and there ;).

We're trying something, each first episode of the month we'll talk about our respective open source projects. This episode will be more story driven than others, and you'll be able to follow our journey maintaining open source Go projects.Links:Andurel Morten's projectStaticBackend Dominic's project