Bartłomiej Płotka

My "Efficient Go" book with @OReillyMedia has been released!🎉 I wrote some words about the book, content and generally my experience writing it (with photos!): bwplotka.dev/book Good for a slow Saturday--maybe it will help you to decide to write your own book? 🤗

Our KubeCon talk recording is out: youtu.be/Rw4c7lmdyFs What if we can define a schema for important @PrometheusIO metrics, version it, allow users to pin PromQL metric to a certain schema version and solve metric renaming problems? 😍

Things that brings the joy 🙃

Thanks for being such an amazing mentee and for writing the blog post! We really enjoyed working with you too 🤗 Let's continue working together in OSS! 💪

Today is a good day! #golang go.dev/blog/error-syn… "For the foreseeable future, the Go team will stop pursuing syntactic language changes for error handling. We will also close all open and incoming proposals that concern themselves primarily with the syntax of error…

First time going to Japan! Come watch my talk if you're also going to KubeCon :)

My talk at #KubeCon is out now! I partnered with Antoine Thébaud to dive into innovative dashboard design with PersesDev. Watch our discussion here: youtube.com/watch?v=7h70Ol… You can also access the slides at: kccnceu2025.sched.com/event/1txHy

Designing software should happen while you’re building it. Not before. You can do some bits beforehand, but in my experience, projects that do well are free to grow organically in any direction they like, not by following some predestined roadmap.

Go is the right language to reimplement your typescript in.

I'm super excited about my work at @grafana and what's planned for my team in the next few quarters. upstream and mentorship are my two favorite things about open source and we manage to combine and make those the highest priority for MONTHS ❤️

RSVPs for February Gophers @ JustEat are now open! meetup.com/londongophers/…

Epic discussion around @golang error handling: github.com/golang/go/disc… Adventurous ideas. Ofc there might something to improve, but the following image is still applicable: 🙈

We see more questions/responses on GitHub issues on OSS projects clearly generated with the help of GenAI - very generic, asking kind of unrelated questions. Hard to judge what part contributor exactly does not understand and how to help. Do you experience similar? Any tips?

Looks like @golang 1.24 is going to be pretty epic! Weak pointers, properly working finalizers alone might change the game! Then optimized maps, native fake clock, benchmarking reliability and ease of use, and tooling dependency management.. and more! antonz.org/go-1-24/

Finally, an OpaqueAPI is officially coming to Go, with exciting lazy decoding and optimized memory layout! Now you know why the new API was necessary with that gogo migration friction. 🙈 Let us know how it goes for you, it massively improved efficiency internally! 💪🏽