About this episode

The episode discusses concerns about the quality of code generated by LLMs and the transition from nginx to Caddy for production servers.

We hop into the call and start recording, and what we found, we had both issues / concerns about quality of LLM produce code. Morten is reviewing some aspect of his project before releasing the public version and found some interesting thing that would make it hard to justify leaving them there. I had very similar issues, entering into a full refactor of a Go backend server I let the LLM cook for a rare time in Go, and decided at some point that enough is enough and decided to refactor the code. It's not like it's big surprise, and I think we're a lot in that situation. When you truly start to review the code that is generated, let's just say that sometimes it's not the best work you'd have done yourself. It's quicker though, no question there. But at what cost. I also finally ditched nginx and installed Caddy for my production servers.

People in this episode

Host: Dominic St-Pierre

Guest: Morten

Topics covered

• LLM quality issues
• code refactoring
• nginx to Caddy
• Go backend
• software development

Mentioned in this episode

Organizations: nginx, Caddy

Products: LLM, Go

More episodes of go podcast()

• 084: Databases, FTS, and local LLM · May 7, 2026 · 1h 1m
• 082: Streaming, product updates, and marketing · April 23, 2026 · 1h 2m
• 081: Weird Redis bug and we talk text editors · April 16, 2026 · 59 min
• 080: Ship it anyway: fighting the urge to refactor · April 9, 2026 · 55 min
• 079: WireGuard and don't mix social engagement w/ product validation · April 2, 2026 · 1h 5m
• 078: Uncloud, bridging the gap between Docker and Kubernetes · March 26, 2026 · 1h 5m

Explore listener stats, chart rankings, contacts and more on the go podcast() podcast page.