Alex Rios
@alexrios.me
Former Carioca 🏖 living in Curitiba 🏔 ⛩️ Supreme Leader ⛩️ Author of System Programming Essentials with Go & Learning Zig. Posts about Tech Leadership, Go and Zig. He/Him
Atualizei o material sobre Go Modules em português até o Go 1.27 💚
Saímos do GitBook e ganhamos casa nova:
gomodules.alexrios.me
Exemplos revisados e contribuições abertas. Material em português merece circular 🇧🇷
Saímos do GitBook e ganhamos casa nova:
gomodules.alexrios.me
Exemplos revisados e contribuições abertas. Material em português merece circular 🇧🇷
October 1, 2026 at 2:08 PM
Atualizei o material sobre Go Modules em português até o Go 1.27 💚
Saímos do GitBook e ganhamos casa nova:
gomodules.alexrios.me
Exemplos revisados e contribuições abertas. Material em português merece circular 🇧🇷
Saímos do GitBook e ganhamos casa nova:
gomodules.alexrios.me
Exemplos revisados e contribuições abertas. Material em português merece circular 🇧🇷
Reposted by Alex Rios
Simplicity gets agreed and then broken by a flag added for one caller. Hard caps beat intentions, because the linter doesn't get tired at 5pm. Tenets don't stop the deadline, but a cap the build enforces does.
prickles.org/tenet/simpli...
prickles.org/tenet/simpli...
F4 Simplicity · Prickles
F4 Simplicity: No line of code is cheaper than the one you didn't write. Reasoning, evidence, the counter-argument and the reply, on Prickles.
prickles.org
September 29, 2026 at 8:06 AM
Simplicity gets agreed and then broken by a flag added for one caller. Hard caps beat intentions, because the linter doesn't get tired at 5pm. Tenets don't stop the deadline, but a cap the build enforces does.
prickles.org/tenet/simpli...
prickles.org/tenet/simpli...
I updated slogbox for Go 1.27 and JSON v2.
I wrote about the migration decisions: what to preserve in the JSON output and how to handle errors after part of an HTTP response has already been sent.
alexrios.me/blog/slogbox...
I wrote about the migration decisions: what to preserve in the JSON output and how to handle errors after part of an HTTP response has already been sent.
alexrios.me/blog/slogbox...
Updating slogbox for Go 1.27
A Go 1.27 upgrade exposed a JSON contract, an HTTP error-design flaw, and a benchmark that looked fast because it failed early
alexrios.me
September 28, 2026 at 2:50 PM
I updated slogbox for Go 1.27 and JSON v2.
I wrote about the migration decisions: what to preserve in the JSON output and how to handle errors after part of an HTTP response has already been sent.
alexrios.me/blog/slogbox...
I wrote about the migration decisions: what to preserve in the JSON output and how to handle errors after part of an HTTP response has already been sent.
alexrios.me/blog/slogbox...
Atualizei o slogbox para Go 1.27 e JSON v2.
Escrevi sobre as decisões da migração: o que preservar no JSON e como lidar com erros quando parte da resposta HTTP já foi enviada.
alexrios.me/blog/slogbox...
Escrevi sobre as decisões da migração: o que preservar no JSON e como lidar com erros quando parte da resposta HTTP já foi enviada.
alexrios.me/blog/slogbox...
Atualizando o slogbox para o Go 1.27
A atualização para Go 1.27 expôs um contrato JSON, uma falha no design de erros HTTP e um benchmark que parecia rápido porque falhava cedo
alexrios.me
September 28, 2026 at 2:50 PM
Atualizei o slogbox para Go 1.27 e JSON v2.
Escrevi sobre as decisões da migração: o que preservar no JSON e como lidar com erros quando parte da resposta HTTP já foi enviada.
alexrios.me/blog/slogbox...
Escrevi sobre as decisões da migração: o que preservar no JSON e como lidar com erros quando parte da resposta HTTP já foi enviada.
alexrios.me/blog/slogbox...
Hey Gophers, I need your help!
What theme should I send to @gophercon.jp call for papers?
I have only 2 submissions!
Don't say Green Tea GC internals. It's the first one 🤓.
What theme should I send to @gophercon.jp call for papers?
I have only 2 submissions!
Don't say Green Tea GC internals. It's the first one 🤓.
September 27, 2026 at 3:52 AM
Hey Gophers, I need your help!
What theme should I send to @gophercon.jp call for papers?
I have only 2 submissions!
Don't say Green Tea GC internals. It's the first one 🤓.
What theme should I send to @gophercon.jp call for papers?
I have only 2 submissions!
Don't say Green Tea GC internals. It's the first one 🤓.
A module can look encapsulated while another reaches straight into its state. I wrote about transparent boundaries, with a Go example that moves mutation back to its owner.
alexrios.me/blog/patholo...
alexrios.me/blog/patholo...
September 14, 2026 at 4:36 PM
A module can look encapsulated while another reaches straight into its state. I wrote about transparent boundaries, with a Go example that moves mutation back to its owner.
alexrios.me/blog/patholo...
alexrios.me/blog/patholo...
Continuando os posts sobre aspectos fundamentais de design 🌞
Nesse post, exploro as "fronteiras transparentes".
alexrios.me/blog/patholo...
Nesse post, exploro as "fronteiras transparentes".
alexrios.me/blog/patholo...
Fronteiras transparentes
O encapsulamento que só existe na aparência
alexrios.me
September 14, 2026 at 4:35 PM
Continuando os posts sobre aspectos fundamentais de design 🌞
Nesse post, exploro as "fronteiras transparentes".
alexrios.me/blog/patholo...
Nesse post, exploro as "fronteiras transparentes".
alexrios.me/blog/patholo...
Seguindo a série sobre fundamentos de design de software: flags booleanas e estados que não deveriam existir.
alexrios.me/blog/bool-fl...
alexrios.me/blog/bool-fl...
Flags booleanas e estados que não deveriam existir
De parâmetros booleanos ambíguos a campos contraditórios: explicite as operações e modele apenas os estados que o domínio permite.
alexrios.me
September 7, 2026 at 7:24 PM
Seguindo a série sobre fundamentos de design de software: flags booleanas e estados que não deveriam existir.
alexrios.me/blog/bool-fl...
alexrios.me/blog/bool-fl...
Continuing my posts on software design fundamentals, this time I’m looking at boolean flags and states our types should not allow.
Boolean flags and states that should not exist
From ambiguous boolean parameters to contradictory struct fields: make operations explicit and model only the states the domain allows.
alexrios.me
September 7, 2026 at 7:23 PM
Continuing my posts on software design fundamentals, this time I’m looking at boolean flags and states our types should not allow.
The world tour continues relentlessly. I keep submitting talks and somehow people keep accepting them.
Next stop: GoLab 2026, Bologna 🇮🇹
Talking about Green Tea GC, Go’s new garbage collector, and why “scan spans, not objects” turns out to be a much bigger idea than it first appears.
Next stop: GoLab 2026, Bologna 🇮🇹
Talking about Green Tea GC, Go’s new garbage collector, and why “scan spans, not objects” turns out to be a much bigger idea than it first appears.
September 7, 2026 at 3:10 PM
The world tour continues relentlessly. I keep submitting talks and somehow people keep accepting them.
Next stop: GoLab 2026, Bologna 🇮🇹
Talking about Green Tea GC, Go’s new garbage collector, and why “scan spans, not objects” turns out to be a much bigger idea than it first appears.
Next stop: GoLab 2026, Bologna 🇮🇹
Talking about Green Tea GC, Go’s new garbage collector, and why “scan spans, not objects” turns out to be a much bigger idea than it first appears.
My slides from GopherCon LATAM 2026 are now available:
🇧🇷 PT-BR
talks.alexrios.me/gc-latam-26-...
🇪🇸 ES
talks.alexrios.me/gc-latam-26-...
🌎 EN
talks.alexrios.me/gc-latam-26-...
Hope they’re useful even if you couldn’t make it to the talk.
🇧🇷 PT-BR
talks.alexrios.me/gc-latam-26-...
🇪🇸 ES
talks.alexrios.me/gc-latam-26-...
🌎 EN
talks.alexrios.me/gc-latam-26-...
Hope they’re useful even if you couldn’t make it to the talk.
September 7, 2026 at 1:39 PM
My slides from GopherCon LATAM 2026 are now available:
🇧🇷 PT-BR
talks.alexrios.me/gc-latam-26-...
🇪🇸 ES
talks.alexrios.me/gc-latam-26-...
🌎 EN
talks.alexrios.me/gc-latam-26-...
Hope they’re useful even if you couldn’t make it to the talk.
🇧🇷 PT-BR
talks.alexrios.me/gc-latam-26-...
🇪🇸 ES
talks.alexrios.me/gc-latam-26-...
🌎 EN
talks.alexrios.me/gc-latam-26-...
Hope they’re useful even if you couldn’t make it to the talk.
Reposted by Alex Rios
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.
September 2, 2026 at 8:06 PM
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.
Tito Lívio diz que Roma reprimiu as Bacanais por assassinato, uso de veneno e fraude.
O único documento oficial contemporâneo que sobreviveu não menciona nada disso. Ele fala de caixa, juramentos, cargos e reuniões.
O que essa diferença revela?
O único documento oficial contemporâneo que sobreviveu não menciona nada disso. Ele fala de caixa, juramentos, cargos e reuniões.
O que essa diferença revela?
August 22, 2026 at 8:06 PM
Tito Lívio diz que Roma reprimiu as Bacanais por assassinato, uso de veneno e fraude.
O único documento oficial contemporâneo que sobreviveu não menciona nada disso. Ele fala de caixa, juramentos, cargos e reuniões.
O que essa diferença revela?
O único documento oficial contemporâneo que sobreviveu não menciona nada disso. Ele fala de caixa, juramentos, cargos e reuniões.
O que essa diferença revela?
Most Go design problems don't start with architecture. They start with a function accepting more than it needs.
I shared thoughts about precise signatures, small interfaces, and why every parameter should be an honest contract.
alexrios.me/blog/stamp-c...
I shared thoughts about precise signatures, small interfaces, and why every parameter should be an honest contract.
alexrios.me/blog/stamp-c...
Precision is the missing virtue in Go interfaces
Every parameter is a contract. Make it small enough to honor
alexrios.me
August 20, 2026 at 2:14 AM
Most Go design problems don't start with architecture. They start with a function accepting more than it needs.
I shared thoughts about precise signatures, small interfaces, and why every parameter should be an honest contract.
alexrios.me/blog/stamp-c...
I shared thoughts about precise signatures, small interfaces, and why every parameter should be an honest contract.
alexrios.me/blog/stamp-c...
Processo dá uma sensação poderosa de controle.
Quando a org cresce, essa sensação pode virar uma armadilha: mais etapas, mais aprovações, mais rituais e mais governança começam a parecer uma resposta para problemas que, muitas vezes, são de contexto, autonomia, competência ou desenho da cia.
Quando a org cresce, essa sensação pode virar uma armadilha: mais etapas, mais aprovações, mais rituais e mais governança começam a parecer uma resposta para problemas que, muitas vezes, são de contexto, autonomia, competência ou desenho da cia.
August 19, 2026 at 1:51 AM
Processo dá uma sensação poderosa de controle.
Quando a org cresce, essa sensação pode virar uma armadilha: mais etapas, mais aprovações, mais rituais e mais governança começam a parecer uma resposta para problemas que, muitas vezes, são de contexto, autonomia, competência ou desenho da cia.
Quando a org cresce, essa sensação pode virar uma armadilha: mais etapas, mais aprovações, mais rituais e mais governança começam a parecer uma resposta para problemas que, muitas vezes, são de contexto, autonomia, competência ou desenho da cia.
Times raramente pulam design porque não se importam. Pulam porque design parece custoso hoje, enquanto fazem debugging, retrabalho e dor operacional chegam aos poucos durante os próximos dezoito meses.
Essa troca quase sempre sai cara 😅 .
Essa troca quase sempre sai cara 😅 .
Cortar design aumenta o custo total
Por que seu MVP continua levando dezoito meses
alexrios.me
August 17, 2026 at 12:16 PM
Times raramente pulam design porque não se importam. Pulam porque design parece custoso hoje, enquanto fazem debugging, retrabalho e dor operacional chegam aos poucos durante os próximos dezoito meses.
Essa troca quase sempre sai cara 😅 .
Essa troca quase sempre sai cara 😅 .
Teams rarely skip design because they do not care. They skip it because design looks expensive today, while debugging, rework, and operational pain arrive quietly over the next eighteen months.
That trade is usually a bad one.
That trade is usually a bad one.
Underbudgeting design increases total cost
Why your MVP keeps taking eighteen months
alexrios.me
August 17, 2026 at 12:16 PM
Teams rarely skip design because they do not care. They skip it because design looks expensive today, while debugging, rework, and operational pain arrive quietly over the next eighteen months.
That trade is usually a bad one.
That trade is usually a bad one.
A gente aprendeu a confundir confiança com competência.
A WeWork chegou a valer US$ 47 bilhões porque Adam Neumann não vendia escritórios. Vendia certeza
A WeWork chegou a valer US$ 47 bilhões porque Adam Neumann não vendia escritórios. Vendia certeza
August 11, 2026 at 11:19 AM
A gente aprendeu a confundir confiança com competência.
A WeWork chegou a valer US$ 47 bilhões porque Adam Neumann não vendia escritórios. Vendia certeza
A WeWork chegou a valer US$ 47 bilhões porque Adam Neumann não vendia escritórios. Vendia certeza
"Should this be a constant or a config value?"
"Should we use DI here or construct it inline?"
Same question, dressed up: when does this identifier get its final value?
"Should we use DI here or construct it inline?"
Same question, dressed up: when does this identifier get its final value?
What does it take to change this?
Five binding times, named by what it costs to change them
alexrios.me
August 11, 2026 at 11:02 AM
"Should this be a constant or a config value?"
"Should we use DI here or construct it inline?"
Same question, dressed up: when does this identifier get its final value?
"Should we use DI here or construct it inline?"
Same question, dressed up: when does this identifier get its final value?
We often call something a “heuristic” when, in practice, it’s just a way to avoid understanding the problem.
When a solution starts accumulating exceptions, weights, thresholds, and special rules, maybe the problem isn’t the algorithm.
Maybe it’s the structure we chose to represent the problem.
When a solution starts accumulating exceptions, weights, thresholds, and special rules, maybe the problem isn’t the algorithm.
Maybe it’s the structure we chose to represent the problem.
Clean code loses to the shape of the problem
The argument that quietly invalidates half of clean code advice
alexrios.me
August 7, 2026 at 11:34 AM
We often call something a “heuristic” when, in practice, it’s just a way to avoid understanding the problem.
When a solution starts accumulating exceptions, weights, thresholds, and special rules, maybe the problem isn’t the algorithm.
Maybe it’s the structure we chose to represent the problem.
When a solution starts accumulating exceptions, weights, thresholds, and special rules, maybe the problem isn’t the algorithm.
Maybe it’s the structure we chose to represent the problem.
Five AI agents don't give you five brains. They give one brain five sources of interruption.
The numbers make the current multi-agent coding playbook look different.
I wrote about the hidden cognitive cost of orchestrating agents, and the simple change that makes the model work much better.
The numbers make the current multi-agent coding playbook look different.
I wrote about the hidden cognitive cost of orchestrating agents, and the simple change that makes the model work much better.
August 7, 2026 at 10:22 AM
Five AI agents don't give you five brains. They give one brain five sources of interruption.
The numbers make the current multi-agent coding playbook look different.
I wrote about the hidden cognitive cost of orchestrating agents, and the simple change that makes the model work much better.
The numbers make the current multi-agent coding playbook look different.
I wrote about the hidden cognitive cost of orchestrating agents, and the simple change that makes the model work much better.
Reposted by Alex Rios
Announcing Canario, a new terminal for macOS.
It uses Rio under the hood 🐤
Spaces with their own colors (⌘1–9), splits, a ⌘K command bar, live tab previews, session restore, and a floating quick terminal on ⌥⌘T.
macOS only for now, Linux and Windows are coming.
rapha.land/canario
It uses Rio under the hood 🐤
Spaces with their own colors (⌘1–9), splits, a ⌘K command bar, live tab previews, session restore, and a floating quick terminal on ⌥⌘T.
macOS only for now, Linux and Windows are coming.
rapha.land/canario
August 6, 2026 at 6:02 AM
Announcing Canario, a new terminal for macOS.
It uses Rio under the hood 🐤
Spaces with their own colors (⌘1–9), splits, a ⌘K command bar, live tab previews, session restore, and a floating quick terminal on ⌥⌘T.
macOS only for now, Linux and Windows are coming.
rapha.land/canario
It uses Rio under the hood 🐤
Spaces with their own colors (⌘1–9), splits, a ⌘K command bar, live tab previews, session restore, and a floating quick terminal on ⌥⌘T.
macOS only for now, Linux and Windows are coming.
rapha.land/canario
Saying review is the bottleneck isn't news.
In my new post, I explore why your seniority works through "chunking," why AI diffs blow your cognitive budget, and how to survive reviewing code written at industrial volume.
In my new post, I explore why your seniority works through "chunking," why AI diffs blow your cognitive budget, and how to survive reviewing code written at industrial volume.
July 23, 2026 at 2:54 AM
Saying review is the bottleneck isn't news.
In my new post, I explore why your seniority works through "chunking," why AI diffs blow your cognitive budget, and how to survive reviewing code written at industrial volume.
In my new post, I explore why your seniority works through "chunking," why AI diffs blow your cognitive budget, and how to survive reviewing code written at industrial volume.
Hey! Almost forgot to share the slides from GopherCon Europe 2026
Here goes nothing: docs.google.com/presentation...
#gopherconEU
Here goes nothing: docs.google.com/presentation...
#gopherconEU
Alex Rios - Green Tea GC - Gophercon EU 26
Green Tea The Insight Behind Go's New Garbage Collector Berlin, Jun 15 2026 Alex Rios Memed alexrios.me
docs.google.com
July 15, 2026 at 1:32 AM
Hey! Almost forgot to share the slides from GopherCon Europe 2026
Here goes nothing: docs.google.com/presentation...
#gopherconEU
Here goes nothing: docs.google.com/presentation...
#gopherconEU