It's a good article and basically correct, I don't agree with the conclusion "why not pay someone else to do it", it may scratch your itch in the short term, bu

It's a good article and basically correct, I don't agree with the conclusion "why not pay someone else to do it", it may scratch your itch in the short term, but in the long term you have no agency if you stuck all your fingers into the finger-trap of github actions, metadata and other EEE. It's literally microsoft at the wheel as well. Similarly free CI services are very attractive but when they stop being free, or die, and you have a lot of investment in tests specific to their infrastructure spread over all your apps and again no agency to keep it going yourself, it's less attractive. "Why not pay someone else to do it" glosses the privacy and security results are not the same when you pass all your email or IP to a large foreign company who may compete in some of your markets, compared to doing it in-house. Yes it can be unexpectedly difficult to do even a small thing securely and well. But it doesn't mean that it's not the right approach.