go podcast()

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.

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 ;).