Persistent datastructures with Go
I present a couple of patterns that help modelling persistent datastructures in Go. I also apply them to three examples.
I present a couple of patterns that help modelling persistent datastructures in Go. I also apply them to three examples.
I philosophize about error handling, what it actually means and how to characterize Go’s approach to it.
I come up with a couple of useless, but entertaining ways to generate entropy without relying on any packages.
I explain the mathematical background of a joke-explanation of monads. Contains lots of math and a hasty introduction to category theory
I make a case for veganism and why you probably already agree with all the reasons you should be vegan. And how I wish people would reframe the topic, to make it less contentious, emotional and, frankly, annoying.
I take a toung-in-cheek look at how I imagine the life of a meat eater to look. At least based on my own experience.
When talking about static type systems, we often tend to focus on one side of the equation. I’m trying to make explicit how I view the question as a tradeoff and why I neither agree with “more is always better”, nor with “a little is enough”.
Some marbles, apparently, have a gender. And they seem to be overwhelmingly male.
In light of recent discussions about its removal, I try to discuss what kinds of problems context.Value tries to solve. I then try to describe a design which would address most (but not all) of the criticism surrounding it.
Logging in Go is a notoriously lacking topic in the standard library. There are 3rd-party libraries trying to work around this. I’m trying to explain, why I find them still lacking