<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>@bwplotka</title><link>https://bwplotka.dev/</link><description>bwplotka blog 💪💻🏐</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>bwplotka@gmail.com (Bartek Płotka)</managingEditor><webMaster>bwplotka@gmail.com (Bartek Płotka)</webMaster><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 10 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://bwplotka.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>The (lazy) Git UI You Didn't Know You Need</title><link>https://bwplotka.dev/2025/lazygit/</link><pubDate>Mon, 10 Nov 2025 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2025/lazygit/</guid><description>&lt;div class="featured-image">
&lt;img src="/og-images/lazygit.png" referrerpolicy="no-referrer">
&lt;/div>When my son was born last April, I had ambitious learning plans for the upcoming 5w paternity leave. As you can imagine, with two kids, life quickly verified this plan 🙃. I did eventually start some projects. One of the goals (sounding rebellious in the current AI hype cycle) was to learn and use neovim for coding. As a Goland aficionado, I (and my wrist) have always been tempted by no-mouse, OSS, gopls based, highly configurable dev setups.</description></item><item><title>Optimizing in-process gRPC with Go 1.23 Iterators and Coroutines</title><link>https://bwplotka.dev/2025/go-grpc-inprocess-iter/</link><pubDate>Mon, 20 Jan 2025 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2025/go-grpc-inprocess-iter/</guid><description>&lt;div class="featured-image">
&lt;img src="/og-images/gophermetrics.png" referrerpolicy="no-referrer">
&lt;/div>A few years back I have been exploring solutions for the in-process gRPC pattern in Go, for the Thanos project . Recently, a friend and a Thanos maintainer Filip refreshed the initial Thanos solution with the new Go 1.23 iterators .
This created a perfect opportunity to share, in a co-authored blog post, what Filip and I learned about the new iterators, new coroutines (not goroutines!) and what options you have for the production in-process gRPC logic.</description></item><item><title>Leveraging benchstat Projections in Go Benchmark Analysis!</title><link>https://bwplotka.dev/2024/go-microbenchmarks-benchstat/</link><pubDate>Mon, 30 Sep 2024 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2024/go-microbenchmarks-benchstat/</guid><description><![CDATA[<div class="featured-image">
                <img src="/og-images/gophermetrics.png" referrerpolicy="no-referrer">
            </div>Go&rsquo;s built-in micro-benchmarking framework is extremely useful and widely known. Sill, not many developers are aware of the additional, yet essential, benchstat tool allowing clear comparisons of Go A/B benchmark results across multiple runs. In 2023, benchstat received a complete overhaul making it even more powerful: projections, filtering and groupings were introduced allowing robust comparisons across any dimension, defined by your sub-benchmarks (aka &ldquo;cases&rdquo;), if you follow a certain naming format .]]></description></item><item><title>Announcing Our Book with O'Reilly: Efficient Go!</title><link>https://bwplotka.dev/2021/efficient-go/</link><pubDate>Tue, 07 Sep 2021 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2021/efficient-go/</guid><description><![CDATA[<div class="featured-image">
                <img src="/og-images/efficient-go.png" referrerpolicy="no-referrer">
            </div>TL;DR: I am super excited to announce an exact topic of our book we write together with O&rsquo;Reilly publisher. &ldquo;Efficient Go&rdquo; will consist of 10 chapters! The book is planned to be released near the end of Q1 2022. Stay Tuned! Join our Discord Community using this link or follow @bwplotka on Twitter if you want to get notified about updates, promotions, opportunities to contribute and events!
 Almost exactly seven months ago, I announced that I will be writing a book with the publisher I have always admired, O&rsquo;Reilly .]]></description></item><item><title>ThanosCon Retrospective</title><link>https://bwplotka.dev/2024/thanoscon2024/</link><pubDate>Sun, 14 Apr 2024 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2024/thanoscon2024/</guid><description><![CDATA[<div class="featured-image">
                <img src="/og-images/thanoscon1.jpg" referrerpolicy="no-referrer">
            </div>Hello back! 👋🏽 Curious how your last weeks looked like, mine were a bit busy:
 My daughter&rsquo;s 1st birthday, then she started daycare adaption with the weekly spread of stomach flu, scarlet fever and other &ldquo;collectables&rdquo;. Fun. Week of final preparations for KubeCon (~7 talks? plus booth duty, organization duties, an interview and a book signing 🙈), then super active KubeCon in Paris together with ~12 thousand attendees. Busy time at work, mostly due to the post-conference excitement syndrome and Google Next that finished this last week.]]></description></item><item><title>How To Achieve More and Go Through Boring Stuff</title><link>https://bwplotka.dev/2021/have-fun/</link><pubDate>Fri, 24 Sep 2021 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2021/have-fun/</guid><description><![CDATA[<div class="featured-image">
                <img src="/og-images/fun.png" referrerpolicy="no-referrer">
            </div>Hello Everyone! 👋
Through the recent years in open source and in my role as the Principal Software Engineer at Red Hat, I had the opportunity to do a lot of work that touches tech/team/project/organization management and leadership. During this experience, one realization stood up to me more than anything. The fact that Software Development is way more about humans than computers.
That&rsquo;s why in my blog space, I wanted to try something new!]]></description></item><item><title>Correlating Signals Efficiently in Modern Observability</title><link>https://bwplotka.dev/2021/correlations-exemplars/</link><pubDate>Sat, 08 May 2021 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2021/correlations-exemplars/</guid><description>&lt;div class="featured-image">
&lt;img src="/og-images/example1.png" referrerpolicy="no-referrer">
&lt;/div>NOTE: I wrote this article for the CNCF TAG (previously SIG) Observability Whitepaper about Observability , so you will see some of this write up there.
The Whitepaper itself, is a fantastic initiative that aims for a complete overview and state-of-the-art of modern observability. Purely community-driven and for the community! When writing this, it’s still in progress, so if you want to help writing this up or reviewing or redacting, please join our calls and #tag-observability channel on the CNCF Slack.</description></item><item><title>How Thanos Would Program in Go</title><link>https://bwplotka.dev/2020/how-thanos-would-program-in-go/</link><pubDate>Mon, 13 Apr 2020 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2020/how-thanos-would-program-in-go/</guid><description>&lt;div class="featured-image">
&lt;img src="/og-images/style-guide-header.jpg" referrerpolicy="no-referrer">
&lt;/div>TL;DR: Recently we introduced extended Go Style Guide for the Thanos project , a high scale open-source distributed metric system where, with our large community, we take extra attention and care for the code quality.
Go + Distributed Systems = ❤️ Modern, scalable backend systems can be incredibly complex. Despite our efforts with other Maintainers, to not add too many features, APIs or inconsistencies to our projects like Prometheus or Thanos, those are still large codebases.</description></item><item><title>Automate Your Documentation With mdox!</title><link>https://bwplotka.dev/2020/mdox/</link><pubDate>Sun, 22 Mar 2020 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2020/mdox/</guid><description>&lt;div class="featured-image">
&lt;img src="/og-images/mdox_initial.gif" referrerpolicy="no-referrer">
&lt;/div>Writing software documentation is hard. Maintaining it is even more challenging in both closed and open-source worlds.
You are probably familiar with the disdain that everyone has for writing, maintaining, and updating documentation, especially software engineers. But it is a necessary process that helps future teams, users and developers to use your project and contribute effectively. It might be a factor between life and death for a project or adoption game changer.</description></item><item><title>How to Become an Amazing OSS Project Maintainer, Survive, And Have Fun on The Way!</title><link>https://bwplotka.dev/2020/how-to-became-oss-maintainer/</link><pubDate>Tue, 11 Feb 2020 00:00:00 +0000</pubDate><author>Bartek Płotka</author><guid>https://bwplotka.dev/2020/how-to-became-oss-maintainer/</guid><description>In this post, I would like to share what, in my honest opinion, a &amp;ldquo;perfect&amp;rdquo; maintainer of an open source software should do. Yes, no one ever will be perfect: we all have limited time, we all make mistakes and have some skills to learn. However, there is nothing bad in defining what we should aim for. (:
Some quick glossary for this (long) post:
Maintainer: Person responsible for the open source project development and community.</description></item></channel></rss>