Oatmeal and toppings

Sometimes you only think you don’t like a dish because you simply don’t like the way it’s been prepared for you in the past. This has happened to me with a LOT of foods. Most recently I realized had written off oatmeal simply because my tastes didn’t match that of the others around me. From childhood to adulthood I’d only been given instant oatmeal if I’d asked to taste oatmeal. It has a place in people’s lives, but like most instant foods, the instant version is a pale imitation of the real thing. Then, when I got married my wife ate steel cut oats. I tried them, but again didn’t like them. It wasn’t until Red Hat Summit this year when I ended up trying them again because I wasn’t really feeling the other breakfast options. And it turned out that I could indeed enjoy oatmeal. It’s just that I liked it more al dente than my wife. Armed with the knowledge that oatmeal didn’t have to be mushy, I set about figuring out the right water to oats ratios to get it to the consistency I preferred. Now, at least once a week I have oatmeal with some fruit and, if we have some in the house, nuts. In the photo above I have some brown suger, but I’ve stopped adding that. With the sugars in the fruit, it’s not necessary. I do add a little vanilla extract and, if the flavors make sense, some cinnamon or cardamom.

Scarlett’s scientific journal entry about a duck and a baby duck

Sometimes the things my kids focus on just crack me up.

Baby birds in BBQ prep station - the mom thought it was the best place to make a nest

I thought I’d blogged before about the bird who made a nest in my BBQ prep station, but a couple quick searches didn’t find it. So the background is that this bird decided the best place to nest is at my BBQ prep station which has a couple shelves that basically look like a bird house (a small, circular hole). I tried to frustrate the bird out of doing it by dumping out the nest daily. At some point I let the bird win. A few months later, these baby birds were born.

I recently started an electronics hacking project to build a thermostat for my Weber Smokey Mountain. You can find details at Hackaday.io, but if you’ve been here long enough you know that I don’t trust other sites to continue to exist. (It’s why I copy my book reviews over from Good Reads). As of right now I’ve got the board able to read temperatures from a thermocouple that I send, via WiFi, to an MQTT broker. Then, via Python I take subscribe to that MQTT topic and put it into InfluxDB. From there I use Grafana to graph it. Here’s an early beta where I was trying to make sure it was working from end-to-end:

When MakeMKV added a new requirement for ccextractor, allowing it to grab subtitles that are encoded on the DVD or Blueray as Closed Captioning instead of subtitles, there wasn’t a package available for Fedora. (There is now, but at the time where wasn’t) So I wanted to make an RPM that I could host on Fedora’s COPR for others who needed the package. There was a problem with their shell script for building RPMs. At the time I just kept hacking away at it until I was able to build RPMs. But I didn’t think about how the manual process wouldn’t be sustainable as changes were made to CC Extractor. They weren’t having releases too often, so I didn’t worry about it. But then they made a new release and I knew that this time, having leveled up on my git-fu, I would try and figure out how to fix that problem and submit a pull request.

Based on the file modification dates, I went from using the Digikam SQLite database to using their embedded MySQL database in May 2018. I did it because at the time everyone was saying that for a large database it’s better to use SQL than SQLite. For a long time it seemed to work well enough like that. But, for the last few months, MySQL hasn’t quite been right. It’s been complaining about issues with InnoDB. Unfortunately, in my Googling I couldn’t figure out how to attempt to fix that issue with an embedded database. All the solutions seemed to involve using a “real” MySQL. So, sick of all that, I decded to go back to SQLite. Since launching Digikam (for the past two days) just causes my computer to go to a load average in the 50s and lead to an unending stream of SQL errors, I had to move the folder that contained MySQL and start from scratch. It was also an opportunity to do what they recommend and have the database reside on an SSD.

A couple days ago, I wrote about giving KDevelop another look and posted it to reddit’s r/kde. In my post, I’d said it was annoying to have to configure the color schemas per file. Someone commented on the subreddit that if you use the View->Schema menus it’s per file while if you go into Settings->KDevelop settings you can change it for all files.

As a side effect I explored the same options in Kate and set it up like this:

When I first started programming it was just at the prompt of my Tandy computer. Then it was in the QBasic text editor on the IBM computers at school. But when I started programming again with “real” languages, I ended up going with Emacs. Although I was first annoyed at the way commands like save were prefixed, it became my favorite editor. I think that was partially because of diving headfirst into the free software movement and partially because I didn’t like vi’s different modes and how annoying that made things if you didn’t realize you weren’t in the text entry mode. Eventually, I moved on to Kate because I love KDE (been running it as my main desktop for over 10 years now) and I loved the features it enabled. Also, since vi (or vim) is found EVERYWHERE while Emacs usually requires installation, I ended up switching to vi whenever I’m ssh’d into a computer. If you add plugins like powerline, it can be pretty awesome to use. Even on my desktop if I’m editing /etc/fstab I’m more likely to pull up vi than the weight of KDE (not that it takes up THAT much RAM).

After a bit more work since my 21 July post, I’ve finally reached what I can consider to be beta status for the GUI. Things have matured to the point where it works well on both Linux and Windows and I’m now using it every time I game. I created a bunch of issues on Github to track new features I want to add in order to get to what I think will be a 1.0 release. I’m excited at the progress I’ve made and that the software continues to have interest. As always, the code is available on Github. Here are videos on how to use the GUI:

Blender “version control” before I knew about VCS

Boy am I glad I know about svn and git now. It was such a mess before to keep track versions of files to be able to go back in the case of an error.