What programming/technical projects have you been working on?

I've worked on a web UI to manage bare git repositories on a server.

Basically, I wanted to be able to create/mirror repositories, edit their category / description / main reference pointer, and to rename and delete them.

Since using something like gitea is simply completely overkill for hosting my repositories, I instead kept my gitweb/git-http-daemon setup and moved towards building another tool that would sit on top of my git repository storage.

Single 2.5MB~ golang binary, deployed behind an authentication-enabled reverse proxy.

I got iMessage working on my Android phone last night by setting up a BlueBubbles server on an old 2011 Mac Mini I got from work. So far, so good! It will be useful for sending media to and from other artists and my family, all of whom are on iPhones. It was a fun project and I'm glad I was able to keep some old hardware out of the landfill for a bit longer.

Made a "binding" of the Vosk speech to text thingy for Tasker. It's my first Android thing in a long time now and honestly I did not like the experience as much as I expected. Android is complex!

Well, either that or me not starting with something more basic caused it. IDK, but it somehow works, which is nice I guess.

Any experienced Android devs here, please try to not cringe at my code too much, OK? But still take a look if you have some free time, I want to know how I might be able to improve it.

• https://github.com/Admicos/VOSK4Tasker
• https://old.reddit.com/r/tasker/comments/n1643w/dev_vosk4tasker_free_and_open_source_completely/

Toying with naming data analysis again, after this discussion. (Boy and Girl defined by SSA)

So it is quite interesting to see how much longer of a tail girl names have relative to boy names. Keep in mind that births are roughly 50/50 split.

I've been working on a code challenge (UI for an API) for a senior front end dev position I applied for. They asked for something using React if possible, which I've not built anything with before, so it's been quite the journey to figure out the build system hurdles. I think I've got them mostly figured out, but boy is it frustrating to have to understand almost the entire build system and the intricacies of Node vs ES6 vs CommonJS before you can even write a test. And it doesn't help that half of the solutions are just "install this random package that will automagically fix it".