A collection of thoughts and experiments that at one point occupied my time, some still do. These are the things happening in my idle cycles.
I've been slowly making my way back into the world of C and C++ lately; consequently I'm filled with angst at what I perceive to be failings in the design of the languages. Just a rant.
I recently experimented with system monitoring but stopped short of creating any reporting on the metrics gathered. I took some time to draw up a quick interface to surface some of that information in a further exploration of managing my own server.
I have been experimenting with a somewhat radical sounding practice for developing software — one designed to reduce both complexity and bugs. It isn't agile, and it isn't TDD, the closest thing to it is copy-paste.
I've finally made a foray into Python packaging;
publishing my own static site
generator. What follows are my notes on the process and some implications on
the development of what used to
Lately I've been faced with some of the peculiarities of UI testing, in my case, using Selenium. Not only are the tests slower than other kinds of tests, they are often tied to specific enviornments. In an effort to combat this coupling of "special" environments I've been working on reliably creating new environments.
I put off cleaning up cruft on my server for too long and then put off writing anything about it while I waited to see what fell off in the wash. It turns out, things were pretty painless.
Projects like gofmt and rustfmt aim to simplify or even eliminate discussions of style during code review. Several tools purport to do the same for Python, but how well do they work, and how can you tell?
I've been trying my hand at designing a stupidly simple system for monitoring the state of a server. This has turned into an exploration of the design of existing systems, and stealing shamelessly from those designs.
Software development metrics can be difficult, knowing what to track and how to observe things without gaming them can seem like an art more than a science. I've been in discussions lately about how to track code review metrics meaningfully and how to do so in the context of my absolute least favorite code review tool.
Static sites are neat, but what if I wanted features of a dynamic website? Searching, for example, could prove interesting or useful but is typically done server-side. Here I detail a fun experiment in implementing search client-side for this very blog.