3 ms·
Any time I find myself doing something twice on a computer, I try and think if it would be easy to write some tool and do it if the value makes sense. Usually t
by asdff 5y ago
Any time I find myself doing something twice on a computer, I try and think if it would be easy to write some tool and do it if the value makes sense. Usually these are teensy little utilities that might pull data from websites, wrangle text and handle common files in my life, let me know upcoming meetings and connect to them, or even just little hobbies like making a scraper and local database of recipes vs manually going to that js heavy website prone to link rot.
All these exist on the command line, some are short functions in my bashrc, and some are more substantial written as discrete scripts and run via launch daemons. Not having to worry about gui or capturing each and every test case makes solutions fast and only a couple to a few dozen lines most of the time. I don't worry about awkard characters in my strings and all the esoteric regex and special cases that would need to go into a production ready script, because i simply don't use those characters in strings or do anything funky that stack overflow comments like to bring up as a potential pitfall. Makes it easy when I am my own client. plus it makes it easy getting all these programs to some new computer of whatever OS when all I need to do is pull a git repo full of these scripts to install.