ha the good old "just use PostgreSQL" advice was always reliable and will always be reliable for me to give, excerpt from last go podcast() episode. youtu.be/LaAsvI1dG7k

📹go podcast() ep. 87 is out, we're having video now as well. Morten took the advice of "just use Postgres" and I'm preparing for a first real-world usage of my SaaS. YT: youtu.be/LaAsvI1dG7k Pod: gopodcast.dev/episodes/087...

ok, 0 to 1 is done in the sense that I've a first paying customer, someone booked a demo for tomorrow, and there's ~2 lead in the pipeline, it's so little but at the same time gigantesque. Did I freaking finally built something people want. Next step is 10 paying customers, which feels like ⛰️

🎙️go podcast() ep. 86 is out. Morten is debating about using ClickHouse for telemetry data, and I try to plant the seed of, use PostgreSQL for now. From my side, I released v1.7.0 of StaticBackend, the first real release since I un-archived the project. gopodcast.dev/episodes/086...

in my last r/golang post, a reply I got: > Wow, how did you manage to write so much code while being blind? People with disability are able to do as much as enable people, IF they're in an environment they can be productive in. Think about this when you gave your next interview.

day-to-day as blind software engineers - I once tried to get my profile in a website that help diversity in tech that helps open companies connect with talent, turns out I never was listed. Well guess what, finding job being disable if very hard as well, even if I'm white. Food for thoughts

StaticBackend v1.7, a Go mature backend API that allow to test product idea very quickly with everything typical web applications need. Yes it's similar to Supabase, we launched at exactly the same time and I became aware of them via a tweet when they got their 1st $30m. github.com/staticbacken...

🎙️go podcast() ep. 85 is out. Am I the only one hearing Morten like he's talking via a phone? haha, nonetheless a traditional episode where we talk about our Go based product we're trying to sustain ourselve from. With the typical tangents and what not. gopodcast.dev/episodes/085...

One of the few advice that everyone is regurgitating for almost 20y in SaaS world that I believe in is use the boring stuff to build and don't jump in the unknown. Especially true with LLM these days. I love Gleam, a lot. But Go just allowed me to finally build a SaaS smbs want to pay for.

🎙️go podcast() ep. 81 is out. Morten closed the call, not sure if it was a msg to tell me to STFU lol I was deblatering about a Redis issue I have in prod, we moved to text editor tangent, neovim, text editor as blind / screen reader user. gopodcast.dev/episodes/081...

programming languages are the new frontend frameworks now - one is created / launched each week it seems. The future will be noisy.

one thing I like about the ? in syntax like Rust is that my screen reader ask a question about a line, looking at Lisette language at the moment: let data = io.ReadAll(file)? Which naturally increase the intonation, really cool on top of not having if err != nil { return x, err }

🎙️go podcast() ep. 79 is out, Morten talks about trying WireGuard for his project and we talk about the danger of taking social engagement for product validation, the trap and how it feels like progress but might not convert to paying customers, like ever. gopodcast.dev/episodes/079...

🎙️go podcast ep. 78 is out, we received Pasha Sviderski, the creator of Uncloud a tool that bridge the gap between Docker and K8, it's helping with infra / deployment on self-hosted servers and of course, built with Go. gopodcast.dev/episodes/078...

you know what, calm company just took a new definition for me, in addition to not grow at all cost, my definition expanded to not use LLM at all cost, the less of the better. Sorry if your new fav metrics is outputing 10k LoC per day or if your PM is able to generate code now. it's terrible code...

🎙️go podcast() ep. 75 is out. @andydotxyz.bsky.social joins us and we talk about Fyne, a new visual designer allowing you to build your UI more easily and a service Andy is bootstraping to help teams with building Fyne apps more easily. gopodcast.dev/episodes/075...

🎙️go podcast() ep.74 is live. We give a small updates on our respective projects and fall into an improvised segment on OSS licensing and changing license once contributors contributed etc. gopodcast.dev/episodes/074...

2026 is the year I say fairwell to nginx and finally adopt Caddy as my main reverse proxy server. What feature won me over? The on demand TLS, I mean it's nice for multi-tenant platform. Nice isn't the word, I'd say it's sick.

🎙️go podcast() ep.73 is live. We talk about things in the news, like Heroku in ~maintenance mode and we talk a little about observability since I'm looking to implement it in StaticBackend. As always we're in the Gophers Slack community in the #gopodcast: gopodcast.dev/episodes/073...

🎙️go podcast() ep.72 is live. We talk about the tools we use as Go software engineers, a little on local dev vs. deployment, CLI and a bit of a different opinion regarding containers for local dev. gopodcast.dev/episodes/072...

Hey a quick teaser for tomorrow's go podcast() episode ;) - Are you using docker/podman as a dev to prevent installing "servers" on your dev env, like PostgreSQL, Valkey, Redis, Mongo, etc?

Go I love you a lot, but I would have hope that Ken, Rob, or Robert (whomever wanted short names) would have thought about screen reader users a bit: strconv.Itoa(params.Page)). The only thing I make sense of is params.Page.

/r/golang isn't what it used to be, I will leave it as that, where Gophers are hanging out these days, what if I'd like to hear from real human?

🎙️go podcast() ep. 70 is live. You'll hear the voice of Morten, a new co-host. We talk about tech education and how LLM has change the landscape a bit of how people learn new skills, and as always, the concensus: expert are hard to replace. gopodcast.dev/episodes/070...

Hey I was in the last Cup o' Go, was super fun to be on the other side of the table, and they have a professional audio editor haha, but seems to have pick my wrong audio input, I sound like crap lol, we talk about podcasting a little. cupogo.dev/episodes/go-...

🎙️go podcast() ep. 69 is out. I'm un-archiving StaticBackend, my OSS baaS. I'm looking at having fun again programming. Not sure about you, but I'm not having the best time being a software engineer lately, and I need to change that. share.transistor.fm/s/cb288869

There were a time in my software engineering career that it was hype to limit the line of code introduced to a code base per day and we were thinking really hard about maintainability. today... it's different. It's called being a 100x engineer I believe?

I'm looking for a/multiple co-host(s) for go podcast(). The show turned 4 years this month and I'd like some freshness for the next phase. There's a post in /r/golang if anyone's want to know more. Podcasting is hard, and I'll admit that I'm not the most consistent host, but I want to continue.

🎙️go podcast() 68: Delaney Gillilan and I revisit datastar. I started using it to replace my HTMX and Alpine combo. We talk in ep.54, this time I wanted to focus a bit on the backend aspect of using datastar, keeping some state in the server, pushing signals etc share.transistor.fm/s/dc554734

🎙️go podcast() 67, All about LLMs with @markus.maragu.dev how LLMs can be used in systems to add values to users / how he uses LLMs in his day-to-day dev tasks. I'm a bit fatigue of the hype and wanted to hear about real-world expereinces. A bit less on Go for this one share.transistor.fm/s/342cb266

🎙️go podcast() 66 is live, this week I talk with Jon Barber about extreme programing concepts, CI, CD, pairing, how software engineer teams can improve their processes and Go is helping a lot making this enjoyable. gopodcast.dev/episodes/066...

some good things about our current days after all. If you recall having to provision SSL certs and installed them back in the days, generating the request, paying the 3rd party, receiving the cert(s), updating... Arf, in my case it was in IIS which I never want to touch again. There's some positive

🎙️go pocast() 65 is live, but this week I'm not talking about Go, I'm talking about the 17 years of trying to build a sustainable software company. I've seen 3 distincts SaaS era since my discovery of solo product builder in the Software of Business forum back in 2003. share.transistor.fm/s/569d6825

🎙️go podcast() 64 is live. It's all about Podman, containers for this one, I retried Podman lately and it's great. I started adding audio clips, for now it's text to speech of text msg I got, but I'd love to get real audio clips for future episodes. gopodcast.dev/episodes/064...

I'm going to talk about podman tomorrow in go podcast(), I'd love to get some audio clips of real-world experience, do you like it, or not, are you using it instead of Docker, etc. You can send me text or audio clip in #gopodcast in the Go slack community, I think it would bring dynamism to the pod

I'm releasing a new course on Go fundamentals. I'm seeing a lot of movement in the Go community lately and it's great, starting with a solid fundation makes it easier to reach the goals that one setup when learning a new language. Go is simple, fast, and fun. dominicstpierre.com/product/zero...

🎙️go podcast() 63 is live. I talk with @qba73.bsky.social about common mistakes Gophers are doing when it comes to testing. Jakub is writing a book "50 Go Testing Mistakes" which is early access atm. Please reach out if you or someone you know want to be a guest. gopodcast.dev/episodes/063...

it's only been a short time I've started writing Gleam and already I'm missing a Result type and pattern matching when doing Go. I ❤️Go's simplicity, but FP, pipeline op, non-nullable value, immutability is gaining on me just like when I did Elm back en the days. 1/2

🎙️go podcast() ep. 62 is live. A university paper caught my attention, it was on Go, basically are our static analysis and linters tools truly helping. Personally I always found Go's overall tooling dead excellent. share.transistor.fm/s/ebdd20e7

50k downloads with go podcast(). I'm proud of this, having almost quit three times. Published the first episode in Jan 2022 w/ some cheesy sound effects 🧀). I haven't published regularly, but huge thanks to all who listen. Next up: 100th episodes. 1st ep to laugh a bit: gopodcast.dev/episodes/001...

🎙️go podcast() 61 is out. This week is all about another programming language that I'm very excited about. I talk about what I'm looking for in a programming language, my experiences going back to vb6 and why Gleam feels as good as when I started with Go 10+ years ago. share.transistor.fm/s/db7ea269

go podcast() in the news, and I'm now a thought leader - this seems a tad AI-generated from the transcript episode though, which is ironic ;) thenewstack.io/go-experts-i...

🎙️go podcast() 60 is out. IMHO the message around LLMs to be very wrong and driven by VCs and big tech companies. At the end who's going to benefits from this, certainly not the rest of us and I don't understand why people propagate the hype. What about quality of life share.transistor.fm/s/bb039a66

my new enmy as a blind programmer, CAPS. Did you knew that CSS class are case sensitive? I did not. But once you use a screen reader, guess what it's not as straightforward to distinguishes between and, end, AND, END, And, End they're all the same to me now... You think you have challenges ;)

this is great addition, very useful in making test simpler for concurrent code.

🎙️go podcast() ep.59 is live, I'm joined by John Arundle and we talk about the maturity of Go, is it's hype over, some AI here and there, and some other things, I hope you enjoy, I took a summer break of the pod, it's coming back. To whom I should talk to next? #golang gopodcast.dev/episodes/059...

PostgreSQL is just crazy, I know I'm certainly 10 years late with the SELECT COUNT(id) FILTER (), COUNT(id) FILTER ()... Basically the FILTER and easily have multiple COUNT on the same SELECT, but those are the kind of things I like to learn being a OG SQL Server user. Dashboard metrics in one query

kind of crazy that a lot of people using AI to help them code are often adding: "no shame in using AI" or kind of always trying to defend. Very similar to people eating meat and talking to a vegan and saying "ho well we only eat meat once a day or something. Assume yourself...

I knew that refactoring an older Go program would be decently easy, but now that I'm doing it in a decently sized and old project, well, maybe not as easy as I thought it would be. But still one of the most straightforward overhaul I've done across stacks I used. Of course it's mainly dependencies

I'm releasing tpl v1, it's not a life-changing library but makes using Go's HTML templates a tad more tolerable. I never remember how to properly parse the freaking HTML templates to have base pages and partials. Now I do and it's adding i18n + other helpers. github.com/dstpierre/tpl