A long time ago I wrote a little web app that takes a search string and finds all the words in the dictionary that have overlap with its spelling. Sort of a portmanteau generator. It was just a fun project at the time, but I have used it on countless occasions to brainstorm unique names for projects, websites, etc.

You can try it from the link below. Just type any word or name and it will populate the results.

https://dev.djdupriest.org/name-combinator/index.html

Archery app. Basically zero users, and got purged from the play store earlier this year because I refused to jump through their hoops.

It was was meant for use with scopes, you would put in some distance and scope settings pairs into it, and it would fit a line allowing you to estimate intermediate scope settings.

It also had an AR mode, where you could save a targets GPS position, and get the distance and angle to the target, and the pin setting.

Sadly, never got any users. So its just for me now. And I deleted the AR stuff.

I made an FPS on NES.

It doesn’t use any mappers or added chips. There’s quicksaves, a level editor. jump-in two-player co-op, and SNES mouse support.

I have not been arsed to add music.

I wrote my own email service: https://port87.com/

I’ve made a lot of things for it, and most of them are open source:

• https://sveltematerialui.com/
• https://hub.docker.com/r/sciactive/nephele
• https://nymph.io/
• https://github.com/sciactive/tokenizer

Also, I made one of those neat sorting algorithm visualizers:

https://sciactive.github.io/libsortjs/demo/

I’m still proud of my rendering of the logistic map. It was mostly just to learn more Rust, but it rendered this beatuiful picture with relatively little code. And mostly by accident, I didn’t know I would get those cool shadows!

In high school, we used to play a game colloquially called Spoons/Assassins/Spoon Assassin/Marker tag. Long story short, everyone playing gets assigned another player as a target. You tag your target on the back of the neck with a spoon or marker to “kill” them + take over their assignment. Rinse and repeat until only the winner is standing.

Major catch here is that for the game to work properly, the targets have to be chained in a loop, so there usually has to be a trusted individual running the game who can validate the assignment list.

So I scraped the online school directory to pull names, emails, and school photos of everyone. Then I built a Java Swing app to track a list of who was playing, and the app would shuffle a random list and email everyone their assignments blindly, photos included. Flash forward a few months, and eventually we had a full roster of ~80 people playing across grades, which was ~10% of the student body.

Unfortunately, a group of freshmen started their own take on the game, which devolved into mauling one another with Crayola markers and Sharpies. The principal catches word that I’ve been running a ring, and brings me into his office to tell me to shut it down.

Uncharacteristically for my teenage years, I went all-in on diplomacy. I plead my case, tell him I’m not involved with the freshmen, hear out his concerns, volunteer to modify the game rules, and point out that our group been playing for months without issues. No dice; the dude was a jackass with a chip on his shoulder. So we come to an impasse, staring at one another in silence.

Eventually, to break the silence, he asks about a stray bandage I have sticking out the top of my shirt. I’d had a small melanoma removed from my collarbone that week, which was caught as early as possible and removed without issue. Seizing the opportunity, I tell the principal “I have cancer”, and immediately walk out before he could formulate a response. Poor dude went white as a sheet. Good times.

Bit of a lame ending for the app, but building it taught me the skills I used to jump-start my career, and drove home the point that software isn’t an end unto itself — it’s the way people use it to come together that makes things great.

Okay, so you know the trope in spy movies where the launch codes or the diamonds or whatever are at the end of a hallway full of lasers, and the protagonist has to do some cool flip moves (if male) or some slinky contortions (if female) to get around the lasers?

I made that as an arcade game with an Arduino. Some red laser pointer diodes, some photosensors, a few lights, bells and whistles, a fog machine, a few big ol buttons, and you’ve got spy laser hallway. It had a separate “break as many lasers as you can” mode as well, played like a combination of DDR and whack-a-mole.

The second coolest thing I ever programmed was probably the GPS MP3 player. A farmer wanted to add an automatic soundtrack to his Halloween hayride, like when the drove through the spooky graveyard it played ghost noises, it would play music for longer stretches on the road. I used a Raspberry Pi with a GPS HAT and wrote up a script in Python that would compare the actual position with a set of coordinates stored in a text file, and if one matched, it would play an associated mp3 file. The effect was kind of lost because the audio was coming from the vehicle itself, but it’s a hay ride, it’s supposed to be kind of lame. The bedsheet ghosts said woo as you drove past, I’m in the special effects industry, dad.

Stop me if you’ve heard this one before, Hello World.

Back in late 1982 (i think it was), i was 16, I’d just convinced my folks to buy me a Commodore 64. It had a tape drive for storage, long before broard Internet access etc. I had magazines about programming in Assembler and programmed a couple games to play becase i didnt have access to, well, anything.

I still remember my bottom porky pig balloon shooter :)

SYS 64738 my dudes.

My next computer was an Amiga 1000, floppy and pirating in my local user group were a thing by then :)

When Google Reader was alive, I wanted to improve its UI, so I wrote a userscript which completely replaced everything in the browser but still spoke to the Reader’s backend for data. When Reader was turned off, I only had to provide my own backend.

In the 2010s I had a Windows Phone which I thought was amazing. I bought the original Surface Pro too, because at the time I thought it was incredible. A full operating system in a tablet form factor that was incredibly fast and touch screen.

In the IT office I worked in, we had a dartboard. It was great for just stepping away from your desk if a problem had stumped you, throwing a few darts to take a break, and inevitably the answer would come to you. It was our rubber duck.

Trouble was, all of us were terrible at the basic maths involved with darts matches. So I thought, what if we mounted the Surface to the wall, and could just tap where the dart had hit, and get scores instantly.

So I wrote this darts score-keeping app that worked on everything from Windows Phones to tablets, and even an Xbox at one point, thanks to the way Microsoft had implemented their cross-device app deployment.

We used it every day in the office. I think in 10 years it’s sold about 3 copies.

Lovely Darts

Back in the day, I got the weird idea that it’d be handy to grab information from the XMMS music player as it was running. So I made an extension that basically dumped the information about the player state as text to a named pipe. A few people wrote scripts for their IRC clients and whatnot to tell others what they were listening.

(Back then, none of the GUI music players really had any kind of RPC capability. Nowadays, you can probably do this stuff easily with D-Bus or whatever.)

One time, late at night, I was just listening to music in bed with headphones, controlling XMMS via infrared remote controller (LIRC). A random cool track came up. I had no idea what it was actually called. I went “wouldn’t it be cool if I could hit a remote button and it’d say what song is currently playing?” …so I got up, got back to the computer, and wrote a script that reads the pipe, takes the artist and song title, and feeds it to Festival TTS, then added that to LIRC configuration.

My first project in Rust was replicating this paper because i wanted to learn rust but needed a project to work on because i hate learning from tutorials.

Of course, I had intended to go the OOP route because that’s what I was used to and this was my first time using rust… that was a bit of a headache. But I did eventually get it working and could watch the weights change in real time. (It was super slow of course but still cool)

Anyway I’ve started making a much much faster version by using a queue to hold neurons and synapses that need updating instead of running through all of them every loop.

It’s like lightning fast compared to the old version; I’m very proud of that. However, my code is an absolute mess and is now filled with

Vec<Arc<Mutex<>>>

And I can’t implement the inhibition in a lazy way like I did the first time, so that’s not fun…

The code I wrote that I use most often is music playback in the Jellyfin Roku client.

I use it almost every day and think it’s pretty cool 🤘

I wrote a program that scanned object files (compiled from a large C++ project) to see how they were interdependent. It was pretty useful for detecting cycles in the shared libraries that we were compiling from them, but the biggest benefit was it enabled me to very easily rewrite the build system from scratch.

It was surprisingly simple - most ELF parsers can read a file and dump the symbol tables in them. (In this context, a symbol means a defined function, so if a C/C++ source file has int main() in it, the corresponding .o file will have a main symbol in it.) They also include information about which symbols are defined in the .o file, as well as which symbols it depends on which are undefined. This allows you to figure out a dependency graph, which you can easily visualize using graphviz or use to autogenerate build files for CMake or any other build system you may wish to use.

In my case, I wrote this kind of program twice in two separate jobs. Both of them had a very janky build system using custom Makefiles. I used this program to rewrite the build systems in CMake. The graphviz dependency graphs are also just generally helpful to have as project documentation. CMake can do this natively, by the way - here’s the documentation for it: https://cmake.org/cmake/help/latest/manual/cmake.1.html#cmdoption-cmake-graphviz