Idk. I’ve worked with tools like he mentioned. Recently I set up a media server and didn’t want to mess with Ansible to provision the VMs and containers or Kub

Idk. I’ve worked with tools like he mentioned. Recently I set up a media server and didn’t want to mess with Ansible to provision the VMs and containers or Kubernetes to manage the configs. I figured I’d be wasting time getting stuck on little devops details when I can just hand-roll everything once and make a backup. Well, it’s been a couple of weeks and I’m still making changes here and there - and there’s no infrastructure in place to rebuild it from a clean slate. That’s ok, I guess for home use, but it doesn’t feel ideal. I had another project which was a server+iOS app which got canceled and I wanted to rebuild it recently. There wasn’t any of this automatic infrastructure in place anymore, well, it wasn’t open source so I’m not sure if I could have even done it like that on GitHub. But yeah, when I pulled it down it was nearly impossible to run without changes and adaptations to the code in order to get 2018 code (and dependencies) running on 2020+ systems and language versions, and building in XCode. Actually the easiest way to build the iOS app seemed to be to use a machine with Catalina still installed and an older version of XCode. I’m sure you’ve all been there before. Anyways, yeah, it feels like a headache to pile on a bunch of best practices and “infrastructure” anytime I want to do something with code, whether that’s write a small web service or a script that runs on laptops. But, if you make it a part of your daily process, and you have a repeatable way to init new projects quickly with identical tooling, maybe the tools get out of your way and you can ultimately be more productive and ship more reliable code? I think that’s what the author is getting at.