where I can’t use cron and systemd is available, then of course I will use it

I argue for a 5% cost-of-living adjustment for bad software, and I make sure it's a separate line item so they know it goes away when systemd goes.

Yeah, I think it's just the way the blog post was written. When I was reading it I saw the first few paragraphs was basically "here's how to do Cron with it", and then everything after that was "here's a bunch of other features it has that cron doesn't and how to use those"

I don't think that's the wrong way to write this kind of article, but I could see it feeling overwhelming on a skim, because it may feel like you need to read the whole thing in order to get anything working. But actually only the start was necessary, and the rest was tasty feature pitch.