The trouble with optional interfaces
I take a look at the pattern of optional interfaces in Go: what they are used for, why they are bad and what we can do about it.
I take a look at the pattern of optional interfaces in Go: what they are used for, why they are bad and what we can do about it.
Using math, I made it a lot easier to find the last undiscovered parts of my Zelda - Breath Of The Wild map.
Trying to provide some advice on how to do easy, readable, scalable routing in go, without relying on any muxers/routers (or writing your own).
I’ve been diagnosed with ADHD. I ramble incoherently for a while and I might do some less rambling posts about it in the future.
There are next to no “backwards compatible API changes” in go. You should explicitely name your compatibility-guarantees.
I did lazy evaluation in go.
It is surprisingly hard to make SQL-based authentication immune to timing side-channels, if you want to prevent enumeration of users.
A short list of four things that I might want to add to go (but probably wouldn’t).
A mildly interesting algorithmic problem and my solution to it.
We made a gamejam-game.