A decade ago I reverse engineered the Macventure game engine, allowing you to play Shadowgate and Deja Vu etc on modern oses. The current copyright holder then paid me to iron out the rough edges and create the official ports currently on steam.

My favorite was this project because it really shouldn’t be possible, it requires some unusual problem solving (kinda like code golf), but the best part is seeing people’s horrified expression when they realize

1. The monstrosity works
2. There’s no real alternative

(I’m working on a video that explains it, but until then the readme and stack overflow post will have to do.)

I wrote a a masturbation tracker app to measure how frequently I fapped to my waifu

Usually the one(s) I’m working on right at the moment.

But if I were to look back and decide which ones I still remember enjoying, a few come to mind.

For my day job, I’ve written two different (more or less) ORMs in my career. (For two different companies and in two different languages.) Pretty interesting stuff, that. The kind of project that you can sink your teeth into.

Neither one was a “I think I’ll write an ORM” kind of situation. They were more like “oh, given these requirements, I think probably I’ll need something that will work like X, Y, Z… oh, that’s an ORM. Ok then, let’s do this.”

Side-projects-wise, most of the side projects I’d talk about are here. (Yes, AntiMS is me even though different username.) “hydrogen_proxy” got way less fun when I got stuck for like a year on how to make HTTPS work. But aside from that it was a lot of fun to work on. “codecomic” is quite interesting to work on as well.

And the project I’ve been working on most recently is a very configurable framework written in a combination of Go and OpenSCAD for creating bespoke, 3d-printable mechanical keyboards including keycaps.

Here’s a preview of kindof roughly where I am with that mechanical keyboard project at the moment:

I wrote a DNS server that did global software load balancing. Essentially it just has a health checking component and a sort and uses that to determine the closest healthy endpoint to return.

Mostly used for cluster failover or in cloud terms it can keep traffic within a zone if possible, otherwise within a region, otherwise closest region.

The reason it was my favorite project is because I was unqualified, but nobody else on my team was a DNS expert. So I got to drink from the firehose and learn. I had a really good testing feedback pipeline where basically visitors to our website did a couple extra background requests on their first page load and we used the web performance timing API to track DNS lookup times and TCP/HTTP times. So I every time I made a change I had millions of performance reports. I could see the impact of my changes in about 60 seconds in grafana.

Between learning something totally new and tying it to a short feedback loop with beautiful graphs I had a great time. Plus that product literally allowed my company to start using the cloud and build multi cloud systems.

I built a ruobo workbench for hand tool and other general woodworking tasks. Was made with all mortise and tenon joints and no fasteners, so I got to learn and practice lots of techniques (hand saw and chisel cuts, router flattening, lamination, etc).

Work related project was a library for curves representation (polynomial, bezier, and a lot of other types) in C++. I liked working on it for several reasons. First one is that I could finally start something from scratch after years of working on legacy code. No dependency on strange old library from the team, only mainstream libraries.

But mostly it was because I learned a lot on this project. I had to mix template programming, heavy use of polymorphism, python bindings of the c++ and serialization together. I had experience in all of this stuff already, but mixing everything together bring a lot of new troubles and you have to understand how it works more in deep to be able to solve them.

I’m not making “famous” open source package with thousands of download and used everywhere, but seeing this package still in use in several other projects (and not only in my initial team) even after I left the initial team feels good. One day someone from my new company recommended to use “my” library as dependency to solve one of our problem, without knowing that I was the author, saying that it was a good well written lib. That’s a nice ego boost!

A while ago I wrote an extensible dummy data generator for Java.

I needed to fake some scientific data for a project at work and wasn’t satisfied with how closed for modification existing data generation solutions were, so I decided to tackle writing a library on my own.

It was my first major contribution to open source and had some architectural challenges which were fun to solve, not to mention the learning experience :)

i spent weeks on this project, called the apple

NES FPS.

Currently not doing much work on it, though. It needs the quicksave system to be compressed so the level editor is worth using. I got arithmetic coding kinda-sorta working (with an assumed Zipfian distribution to avoid building the tree on-hardware) but the decoder never worked right. I’ve been putting off another do-over on that. Which means the levels aren’t getting made, since obviously I’d use that format to store them in ROM. Got portals working, though.

6 years ago during university I participated in a Coding Challenge for Vehicle Routing Problems. I really like TSP and VRP related problems. I tinkered on my algorithm in the evenings to make it faster, consider more edge cases, produce better solutions etc. It was a really rewarding work because every time you change something you can run it and can see if your thinking was right and improved the result. The goal was to find the shortest time to serve all customers, so the result was basically a number indicating total time. Number goes down = win.

Unfortunately I haven’t found anything in my professional career so far that I really liked :(

My first discord bot written in discord.py. It had over 800 lines of code. I wrote it all in one main.py and hence the organization wasn’t great. I also wasn’t very good in Python at the time so I am now rewriting it with cogs and better practices.

My favorite project was around 6 years ago when my former employer was looking to modernize the customer service automation experience with AI, it started with a round the US tour of going to the HQ’s of 4 big tech companies in the space(IBM, Microsoft, Amazon, Google at the time) as part of an investigatory team. We were to select what we thought would be the best engine to run conversational AI in our applications, during that time we were also given greenfield to write a modern framework apart from our existing technology to leverage it. Over the course of a year and a half we went from ideation to the creation of an omni-channel conversational framework that netted me and the team a patent, and allowed me to flex architecture skillset that lead me to my current role as a solution architect working with some of the same people at another better company. Definitely the most fun, exciting and rewarding project of mine to date.

Wrote a basic primality checker library, it’s not by far my most interesting or complex project but I like that I accomplished all my initial goals in a timely fashion.

Automatic differentiation in C++17, had to do it from scratch as they weren’t open to 3rd-party libraries and it had to integrate with many symbolic calculations that are also done in the library (so even if you used a 3rd-party library you’d still have to rewrite parts of it to deal with the symbolic stuff). Succeeded in doing it and basically the performance was on par with what people in the industry would expect (all derivatives at once in around 3 times the evaluation time, sometimes much less if the calculation code has no dynamic parts and is differentiated entirely at compile-time).

It was pretty cool because it was a fun opportunity to really abuse template meta-programming and especially expression templates (you’re basically sort of building expression trees at compile-time), compile-time lazy evaluation, static polymorphism and lots of SFINAE dark magic and play around with custom memory allocators.

Then you get scolded by the CI guys because your template nightmare makes the build times 3x slower, so the project then also becomes an occasion to try out a bunch of tricks to speed up compilation.