gopls references works really well for finding unused identifiers, like fields in a dependency struct that aren't used anymore. Is there a less hacky way to do this than writing a wrapper that loops through each field and calls gopls references with the line and column?

“The Green Tea Garbage Collector” by Michael Knyszek and Austin Clements — https://go.dev/blog/greenteagc #golang

Great to see the slides from my talk sparking lively debate on Reddit. Exactly the outcome I hoped for: people thinking seriously about the trade-offs www.reddit.com/r/golang/com...

Ah yes, another classic Comcast outage in San Francisco.

Several people asked for the slides after my GoLab talk, so here they are speakerdeck.com/konradreiche...

“Highlighting syntax is not always the most important thing to us. The information we want from code depends on what we're trying to do.” buttondown.com/hillelwayne/...

My time at @golab.io came with heavy jet lag. But leave it to @goinggo.net to close out and make it feel like you had three espressos. An immersive talk on the Go trace tool provided a sharp intuition for balancing concurrency in light of the garbage collector with respect to CPU vs. memory.

The biggest surprise at @golab.io was a talk by Nate Smith. He explored Go as a medium for creative expression, sharing art made with code. It was moving, opening a world I hadn’t seen in years; a rare fusion of craft and art, perfectly fitting for a presentation in Italy.

Excellent breakdown of the new optimized sync.Mutex spin behavior implementation by Raiza Claudino at @golab.io. Loved the Go concurrency visualizations.

“The hardest bugs are those where your mental model of the situation is just wrong, so you can't see the problem at all.” —Brian Kernighan @goinggo.net shared a treasure trove of programming quotes during the @golab.io lightning talks session, check it out: github.com/ardanlabs/go...

“Util packages are a sign of defeat” @konradreiche.com at @golab.io Totally agree! Naming is hard, but getting names right can dramatically improve software design, as often one thing leads to another. #golang

👏 Thanks to Konrad Reiche for “Writing Better Go: Lessons from 10 Code Reviews”. A great reminder that code reviews are more than nitpicks — they’re a path to clearer, pragmatic Go. 🚀 #golang #golab2025 @konradreiche.com

Konrad Reiche is about to start “Writing Better Go: Lessons from 10 Code Reviews”. Don’t miss practical insights on Go’s design philosophy and writing clearer code. 🐹💡 ⏰ 10:45 📍 Leonardo Room! #golang #golab2025 @konradreiche.com

Tomorrow is THE day! 🎉 The Gophers are landing in Florence for #GoLab2025. Last chance to check your ticket, pack your swag, and get ready for 3 amazing days of Go! 🐹 💫 👉 golab.io #GoLang

My team at Reddit is hiring a Staff Engineer (Remote US) 🚀 Love Go and distributed systems? Our infrastructure powers personalized experiences like Home Feed, Search and Push Notifications. Help us shape the vision for the next generation of our platform job-boards.greenhouse.io/reddit/jobs/...

Excited to be giving my talk at @golab.io this year! It's a distilled set of lessons from maintaining a large Go codebase with hundreds of contributors. Over time, I've gone from dismissing my comments as nitpicky to realizing they're essential for writing maintainable and safe production Go code.

And now it looks like #GopherConUK started publishing videos!

New blog post: Security through intentional redundancy commaok.xyz/post/securit...

I've been eager to get more context and commentary on those slides. Fortunately, @dave.cheney.net gave the talk again at GopherCon Europe 2025, and the recording is now live! www.youtube.com/watch?v=RZe8...

Asked my colleague if their GitHub "retro theme" was a Chrome extension. Turns out it's just high contrast mode. Retro is a good sell.

I've been looking into improving our team and platform wiki. Turns out a lot of the prior art in Confluence looks like something lifted straight from early-2000s HTML: three columns, each packed with tables of links. I can't decide if I feel more nostalgic or horrified.

London made tap-and-ride a thing in 2014. BART is unveiling it now, in 2025 www.bart.gov/news/article...

Anyone else keeping permanently closed places in their Google Maps saves? I know that bar or restaurant isn't reopening but I can't delete it... pure nostalgia until I'm actually trying to find a place to eat.

Here are the slides for my "What's coming to Go 1.25" talk at #GopherConUK! #golang

Why do Go devs nitpick your code? @konradreiche.com unpacks 10 real code reviews to reveal Go’s design philosophy — and how to write clearer, sharper code. ✍️ Writing Better Go: Lessons from 10 Code Reviews #golang #golab2025

Gopls v0.20.0 is released: go.dev/gopls/releas... $ go install golang.org/x/tools/[email protected] Docs at go.dev/gopls. Thanks to all who contributed!

Whenever I find myself going in circles with Go's type parameters, I revisit @rog.bsky.social's Generics Unconstrained talk. It's a reminder that sometimes interfaces are all you need and that unconstrained type parameters might be what you're actually looking for www.youtube.com/watch?v=eU-w...

HDR support just landed in SwayWM 🌈 Tempted to reinstall from the main branch to check it out now... or I could wait for the next release. Decisions, decisions.

Leave it to San Francisco to reinvent the weather app, again. This one's actually good.

Excellent #golang blog post with a bunch of interesting general Go performance nuggets along with an overview of a new (and fast) Protobuf parser in Go from the folks at Buf. 🚀

In Go (and other languages), I've noticed a tendency for methods to grow longer without breaking out parts into helpers. Perhaps because the code hasn't been reused yet? But that feels like a missed opportunity; pulling out a well-named helper, even once, really helps reduce cognitive load.

LLMs have made knowledge more accessible, but it's surprising how often they still get things wrong, especially about Prometheus.

Ever since I got a foldable phone and the Android Linux Terminal app, I've been wondering: how far can you take it with an external keyboard? Especially while traveling. I gave it a shot and wrote up my setup. Check it out: konradreiche.com/blog/my-trav...

unix pipes still kinda feel like they’re from the future which is embarrassing because it suggests our programming paradigms are still stuck in the distant past

I'm working on an interactive Go 1.25 tour, but there are so many changes in json/v2 that I decided to cover them in a separate blog post. Plenty of interactive examples ahead! antonz.org/go-json-v2

it is impossible to generate code comments from source code because good comments are definitionally based on things not in the source code (intent, counterfactuals, experiments, etc.)

On Learning and LLMs: "Knowledge isn't supposed to be fed to you on a plate. If you want that sort of learning, read a book—the joy in building toy projects like this comes from an exploration of the unknown, without polluting one's mind with an existing solution" blog.jsbarretto.com/post/softwar...

One useful habit I picked up from a colleague: leaving comments on my own pull requests. He would highlight key changes or suggest areas to focus on during the review, making the whole process more thoughtful.

Over five years ago, I wrote my first incident postmortem—and got my first taste of blameless culture. It was a shock, coming from fault-finding environments. I wrote a short post on how we can build empathy into our infrastructure konradreiche.com/blog/blamele...

Which function is more idiomatic: clamp or restrict? Which one speaks fluent Go?

New short blog post: Backoff-with-retry can be much simpler. commaok.xyz/post/simple-... Also, maybe peek at commaok.xyz/post/blog-sc....

I've been on a quest to cut down notification noise 🔕 Every time I disable alerts for an app, I worry I'll miss something important. And every time, I'm proven wrong—I forget I even turned them off. It makes me wonder: what would we miss if we turned off all notifications?

Code comments and pull request descriptions are way more useful when they explain why something exists or changed. The what and how are usually easy to figure out; it's the why that really helps things click.

Haven't been to a Go meetup in ages! Looking forward to the one in San Francisco today lu.ma/fn57nlhh

Gophers worldwide, please welcome the first GoLab 2025 sponsor: GOOGLE! opensource.google We are overexcited! 😊 If you wanna join them please click here: golab.io/sponsors

I really enjoy writing Go tests, starting simple and evolving them into table-driven tests. I can usually cover any behavior, but it gets tricky when I look at my tests after days, weeks, or months, especially understanding why certain inputs or assertions were used.

We are proud to announce the Schedule for GoLab 2025! It’s not completed yet: there will be some minor changes or additions, especially in the workshops and social events areas, but this is it! Take a look at it and join us now! golab.io/schedule

Still on Arch with Sway though: stripped-down, just what I need. The only real headaches have been Nvidia, especially Optimus and Lenovo’s graphics multiplexer on the X1 Extreme. Compared to my ThinkPad Nano, it's been night and day.

Funny how you sometimes see a term before the definition. I thought vibe coding meant leaning into whatever part of the code feels right in the moment just to get into the flow.

New experimental garbage collector for Go programs! github.com/golang/go/is...