Software Engineer · Go Open-Sourcer · GenAI Community Leader · Hackathon Organizer

📍 Nantes, France | 🌐 samuel-berthe.fr | 📝 Substack | 🐦 @samuelberthe | 🦋 @samber.bsky.social | 💼 LinkedIn

Hi. I'm Samuel. I write Go libraries. It started as a hobby, turned into a side project, and is now my attempt at making open source a full-time job. The jury is still out. The coffee budget is not.

It began the usual way: I needed something at work that didn't exist, built it, and thought "someone else probably needs this too." That pattern never stopped. The most well-known result is lo, a utility library built on Go generics. It's now used in production at companies of all sizes, such as RedHat, VMware, Tencent, Bytedance, Grafana, and many others.

The community around these projects is overwhelmingly kind, sharp, and generous. Yes, even the occasional keyboard warrior ready to die on a typo 🙃. And I'm grateful for every single one of you. 💖

The ecosystem kept growing from there: monads, dependency injection, caching, structured errors, and 35+ log/slog handlers. If your stack uses Terraform, Kubernetes, the Grafana stack, apps you've definitely opened today (if you're Chinese), or a few places you'd rather not think about 😅 #pr0n — there's a fair chance my code is already quietly running somewhere.

On the community side: I started the Generative AI meetup in Nantes (Fr) from scratch: no audience, no budget, no certainty anyone would show up. It became the largest GenAI meetup in France 🇫🇷. I also run hackathons, speak at conferences, and write on Substack.

If your team ships with any of my libraries and you want to help me keep doing this, sponsoring on GitHub goes a long way. No SLA included, but bugs get fixed with genuine enthusiasm.

My lifetime goal? git push --force into a satellite. Just kidding. Well... maybe not entirely.

Turns out Go generics unlock a lot. I'm still finding out how much.

Be aware, 22 letters left for my next Go projects. Plenty of runway. 😂😂😂

At this pace I'll own the entire alphabet before Go drops GOPATH from the docs.

Go 1.21 introduced log/slog as the standard structured logger. I built 35+ handlers so you only configure slog once and route logs anywhere:

At some point "just one more handler" stopped being a joke. When you have 1, the next 42 come effortlessly.

Core

HTTP middleware — slog-gin · slog-echo · slog-fiber · slog-chi · slog-http

Monitoring & observability — slog-logstash · slog-syslog · slog-fluentd · slog-loki · slog-datadog · slog-sentry · slog-otel · slog-graylog · slog-quickwit · slog-rollbar · slog-betterstack

Notifications — slog-slack · slog-telegram · slog-webhook · slog-mattermost · slog-microsoft-teams

Messaging & streaming — slog-kafka · slog-nats · slog-channel · slog-parquet

Adapters — slog-zap · slog-zerolog · slog-logrus

The stuff that didn't fit anywhere else but was too useful to delete.

AI-native tooling built by someone who spends way too much time inside the tool. You know... dopamine...

Lists of things so you don't have to ChatGPT them at 2am.

If you can't measure it, you can't get paged on it at 3am.

Alert on everything. Sleep on nothing.

Random things? Maybe. Useless? Never.

Occasionally I stop writing code long enough to write words about code, with live demo that goes exactly as planned.

Substack - I write about Go, open-source, and software engineering on Substack. Deep dives into performance engineering, library design, and lessons learned from maintaining high-traffic OSS projects.

Talks - Slides and resources from my conference talks and meetup presentations. Topics include generative AI, performance engineering, observability, Golang, and building open-source communities.

Generative AI meetup replays 🇫🇷 - When my camera does not crash in the middle of the talk.

All those green squares, and yet rent is still due every month.

My open-source libraries ship in production at companies of all sizes, maybe yours too. Sponsorship keeps the libraries maintained, documented, and evolving.