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

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.

An unexpected behavior of python that surprised me today.

Updating my TLS-certificates due to Heartbleed.

A small pattern to add stacktraces to errors.

I sign my blog posts.

I hate software-engineering as it is teached in Heidelberg. Really.

ext4 has a feature called dir_index enabled by default, which is quite susceptible to hash-collisions

Put a terminal with a vim-instance in an i3-scratchpad, combine it with autosave-when-idle and you got the perfect note keeping workflow."

I wrote a simple Tic Tac Toe AI as an exercise. You can get it on github.

Using gdb to manipulate a running process is fun and just the right amount of danger to be exiting

We had a codegolf challenge recently. My C-solution was 246 byte, the perl-winner was 191. I decided to give notes for C-golf beginners.

I put up a small script to automate creating blog-posts in jekyll

I gave a very introductory programming course and saw once again how the basic ideas underlying the modernization of teaching just work when implemented right.

The (n+1)th launch of my blog