alexrios

sync.Mutex has spun before parking since Go 1.5.

Go has a second mutex, used by the scheduler itself.

Go spins in both of its mutexes and exposes neither spin loop.

A handmade spinlock in Go looks like eight lines of code.

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

A Go 1.27 upgrade exposed a JSON contract, an HTTP error-design flaw, and a benchmark that looked fast because it failed early

O encapsulamento que só existe na aparência

The encapsulation that isn't

De parâmetros booleanos ambíguos a campos contraditórios: explicite as operações e modele apenas os estados que o domínio permite.

From ambiguous boolean parameters to contradictory struct fields: make operations explicit and model only the states the domain allows.

Cada parâmetro é um contrato.

Every parameter is a contract.

Por que seu MVP continua levando dezoito meses

Why your MVP keeps taking eighteen months

Por que o Zig deletou GenericWriter e AnyWriter, e o que o envenenamento genérico custa de verdade.

Why Zig deleted GenericWriter and AnyWriter, and what generic poisoning really costs.

Padrões práticos pra atualizar código Zig de std.io pra std.Io, com exemplos de antes e depois.

Practical patterns for updating Zig code from std.io to std.Io, with before/after examples.

O nome informal da refatoração massiva da interface de I/O do Zig que removeu GenericWriter/Reader em favor de tipos concretos com vtable.

Por dentro do design de vtable em três níveis do Zig, e como a posição do buffer viabiliza performance e async ao mesmo tempo.

Inside Zig's three-level vtable design, and how buffer placement enables both performance and async.

The informal name for Zig's massive I/O interface refactoring that removed GenericWriter/Reader in favor of vtable-based concrete types.

Cinco momentos de binding, nomeados pelo que custa pra mudar cada um

Five binding times, named by what it costs to change them

O argumento que invalida silenciosamente metade do conselho de clean code

The argument that quietly invalidates half of clean code advice

Quando dividir as unidades de deploy mantendo o storage compartilhado funciona, e quando não

When splitting deploy units while sharing storage works, and when it doesn't

Dois eixos, não uma lista

Two axes, not one list

O que o código gerado por IA continua errando sobre coesão

What AI-shipped code keeps getting wrong about cohesion

Como refactor DRY bem intencionado produz os piores módulos que eu já vi

How well intentioned DRY refactors produce the worst modules I've seen

How Go 1.26 repurposes an AES cryptography instruction to make garbage collection up to 20% faster

How a one-line nesting mistake in internal/cpu silently disabled GFNI detection on every consumer-grade Intel CPU shipped since 2021 (Alder Lake, Raptor Lake, the Atom-derived N-series, and more).

What it takes to move a zero-allocation UUID library from Zig 0.15 to 0.16, where every side effect now flows through std.Io.

How comptime generics replaced function pointers for deterministic UUID testing: zero runtime cost, full test coverage

Three bugs found in a UUID library within hours of writing it: negative timestamp corruption, broken monotonicity, and unreachable code that was reachable

Thirteen years after Making Sense of NoSQL, most of its claims are debunked.

A design journal for a zero-allocation RFC 9562 UUID library in Zig: constraints, decisions, and what I learned shipping it

A design journal for slogbox, a zero-dependency slog.Handler that keeps recent logs in a ring buffer

How to test Go's new garbage collector on your workload, and why the results might surprise you

Data structures, algorithms, and the clever design decisions behind Go's span-based garbage collector

Why Go's new garbage collector works with pages instead of objects—and what that means for your applications

How academic research became a Go runtime feature, and how to start using the leak detector today

Real-world goroutine leak patterns and how they are caught

This is called AI assistant for a reason

Why you should always have a recovery plan before clicking "Update"

Understanding goroutine leaks through a parent lens