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

hot take: I'm not as repulsed as I once were for a package named "controllers" or "handlers" in a Go web server app. after all those years writing Go, the data access and logic / algorithm is where I want nicely reusable packages. I cannot care less about my handlers being in the same package.

ho .git directories around all orgs hide so much skeleton, security risks, data breach, scary shit lol. If you clone an hold repo from scratch that should be in the small donwload time and takes a lot, check your .git history for surprises. I did on a 7y/o Go project... Like I said, scary.

> just write code like a fucking normal human being. This is music to my ears. There's so much crap and shit all over the place, it's not because you're now capable of shipping things due to AI that you should.

User health scoring in Parle launches. it's very quick to see the overall health of a user, a cohort or your entire user base. p.s. I'm looking for a marketing partner for Parle, I know, I know, it's certainly not the way to find someone, but damn I don't know anyone 😜#buildinpublic

Small accessibility tip for my felow SWE that have GitHub repos, please keep or have an H1 on your README, even though GH do have a landmark for the README, not having an H1, say using H2 fights against other GH UI elements. Seems to be more and more frequent, and it's bad a11y btw.

I've added product usage criteria in Parle automation workflow for condition type node. This makes it possible to branch based on if a user performed an action, optionally X amount of time and optionally in the last Y amount of days. That's targeted messaging. #buildinpublic parle.io

I was a 25x, heck 100x better programmer when I was doing Elm daily between 2018 and 2020. I'm incorporating a component into my saaS I've built back then. I'm rusty as f*, but damn is the compiler good. Go is great, Python is fine, Returning to Elm and FP is such a breeze of fresh air.

Anyone else tried uv and ruff on a Python project and got excited. My up-coming SaaS isn't a Go based backend, but Django, I might do a pod on go podcast() about this and why and where I use Go. But Elm and Go (and screen reader) made me appreciate code formatters. uv and ruff are great..

finally, the first production workflow has been executed. Crazy exciting, but it was hard getting there. My product has reach a decent MVP state, enough to get more feedback at least. At this moment: workflow automation (emails and in-app msgs). Check my bio if curious. #buildinpublic

how many days b4 launch that's not shameful to delete the db and all migrations because you're realising that a core relationship does not really make sense now that the system is taking forms? Crazy that 25y ago it could take years of dev before a real user would use the system and give feedback.

I'm way friendlier with my future self these days. I'm documenting important processes in my soon to release SaaS, something I wasn't doing before. Adding a new action (Delay) to my automation workflow, Next time I need to do that I'll have the steps all lined up. #buildinpublic w/ +15y of exp

A cliché but that last 10% to finish that v1 is so slow. And admitely is the thing to be careful as a tech founder, there's always something to add. Don't get cut into that vicious circle. It's been said before, but easy to fall into that trap. My trick, keep a list and do nothing more, nothing.

My SaaS has an automation workflow component, I've never built something like this. I've built countless ETL, but it's not the same beast IMO. The thing that runs the workflow was crazy fun to design and impl. The rendering uses recursion. If marketing would be that rewarding ;) #buildinpublic

~3 weeks ago I completed a contract and took a gigantesque life decision. I was looking at acquiring a SaaS that were in the 1k-2k MRR range for the last year or so. Inspired by @valsopi.com I decided to self-fund myself and finally launch this product I wanted for years. Full time on it. 1/2

I woke at 3am to continue work on my B2B SaaS. I've only started 1 week ago, but fairly determined and I haven't started at 3am since my last product Roadmap in 2016 At 44, comparing to doing the SaaS thing 15 years ago, it's tougher, much tougher. Will I regret that tomorrow? TBD... #buildinpublic

🎙️go podcast ep. 56 is live. I talk with Ivan Fetch about being blind in tech. I've received a lot of questions and interests from previous guests when saying I was using a screen reader. A two part episode. The day-to-day challenges etc. Ivan is an SRE. gopodcast.dev/episodes/056...

I'll be interviewing another blind programmer next week in go podcast(), we'll talk about why Go is great from code accessibility PoV, devops and challenges we both face as blind SWE. If you have questions you'd like us to cover, I'd be happy to get your suggestions. #golang

I'm currently debating acquiring a SaaS or self-funding launching something myself. It just need to happen for me, I've been chasing this since 2007, and being all-in keeps me so focus and energize vs. morning and week-end. A huge family decision impacting my wife and 2 kids though.

🎙️go podcast() ep. 55 is out. I talk with Tristan Mayo, the creator of Zog, a Go validation library that helps with parsing data and transforming say HTTP POST data into struct. #golang gopodcast.dev/episodes/055...

🎙️go podcast() ep. 54 is out, I talk with Delaney Gillilan about Datastar, a new framework that helps create web apps using SSE and handles a lots of functionalities aka HTMX + Alpinejs. A great fit for Go web application. gopodcast.dev/episodes/054...

When recording episodes of go podcast() Each time I tell a guess I'm blind they all have the same reaction and wants to know more about how I'm writing code and challenges I face. I'd like to be more open and wonders what's the best medium for this, podcast or YouTube? Thoughts?

Accessibility tip for open source maintainers. Please use an H1 in your GitHub project README, otherwise, say using an H2 conflicts with GitHub's own elements.

🎙️go podcast() ep. 53 is live. I talk with Markus Wustenberg, the creator of Gomponent about my real-world experiences adding Gomponent to a Go production SaaS that uses html/template, my ups and downs and where's the project is heading. #golang gopodcast.dev/episodes/053...

Does that still exists, tiny SaaS that are around 1k in MRR but aren't looking for 200k acquisition price? I've bought / sold half a dozen SaaS in the last 15 years, but where are those these days?

Currently looking to fill guests spot for the following weeks. For all my Gophers friends, if you want to jump into an episode, just contact me dominicstpierre at gmail. #golang

🎙️go podcast() ep. 52 is out. I'm joined by Peter Strøiman, the creator of Gost a Go headless browser that can execute HTMX / JS in-process for TDD flow. gopodcast.dev/episodes/052...