> All of these steps can be efficiently automated.

Good luck with that. Yes, a compiler will do a good job with i * 28, but the optimization in the article - which is a pretty simple case, chosen to fit in a blog post - requires manipulating the algorithm beyond the capability of any compiler I'm aware of.

We do have good tooling to show what code is slow, for instance, so it's not like automation doesn't help here.