Sent rejection or “waitlist” emails to all the other applicants.
I’m only trialing one person at a time, so the clear “no” candidates, I told it wasn’t a match, but the others I said I was doing a trial and would reach out to them if it didn’t work to see if they’re still available.
The tests missed it because I used to skip all test steps related to systemd services during CI testing because I couldn’t figure out how to get systemd to work in Docker. I later figured it out but forgot to remove the skipping behavior. The test missed the bug here because it was logic related to a systemd service.
Recorded two new sections and three new deep dives
Only one section and two deep dives to go
Presented the remaining sections of the course in previews to Blogging for Devs
Cut the section on blogging software
I started to feel like it was too far into the weeds and the course had gotten too long, but I felt weird changing the content after people had already pre-ordered.
As I was writing my December retro, I realized how unlikely it is that any of my customers had their hearts set on that particular section. And if they did, I could just offer them a refund.
So, I ended up cutting that section and splitting another section into two, and I think it makes the material more cohesive.
Added my first affiliate
Kind of an experiment, hopefully they don’t do anything spammy.
