Software articles at a level of rigor somewhere between textbook and blog. mostly systems programming & backend but not limited to it.
An investigation into collapse of Github and how the decay of our tech infrastructure is a crime against software. Detailed comparisons of Github, Gitlab, Codeberg, and more from a distributed systems and software performance expert
ALPHA: Third part of a guide to systems programming, covering performance, including computer architecture, architectural design, profiling, benchmarking, and examples of micro-optimizations.
An attempt to communicate wisdom from the engineers and programmers of the past
Second part of a guide to systems programming, covering how to interact with the outside world - syscalls, files, etc.
Gin is a very bad software library. Way, way too much detail on why.
First part of a guide to systems programming, starting with building the basic tools to examine and manipulate files and binary data
An investigation into the mechanism and performance of Gin's fancy stack traces
Adding autocomplete to our reflection-based debug console
Third part of a guide to backend development in go, covering testing, middleware, dependencies, routing, and a little bit of databases
Now that we know how to build it by hand, use the go stdlib to do it the practical way
First part of a guide to backend development in go, covering the basics of TCP, DNS, and HTTP
A very fancy way to make a realtime debug console like quake for your go programs
The only thing your program does every time is start, so it should start as fast as possible. Here's how.
part 3 of a grab-bag of go quirks and tricks, covering arrays, validation, and build constraints.
part 2 of a grab-bag of go quirks and tricks, covering concurrency, unsafe, and reflect.
part 1 of a grab-bag of go quirks and tricks, covering declaration, control flow, and the typesystem.
Using the magic technique of 'just kind of looking at raw bytes' to solve a problem with UUIDs.