"Software is free as in puppies. It will pee in your bedroom and eat your furniture. The weight of every line of code is real. We will need to maintain it. We will need to port it. It goes into the context window. Someone will get paged at 2 a.m. unexpectedly." ― @industrialempathy.com

"In a thoughtful piece, Azeem Azhar, the technology writer, describes his efforts to safeguard 'the space where ideas arrive before they’re shaped'. But how many of us will put in such careful, reflective effort to protect our most generative spaces of thought?"

I was happy to see JetBrains release modern Go guidelines for AI agents. That said, we added go fix ./... to our formatter and CI, and it quietly solved most of it. The Go team keeps surprising by turning rules into deterministic tooling.

Great read from @apenwarr.ca. Reviews don't scale. Each approval step turns minutes into days of waiting. They catch issues, but after the code is written. The system already allowed them. Repeated comments point to missing boundaries and unclear APIs apenwarr.ca/log/20260316

If adding less code feels impossible, that's a signal that we should consolidate what already exists instead of extending it. AI increases how fast we can add solutions. It does not increase how much system complexity we can hold in our heads.

Watching capable engineers ship large amounts of AI-generated code at an impressive velocity. It was never hard to add more code. The hard part is adding less. We optimize locally. A new problem appears, so we add another piece of code that solves it. The system becomes harder to reason about.

„There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.“ — C. A. R. Hoare

I've just released a new version of the "sh" #golang module, including initial Zsh support in shfmt, as well as many improvements and fixes to the parser and interpreter 🎉

📣 The #GopherCon Call for Speakers is officially closed! A huge thank you to everyone who submitted a talk proposal. We received 150+ submissions, and our Evaluation Committee is now diving into the review process. Stay tuned as programming is expected to go live in early May. #RoadToGopherCon

This one is pretty funny go.dev/issue/77934. Turns out a struct used for Go ←→ Linux syscalls use int64 when Linux expects int32. But by chance this can't cause a bug because: 1. it is the last field of the struct 2. the size of the struct doesn't change since C aligns int64 to 8 bytes on 32 bits

Less than 24 hours until the @gophercon.com call for speakers closes. I started editing my proposal, then remembered the German word "verschlimmbessern" (to improve something for the worse). Turns out it was already where it needed to be. Threw out the edits 👋🗑️

Excellent example of how a data race can produce a value that was never assigned. This is what undefined behavior can look like in practice: go.dev/play/p/HuIoL...

Very cool Go library from @dronnix.bsky.social. It implements a Black-White Array, an ordered structure with O(log n) operations but far fewer allocations than B-Trees. Cache-friendly and supports duplicates github.com/dronnix/bwarr

🎤 The #GopherCon stage is calling… Dreaming of your mic drop moment? Just 2 weeks left to wow us with your #golang talk proposal! Submit by March 4th 👇 sessionize.com/gophercon-20... #RoadToGopherCon

“Using go fix to modernize Go code” by Alan Donovan — https://go.dev/blog/gofix #golang

It's conference talk proposal season again! In 2024 I had the privilege of reviewing 233 proposals as part of the GopherCon review committee. Most scored below 3/5, not because they were bad, but because they missed the critical piece. I wrote up what I learned: konradreiche.com/blog/what-go...

A colleague shared this Go library that can redefine functions at runtime. I assumed it was a joke. It was not a joke. I'm going to pretend I never saw this github.com/pboyd/redefine

I'm putting the finishing touches on the Staticcheck update for #golang 1.26. You can expect a release by the end of the week.

#GopherConSG is back for 2026! Our next conference will take place on 20–22 May, and our #CFP is open right now! 💥 If you have #golang ideas to share, we're looking forward to hearing all about them! 🙋‍♀️🙋‍♂️ www.papercall.io/gopherconsg-...

Looks like @gophercon.sg is scheduled for May 20–22 🇸🇬 2026.gophercon.sg

Interesting expansion of generics in #golang 👀

I'd been feeling pretty good about leveling up my Vim refactoring skills with regex find/replace and :argdo. Then I wrote my first gopatch, applied it across the codebase, and there's no going back github.com/uber-go/gopa...

Sitting at home in San Francisco, drinking coffee from a Stuttgart Gophers mug that was given to me at the @golab.io conference in Florence, Italy. I find this quite telling of how international the Go community is.

Differential Coverage for Debugging research.swtch.com/diffcover

While I am quietly rooting for Framework laptops, I am genuinely surprised to see Lenovo embracing repairability again. ThinkPad X1 Carbon Gen 14 coming with a modular keyboard and USB C ports is not what I was expecting www.notebookcheck.net/Repairabilit...

Hi @antonz.org, good question! Something like 'make([]byte, 0, 33)' does indeed create a slice with a capacity of exactly 33, as your example shows. However, the underlying allocated heap object actually is larger. Quick playground example that hacks things to print the heap object size:

PSA: go.sum is not a lockfile. You never need to look at go.sum. go.mod has everything you need.

Less "AI write my code" and more "AI show me where I'm slow": recording Vim keystrokes with vim -w, then analyzing them to find repetitive patterns and adopt better motions and commands.

Profiling Request Latency with Critical Path Analysis, @felixge.de @ GopherCon 2025 www.youtube.com/watch?v=BayZ...

I cannot think of a single thing that could possibly go wrong.

This Go memory allocation explanation is seriously awesome😍 nghiant3223.github.io/2025/06/03/m... #golang

Accepted! Go 1.26 will include a SECRET package. Don't tell anyone about it 🤫 Just kidding. The package wipes the memory to keep secrets safe — hence the name. antonz.org/accepted/run...

Amazon’s phrasing is “Designed to provide 99.999999999% durability …” docs.aws.amazon.com/AmazonS3/lat... Andy Warfield gave a pretty good explanation of what they do to achieve this. youtu.be/sc3J4McebHE?...

The Computer Wants to Lose Your Data: Bonus Bits A footnote to my #SREcon talk on how databases implement crash safety, with extra details for database nerds ✌🏻💖 blog.sinjakli.co.uk/2025/11/29/t... #Postgres #MySQL

Small contribution just before the Go 1.26 freeze: go.dev/cl/610815 removes the hard-coded 100ms sleep from the CPU profiler for most platforms. This will make it more efficient and unblock deeper call stacks. As a bonus, uncovered and fixed an 8 year old bug in the profiler go.dev/cl/722940 :)

Bookmark this Go enum solution 🔖 It may look heavy at first, but it covers everything. I often forget that the type safety comes from hiding the string inside a struct, which prevents direct access. With unqualified field syntax, you can still define the values without clutter.

Compile-Time Safety for Enumerations in Go by @vladimir.varank.in vladimir.varank.in/notes/2023/0...

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