I just make some shell scripts to automate boilerplate.
That way, once I have properly debugged it, I know it will give the correct output everytime in the future and I don’t need to keep checking it.
I don’t plan for all of them.
Just when I realise some specific one is getting too repetitive, I make a script for it.
Never needed to do so at home (yet), because my IDEs usually provide good enough boilerplate and I am mostly doing learning projects (i.e. hardly any repetition), but I did make a few in one of my previous work places, which someone else might be using rn (hopefully not, because it was meant for me and not for users).
I just make some shell scripts to automate boilerplate.
That way, once I have properly debugged it, I know it will give the correct output everytime in the future and I don’t need to keep checking it.
That’s nice too I guess, and more eco friendly
But there are different types of boilerplate, planning for all of them can be a bit of a pain
I don’t plan for all of them.
Just when I realise some specific one is getting too repetitive, I make a script for it.
Never needed to do so at home (yet), because my IDEs usually provide good enough boilerplate and I am mostly doing learning projects (i.e. hardly any repetition), but I did make a few in one of my previous work places, which someone else might be using rn (hopefully not, because it was meant for me and not for users).