Konrad Reiche

Got the beta access. Spent way more time on Superlogical Rex than I prolly should have. Ended up building herdr-reviwr for it. The server API makes it way to easy to build extensions around it. You can write exts in any language since you'd just be talking with the server API. #Go works great!

Pro-tip from someone who does security: Stop answering your phone and reading your email, and your phishing risk drops dramatically.

Go spins in both of its mutexes, but there's no sync.SpinMutex. Why? My GopherCon Africa talk, now a 4-part series: alexrios.me/blog/go-spin...

Last year you told us what to fix. This year we shipped a new go fix. Coincidence? Not entirely. The 2026 Go Developer Survey is open through Nov 3 -- tell us what’s next: blink.qualtrics.com/jfe/form/SV_...

Throwback to September, when I spoke at GopherCon Latam in Brazil 🇧🇷 Afterwards, I gave a short interview about why I gave this talk again and whether Go's principle of writing code for the reader, not the writer, still matters when AI is writing most of the code.

No more leap seconds, ever! There isn’t one in December and they will be abolished in May. The last one will forever be the 2016(?!) one. Didn’t realize having experienced leap seconds in prod dates me. I’m not going to miss time going backwards, I’ll be honest. www.bipm.org/en/cgpm-2026...

New bible just dropped. cloud.google.com/blog/product...

Randomly stumbled upon 97 Things Every Software Architect Should Know as an audiobook and it's too painful to listen to. Every statement is concise and hits home that I'm still processing one statement when the next one drops!

Code has become cheap. Code review is becoming cheap. So what is still scarce? Good decisions and good taste.

I don't use panic much, so I didn't notice that you can pass any value to it and get that value back via recover. See for example in the Go standard library go.dev/src/go/parse... That doesn't mean I'd recommend making extensive use of it 😉

I’m very, very happy to share that I have just joined the core Go team at Google to work on the Go runtime and compiler! I’ve been pitching in as an external contributor since 2018, but now my very enjoyable hobby is becoming my day job 😅 (Also, my name is PJ 👋)

#GopherConJP [📣 Announcement 📣] GopherCon Japan 2027 date & venue are officially set! 🎉🇯🇵 🗓️ Date: Feb 13–14, 2027 (Sat–Sun) 🏢 Venue: Abema Towers More details, including CFPs, will be announced shortly. Stay tuned for more!

One of my blog posts was discussed on r/golang and some readers described opening my blog as getting flashbanged 💥 A good time to add color preference support.

Genuinely surprised by how well using the CSS property filter: invert(1) hue-rotate(180deg) works as a band-aid for dark mode across different images.

Code review to find bugs should disappear. Let it validate decisions, e.g. does the chosen implementation add painful complexity? Code review gets a bad reputation when draft work is submitted restating the code. Reviews shine with why the code is needed and why the specific approach was chosen.

Write about how software engineering is changing inside your company / team / project. Don’t use AI. Win $10K and get published in The Pragmatic Engineer. You have a month: submit by 4 October. Details: blog.pragmaticengineer.com/how-software...

Excellent point from @eltonminetto.dev in his closing keynote at GopherCon Latam. The tooling we build to help humans also gives agents what they need, a fast feedback loop. Compile, test, lint, benchmark, repeat. We should automate, step by step, the same process a human would follow.

At GopherconLatam, watching @konradreiche.com 's talk

Great talk from @alexrios.me on spin locks in Go at GopherCon Latam. They can outperform sync.Mutex, but only under a narrow set of conditions: a critical section under 100 ns, proven contention, multi-core deployment, and why Go generally favors safety, portability, and fairness over exposing them.

Oi, GopherCon Latam! I made it to Florianópolis 🇧🇷 Looking forward to giving my talk "When Go Style Stops Being Style", where I'll dissect Go conventions we've found to scale well in large repositories and why conventions still matter in the age of AI.

Congrats to Go co-creator Rob Pike on receiving the 2026 USENIX Lifetime Achievement Award (The Flame)! 🔥 Rob’s impact spans Go, UTF-8, Plan 9, & Unix programming classics. 📺 Watch acceptance speech: youtu.be/wSXATB0H1DY 📖 USENIX citation: www.usenix.org/about/awards...

Excited to be heading to GopherCon Latam in Florianópolis, Brazil 🇧🇷 Looks like I'm willing to travel 6,600 miles to talk about Go, my furthest one so far. See you there 🌎

Profile-guided optimization in Go https://lemire.me/blog/2026/08/09/profile-guided-optimization-in-go/

Evidence so far suggests that it’s easier to discover previously unknown proofs in math and make new scientific discoveries than it is to make UI tests in Xcode pass reliably

I haven't found a good answer to this yet. When exposing a seed for a PCG RNG, is it better to accept both the state seed and stream value or accept one seed and derive the other? I'm using it for a finite Zipf generator.

A great take. Why should we care? Why are we here? Many will think AI does a better job at this, but chances are you haven't told it why.

The Electron era of CLIs

Another great post by @rednafi.com for go lang devs. This time all about modernizers and `go fix` CLI tool. "Modernizers & go fix" rednafi.com/go/gofix/ #golang

Co-worker asked what programming languages I learned in high school. I said Borland Delphi and they asked if I went to high school in the 90s. A fair but devastating burn.

Sorry for the delay, here is the link. docs.google.com/presentation...

[ ] I’m in this photo and I don’t like it

used this for the first time today and it rocks. incredibly powerful go.dev/blog/synctest

Most nil checks I see in Go aren't defensive programming. They're a sign that the code lost track of what can and cannot be nil. A nil check is good when it enforces a real boundary. It's suspicious when it silently handles a state your program claims is impossible konradreiche.com/blog/excessi...

Google Maps the moment you start directions: "There's a 20 minute delay, but you're still on the fastest route." Nothing you can do about it. Just thought you should know.

I got to meet Steve Yegge in Montreal. Super nice guy and we had a short but interesting conversation. TL;DR We need to recognize developers are writing code even when a tool is performing the work. Engineering means the developer steers the model, not the other way around.

Getting Started with Windows 2000 Professional

i wrote a post about the growing divide between AI skeptics and AI enthusiasts. wins and costs are both real, but too often fall on different groups of people. when you're only experiencing half the story, it's too easy to write each other off. charitydotwtf.substack.com/p/ai-enthusi...

Sway 1.12 is out, and we're getting showered in features: HDR10 output, individual window capture, a friendlier approach to NVIDIA GPUs, and new Wayland protocol support tying together color management, workspaces, and more github.com/swaywm/sway/...

I just published a proposal for a new RSS profile type for Go. It aims to solve the issue that the heap profile typically shows < 50% of process RSS, which is very confusing. It should also help to quickly identify when memory usage is dominated by cgo. github.com/golang/go/is...

We need to talk about excessive nil pointer checks in Go. Writing code that's safe and prevents panics is excellent, but when we reach the point where no pointer can be trusted, we've dug ourselves into a hole.

It's only a discussion right now but opaque + sum types = efficient oneofs github.com/golang/go/is...

Interesting finding from benchmarks, protobuf's Go opaque API was a win for elementary fields, but the gains fell off once those fields were wrapped in oneof.

What's new in gopls 22: go.dev/gopls/release/v0.22.0 Please try it out: $ go install golang.org/x/tools/gopls@latest

Ideally, middleware execution order shouldn't matter, but consider caching, error wrapping, and concurrency limiting. go-redis changed: 2020 FIFO to LIFO: github.com/redis/go-red... 2023 LIFO to FIFO: github.com/redis/go-red... The lesson: in lack of order-invariance, have a test to check for it.

Quality-of-life improvement: adding a test helper package that lets you construct context variants in one line, without anonymous functions in table-driven tests: ctxtest.New(t, ctxtest.WithCanceled(true)) The kind of package you create after wishing it existed for the fifth time.

Remember when it was called source code, not just code?

I don't always make open source contributions, but when I do, it feels like this.

One of my favorite Go proverbs: write code, don't design types.