Bartłomiej Płotka (@bwplotka) 's Twitter Profile
Bartłomiej Płotka

@bwplotka

Senior SWE TL @Google | ex Principal @RedHat | @ThanosMetrics @PrometheusIO | Bsky: bsky.app/profile/bwplot… | Efficient Go 📖 @OReillyMedia

ID: 4017328455

linkhttps://bwplotka.dev calendar_today22-10-2015 14:16:13

7,7K Tweet

6,6K Takipçi

797 Takip Edilen

Sundar Pichai (@sundarpichai) 's Twitter Profile Photo

Introducing Willow, our new state-of-the-art quantum computing chip with a breakthrough that can reduce errors exponentially as we scale up using more qubits, cracking a 30-year challenge in the field. In benchmark tests, Willow solved a standard computation in <5 mins that would

Bartłomiej Płotka (@bwplotka) 's Twitter Profile Photo

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! 💪🏽

Bartłomiej Płotka (@bwplotka) 's Twitter Profile Photo

Looks like Go 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/

Bartłomiej Płotka (@bwplotka) 's Twitter Profile Photo

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?

Bartłomiej Płotka (@bwplotka) 's Twitter Profile Photo

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

Epic discussion around <a href="/golang/">Go</a> error handling:   github.com/golang/go/disc… 

Adventurous ideas. Ofc there might something to improve, but the following image is still applicable: 🙈
Arthur Silva Sens (@arthursilvasens) 's Twitter Profile Photo

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 ❤️

Mat Ryer (@matryer) 's Twitter Profile Photo

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.

Nicolas Takashi (@ntakashics) 's Twitter Profile Photo

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

Bartłomiej Płotka (@bwplotka) 's Twitter Profile Photo

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

Saswata Mukherjee (@saswatamcode) 's Twitter Profile Photo

Saumya Shah Thanos Monitoring Christine 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! 💪

William (Bill) Kennedy (@goinggodotnet) 's Twitter Profile Photo

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