Senior SWE TL @Google | ex Principal @RedHat | @ThanosMetrics @PrometheusIO | Bsky: bsky.app/profile/bwplotka.de… | Efficient Go 📖 @OReillyMedia
London, England
- Tweets 7,489
- Following 786
- Followers 7,325
- Likes 23,625
Pinned Tweet
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? 🤗
[NEW RELEASE] Efficient Go -- Author @bwplotka provides the tools and knowledge required to make your systems faster and less resource-hungry. oreil.ly/SyTuj #OReillyExperts
17
39
271
Bartłomiej Płotka retweeted
🥳 Excited to start revealing what we've been working on in the last few months. First, we decided to reinvent Kubernetes for agentic workloads with statefulness and fast resumption. Secondly, we are building an agentic orchestrator that will be Google's open agentic orchestrator and runtime. github.com/google/ax
128
378
4,238
717,721
Bartłomiej Płotka retweeted
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage.
I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care.
But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently.
For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios.
But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
230
966
9,223
473,132
Bartłomiej Płotka retweeted
🚀 Incredibly excited to share: Polar Signals is joining Dash0! 🧊
polarsignals.com/blog/posts/…
1
3
15
2,419
Bartłomiej Płotka retweeted
We caught up with @bwplotka at KubeCon EU. He's pumped about semantic conventions across OTel and Prometheus finally becoming practical, and AI changing how open source is built. #KubeCon #Prometheus #OpenTelemetry
piped.video/shorts/QF3Yk0wXg…
1
1
6
812
🚨 ALERTS{alertname="NewBlogPost", alertstate="firing"} 1
I wrote about exciting and ambitious changes we are making in @PrometheusIO project:
prometheus.io/blog/2026/02/1…
Diving into the potential future of the "native" model for the composite metric types in Prometheus. 💪
3
16
1,693
"Make me care" is probably first rule to follow in tech talks too (:
gwern.net/blog/2026/make-me-…
1
5
844
Woke up today to my blog post appearing on the top 10 of hacker news today!
Sounds like my site is up on down due to concurrent traffic... 🙃 switched to higher provider tier, but if it's down, here is a backup link: web.archive.org/web/20251111…
Side projects, blog, podcasting is hard with 2 small kids, but I eventually managed to find time for a blog! (PS: I had to switch to 5am routine 🙈)
Wrote some words about @DuffieldJesse #lazygit OSS tool and what we can learn from its UX. Enjoy! 🤗
bwplotka.dev/2025/lazygit/
1
7
793
100% this.
We are in the cycle of "unifying things", which is like going back to monoliths for DBs, collection, SDKs etc.
Tempting but maybe utopia?
BUT no one blocks ppl from trying and learning on their mistakes (: We will see in 5y cycle to move back to dedicated solutions.
There are DevOps and SRE engineers who think that a unified database for metrics and logs is a good idea. This isn't a good idea from an operations perspective because of the following reasons:
- Lower availability. If something wrong happens with the stored logs, there are high chances that this will affect metrics stored in the same database, and vice versa.
- Noisy neighbour. You cannot allocate dedicated resources (storage space and storage IO, CPU, RAM, network bandwidth) individually for metrics and logs if they are stored in the same database. These resources are shared, so the increase in logs' workload may negatively affect metrics' workload and vice versa.
- Operational complexity and efficiency. You cannot have individual backup and recovery strategies per metrics and logs stored in the same database. Logs and metrics may require different retention policies. These policies are hard to implement efficiently and clearly when logs and metrics are stored in the same database.
- Query usability and performance. Efficient querying metrics and logs are completely different things - they need different query languages optimised for typical queries over metrics and logs. They also need different optimizations at the database level for achieving high querying performance and low resource usage.
So think twice before choosing an all-in-one observability solution for metrics, logs, traces and profiles, which stores all this data into a single database, and advertises this as a feature. It usually works great at demo time and at low load in staging environments, but it may not be so great under load in production because of the issues mentioned above.
5
506
Side projects, blog, podcasting is hard with 2 small kids, but I eventually managed to find time for a blog! (PS: I had to switch to 5am routine 🙈)
Wrote some words about @DuffieldJesse #lazygit OSS tool and what we can learn from its UX. Enjoy! 🤗
bwplotka.dev/2025/lazygit/
2
2
11
1,492
FYI, @CloudNativeFdn KubeCon Europe (23-26th March) CFP closes in 3 days (12th October). What fun talks do you plan to propose? (:
events.linuxfoundation.org/k…
What'd you like to like to hear more about?
Maybe you'd like to co-speak? Happy to mentor/co-speak with passionate ppl!
1
2
554
PromCon is one month away! 🤗
We wrote all your need to know on our blog: prometheus.io/blog/2025/09/2…
6
17
1,962
Fun bugs happen, let's see if you can spot them (without looking on comments)! (:
Quiz#1: Why "make check" will never detect any formatting errors in the following snippet:
gist.github.com/bwplotka/5c6…
2
470
Thinking about starting writing more again (blog posting, social media).. should I?
I have some engineering/oss/mentoring topics queued for too long 🙈
7
33
1,991
Ever dreamed to be mentored by @PrometheusIO community; get skilled in high performance monitoring databases, @golang and help #opensource on the way?
Apply today on the LFX website 🤗
mentorship.lfx.linuxfoundati…
Applications for @PrometheusIO LFX mentorships open today!
We have some highly impactful projects this time, around Prometheus OTel UX, Remote Write 2.0, and Native summaries.
Go apply to work with some really cool folks, and learn while you're at it! 🔥
github.com/cncf/mentoring/bl…
1
4
17
1,660
Bartłomiej Płotka retweeted
Applications for @PrometheusIO LFX mentorships open today!
We have some highly impactful projects this time, around Prometheus OTel UX, Remote Write 2.0, and Native summaries.
Go apply to work with some really cool folks, and learn while you're at it! 🔥
github.com/cncf/mentoring/bl…
2
11
22
3,214
Bartłomiej Płotka retweeted
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! 💪
1
2
6
618
Bartłomiej Płotka retweeted
Today is a good day! #golang
go.dev/blog/error-syntax
"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 handling, without further investigation."
68
119
941
374,264
