I don't know if I agree. Software is a pain to write well, especially for a process that's not yet understood.
A simple example from my personal life is writing down exercises I do at the gym. I was surprised by how many different type of exercises there are. At first it was just "lat pull down, 80 pounds, 3 sets, 10 reps". Then I tracked different manufacturers, to stay on top of machine differences. Then I started tracking number of attempted reps, along with reps at lower weight. Then I made a note for weights per arm, for machines with independent weights on each side. Then I took into account the base weight for the bar. I could add features forever.
To manage the complexity, I started looking at software to help. I decided to scrap the idea of building software in favor of writing exercises on a sticky note I stuck to my wallet, and later migrating the data to a "good enough" spreadsheet.
Software is meant to serve us. If you let it take over, it will. Manufacturing benefits from software in places, but sometimes a pen, sticky, and spreadsheet is all you really need, and if you outgrow it, you'll understand exactly how software can help.
My uncle and 101 year old grandfather make machine parts in a shop with a bunch of old school analog stuff. They have a computer for a milling machine. It all works great.