The elephant in the room here is this is talking about projects made by a single person. Part of the infrastructure mentioned is only in part about delivering r

The elephant in the room here is this is talking about projects made by a single person. Part of the infrastructure mentioned is only in part about delivering reliable service, it's also about enabling deployments and concurrent work. If you go from one to two people, you're going to be thankful you set up a continuous delivery pipeline and the usual things needed to ship code consistently like a working CI build and test suite. Even with one person, making it easy and reliable to deploy changes without some crazy manual steps is a good idea. (I agree with the whole "don't run k8 et al" for your side project, though obv.)