Highlights

• I failed to sell recurring TinyPilot license subscriptions.
• I realized I made TinyPilot way too configurable.
• I thought I’d been investing poorly into TinyPilot’s development, but writing this retrospective made me realize I’m mostly on track.

Goal grades

At the start of each month, I declare what I’d like to accomplish. Here’s how I did against those goals:

I’m still a Nix beginner, and one thing I couldn’t figure out until recently was how to keep parts of my configuration.nix file under source control.

My goal

I’d like for my Nix configuration files to be modular and reusable, so depending on the system or flake, I can pull in only the configuration files I need. I’d like all my Nix configuration files to be under source control so that different systems can depend on different versions of any file so I don’t have to upgrade every system to the latest version of each configuration file at the same time.

In 2005, Joel Spolsky’s software company, Fog Creek, filmed a documentary about their summer internship program. The film is called Aardvark’d: 12 Weeks with Geeks, and it follows four college interns as they design, implement, and launch a completely new software product.

That’s not the interesting part.

Looking back on this documentary 18 years later, it’s striking how many interviews it captured with people who would go on to greater fame and success:

Highlights

• I think through what it would take to add recurring subscriptions for TinyPilot Pro.
• I’ve done some more exploration into Nix for managing development environments.

Goal grades

At the start of each month, I declare what I’d like to accomplish. Here’s how I did against those goals:

In creating the tutorial, “Installing NixOS on Raspberry Pi 4,” I ran into a ton of paths that didn’t work.

I’ve collected them here for the sake of saving others time retrying the same steps.

The standard NixOS aarch64 image doesn’t work

When I checked the NixOS download page, I saw that they offered 64-bit ARM images.