I’m working on finding a job after being laid off at the start of September.

… and fixing this stupid subtitle bug in the Jellyfin for Roku app 🤘

I never get much focus on code these days because there’s always something else to fix in the real world. The list of ideas keeps growing, while I work on the garden, repair tools, maintain vehicles,…

A script which will find random pictures of anyone in the family from the Immich database, resize them and add metadata on them like where they were taken and when and put them on the TV to show as kind of a screen saver when we’re at home.

I like this Facebook feature which shows you “Today 10 years ago”, Immich, does have it in it’s UI too and perhaps I will mix in those pictures also to show on TV.

Just another game engine 🤷

Working on my game that I plan to release on Steam by the middle of October if all goes well, which has been my last 6 months or so. Still lots to do, but the code is tight without a single bug at this point so happy times there. haha

I’m working on a commandline application in spirit of tools like grep and jq. It’s to filter and edit RetroArch Playlist files in JSON format with file extension .lpl. The program is written in Rust and has many options and features that exceed the simple JSON parsing of jq in example.

All of this is a learning process for me about the Rust language, JSON and RetroArch Playlist format and how the offline Ai tools and models on such low hardware stacks up in real world. I primarily used it to ask occasionally questions, such as what option name it would recommend, or what function description would be good, sometimes asked what it is thinking of a function implementation, or how to do a certain thing in Rust. I look at the code and its reasoning to understand it and if its an improvement. This was incredible helpful to me in learning more and even finding and eliminating bugs. Especially because I was 6 weeks offline and a few weeks after that period.

I also used the Ai to write about 260 unit tests for functions. Off course I checked every single test, reworked it if necesseray. It helped me to find bugs, but also introduced nasty bugs. So using Ai is dangerous, especially beceause It solves problems you start trusting it more. This was an important lesson for me.

I’m currently almost done and write the README and soon will be uploaded on Github and crates.io.

Been hacking away for quite a while at basically a build tool/framework for Rust, which picks up where Cargo leaves things. So, it’s really just a set of libraries for now, which you can use while writing your build scripts in Rust, to help with stuff like putting together a distribution archive, caching intermediate results or handling the automatic installation of CLIs you use in your scripts.

Definitely has been an experience to build this. It feels like a magnitude more work to find generic solutions for this stuff, compared to just throwing it down for a single codebase.
But it has also been rewarding, seeing builds becoming more robust and quicker in the other projects that I’m definitely also still developing and not just using as a testbed for my build tooling. 😅

Getting an update out for my app, Shosetsu.

I’m working on a page hit counter that I use to track visits on my personal websites. To make it challenging, it runs on quarkus with hibernate reactive and deploys to a serverless environment. So far it had no usable admin UI, prompting me to stitch together a React UI lib with a look & feel inspired by TUI applications.

Think keyboard navigation, visualisation through ASCII characters etc. but some of the convenience that comes with modern webapps. The goal is to create components that mostly work out of the box to use with my personal projects.

Working on my programming language, and improving some blog posts of mine. :-)

Well I am learning that hardware-wise, my open source smart watch AFE might require an interrupt pin (apparently the RTC fallback that Maxim says is why a big crystal is required just doesn’t do anything and no docs on how to set up that or polling mode) to work with the algorithm chip. That brings the cost from 20€ for 5 PCBs to 350€.

So I might need to write a new zephyr driver for the AFE chip directly and then spend months more work making an open source PPG algorithm and adjustable LED gain algorithm to keep the project going.

Been writing a NES emulator for a while. Works well enough but there is a new automated test available. My emulator does ok, but not good enough. Going to try and improve things.

• https://gitlab.com/coreyoconnor/wes
• https://github.com/100thCoin/AccuracyCoin

I’m writing a script that finds filenames in a directory that only differ in case. Since I’m working with filesystems that are case insensitive sometimes, this is a pain to deal with and I’d rather rename the few files. But first I’ll have to find them 😉. Now, there might be some tool already that does this, but I enjoy the challenge.

Foundational steps of a tool that reads and interacts with the menus of Madden 08 for the PC. Starting with the screen reader to read on screen text. I’ve been working on it for months and so far I have no text reading and a few dozen lines of the most dogshit C# code even your nightmares couldn’t recreate.

I’m in so far over my head I can no longer even really visualize what I’m doing.

Been thinking about that game I started building a while back. Got some new ideas. Might pick it up again soon. It’s been so long though that I have to read all my notes and figure out what I was doing before I can do anything new. Dreading that part.