Some thoughts on effective altruism, utilitarianism and optimization.

I recently found out about a nifty security attack called SSL strip.

A quick deep dive into Feistel networks, to see if I can motivate them to myself and make them feel less arbitrary.

I recently discovered that I had only scratched the surface when it came to git tooling within vim. Here's my attempt at crafting a more polished experience.

Most modern browsers implement WebGL, a javascript API modeled after the OpenGL API that allows your javascript code to directly access your GPU for rendering graphics to a canvas element. Let's have a first look at how to use WebGL to create graphics in the browser.

An exploration into creating graphics with Quil, and getting better at Clojure along the way.

Modern browsers ship a web API called IntersectionObserver that largely obviates the need for inefficient scroll event listeners. Let's use it to create an infinitely scrolling page using React hooks.

ES6 finally brought iterators and generators to javascript. Recently, I found out how you can nest generators to implement lazy recursion.

I started a fresh .vimrc from scratch, and decided it was a good idea to document the process for my future self, and anyone else who might benefit from it.

Pick someone off of the steet and ask them if they know a piece by Rachmaninoff, chances are they'll name one of his piano concertos. It's gained immortal status by its ubiquity in the Queen Elisabeth competition, and countless others. While they much deserve their celebrity status, I thought I'd take some time to discuss one of my own favorites. That said, I suppose anyone more aquainted with Rachmaninoff would say it's hardly less famous than his piano concertos.

The first thing one notices when looking at the Eleventy documentation is that *there isn't really much there*. It's about as bare bones as it gets: no complicated data models, no strict directory hierarchies. Eleventy takes all files from one folder, compiles them, and generates a folder of output files. Learning how to use it was, in a word, a breeze.

There is a bit of a trope, a tradition, that the first thing that is discussed on a newly founded blog should be how said blog was set up and configured. I wouldn't dare break away from this tradition, and will in due time write down the nitty gritty that went into setting up this blog, the things I've learned and the gripes I had with the tools used. In this particular post, though, I'd like to start by talking about some of the reasons for choosing the particular technologies that I did.