4 ms·

You're a very long way from the only developer to take this road, and it's a road that's very well traveled indeed. Writing your own build tools seems to be an

You're a very long way from the only developer to take this road, and it's a road that's very well traveled indeed. Writing your own build tools seems to be an attractor task for programmers. Every year there are a few more build systems made public by eager developers who started simply by solving their own problems; almost every one of them having started life as a lash-up of scripts by frustrated programmers just like you. I suspect the number of people who have ever traveled as far along this road as you have so far numbers in the millions.

travisgriggs 7y ago
Yes, I was attracted to it. If nothing else, it made my Python skills that much fuller. Its never something I wanted to turn into a reusable solution though. I have 3 of these right now, each time, I took the old one as a starting point, and then changed to match the newer needs (and only those specific needs) and maybe whatever was my latest approach to solving. For me, the utmost guiding principle has been to keep them simple so that someone can casually tweak/change it with not too much work. I've worked in automation (food processing, nuclear manufacturing, and agriculture) for a lot of years. One thing I've discovered is that while you can automate everything in the real world, there really are some parts of the process where an adaptable human being is the best tool for that particular part of the process. I've viewed these efforts in a similar vein.