Konrad Reiche
@konradreiche.com
Writing ⌯Go at Reddit
konradreiche.com
konradreiche.com
Reposted by Konrad Reiche
I cannot think of a single thing that could possibly go wrong.
December 28, 2025 at 12:39 AM
I cannot think of a single thing that could possibly go wrong.
Reposted by Konrad Reiche
This Go memory allocation explanation is seriously awesome😍
nghiant3223.github.io/2025/06/03/m...
#golang
nghiant3223.github.io/2025/06/03/m...
#golang
Memory Allocation in Go
Memory Allocation in Go
nghiant3223.github.io
December 25, 2025 at 2:37 AM
This Go memory allocation explanation is seriously awesome😍
nghiant3223.github.io/2025/06/03/m...
#golang
nghiant3223.github.io/2025/06/03/m...
#golang
Reposted by Konrad Reiche
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...
Just kidding. The package wipes the memory to keep secrets safe — hence the name.
antonz.org/accepted/run...
Go proposal: Secret mode
Automatically erase memory to prevent secret leaks.
antonz.org
December 9, 2025 at 10:31 AM
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...
Just kidding. The package wipes the memory to keep secrets safe — hence the name.
antonz.org/accepted/run...
Reposted by Konrad Reiche
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?...
docs.aws.amazon.com/AmazonS3/lat...
Andy Warfield gave a pretty good explanation of what they do to achieve this.
youtu.be/sc3J4McebHE?...
FAST '23 - Building and Operating a Pretty Big Storage System (My Adventures in Amazon S3)
YouTube video by USENIX
youtu.be
December 8, 2025 at 9:57 AM
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?...
docs.aws.amazon.com/AmazonS3/lat...
Andy Warfield gave a pretty good explanation of what they do to achieve this.
youtu.be/sc3J4McebHE?...
Reposted by Konrad Reiche
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
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
November 29, 2025 at 1:06 PM
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
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
Reposted by Konrad Reiche
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 :)
November 23, 2025 at 6:48 PM
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.
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.
Though that will work for compiler protection is that simple scenario, using an interface creates other problems. I think this is a better solution and the one I teach.
github.com/ardanlabs/se...
github.com/ardanlabs/se...
service/business/types/role/role.go at master · ardanlabs/service
Starter-kit for writing services in Go using Kubernetes. - ardanlabs/service
github.com
November 16, 2025 at 8:45 PM
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.
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...
Compile-time safety for enumerations in Go
Last month, a colleague of mine asked how to reason about enumerated values (“enums”) in Go. They wanted to benefit from Go’s type-safety and to prevent users from misusing the package.
For an imagina...
vladimir.varank.in
November 15, 2025 at 3:08 AM
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?
November 3, 2025 at 8:51 PM
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?
Reposted by Konrad Reiche
“The Green Tea Garbage Collector” by Michael Knyszek and Austin Clements — https://go.dev/blog/greenteagc
#golang
#golang
October 29, 2025 at 4:59 PM
“The Green Tea Garbage Collector” by Michael Knyszek and Austin Clements — https://go.dev/blog/greenteagc
#golang
#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...
From the golang community on Reddit: Writing Better Go: Lessons from 10 Code Reviews
Explore this post and more from the golang community
www.reddit.com
October 23, 2025 at 7:51 PM
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.
October 16, 2025 at 12:54 PM
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...
Writing Better Go: Lessons from 10 Code Reviews
Why do Go developers obsess over variable names, error handling, and interfaces, even when your approach does the job, too? Whether gently or not so gen…
speakerdeck.com
October 14, 2025 at 8:58 AM
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/...
Syntax highlighting is a waste of an information channel
No newsletter next week Running the TLA+ workshop. No way I'm gonna have any brainpower after that. Syntax highlighting is a waste of an information channel...
buttondown.com
October 13, 2025 at 5:51 PM
“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.
October 10, 2025 at 7:14 AM
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.
October 10, 2025 at 6:59 AM
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.
October 7, 2025 at 10:07 AM
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...
@goinggo.net shared a treasure trove of programming quotes during the @golab.io lightning talks session, check it out:
github.com/ardanlabs/go...
October 6, 2025 at 2:23 PM
“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...
@goinggo.net shared a treasure trove of programming quotes during the @golab.io lightning talks session, check it out:
github.com/ardanlabs/go...
Reposted by Konrad Reiche
“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
Totally agree! Naming is hard, but getting names right can dramatically improve software design, as often one thing leads to another. #golang
October 6, 2025 at 9:29 AM
“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
Totally agree! Naming is hard, but getting names right can dramatically improve software design, as often one thing leads to another. #golang
Reposted by Konrad Reiche
👏 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
#golang #golab2025 @konradreiche.com
October 6, 2025 at 9:21 AM
👏 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
#golang #golab2025 @konradreiche.com
Reposted by Konrad Reiche
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
⏰ 10:45
📍 Leonardo Room!
#golang #golab2025 @konradreiche.com
October 6, 2025 at 8:30 AM
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
⏰ 10:45
📍 Leonardo Room!
#golang #golab2025 @konradreiche.com
Reposted by Konrad Reiche
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
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
GoLab | The International Conference on Go in Florence
GoLab is a conference for developers made by developers
golab.io
October 4, 2025 at 9:45 AM
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
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/...
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/...
Staff Software Engineer, ML Ranking Platform
Remote - United States
job-boards.greenhouse.io
September 29, 2025 at 3:28 PM
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/...
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.
September 27, 2025 at 9:34 PM
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.
Reposted by Konrad Reiche
And now it looks like #GopherConUK started publishing videos!
September 18, 2025 at 12:02 PM
And now it looks like #GopherConUK started publishing videos!