Hacker News new | past | comments | ask | show | jobs | submit
I was unsuccessful in area of automation because of different issue.

By trade I am a .Net software developer so as a lot of people would imagine — I was not able to accept a script that wouldn’t be reusable and flexible, basically over engineered.

I do quite some devops so I finally had to accept the fact that I can write simple script with hardcoded values that will live on a server (where I can copy paste and change values to meet other server) and most likely I will not have to look at that script for years as it will be running with cron doing its job without an issue.

Over engineered scripts designed from get go always required debugging from time to time so lots of time I was just doing stuff manually to make it quicker.

So I started winning when I accepted first script can be really simple and when needed I can move it to be parametrized but if not it will just keep doing it's job there on the server.

There is an idea I have been enjoying called WET, Write Everything Twice. Basic idea is you should only make things more general and parameterized if you need to write it a third time.

The upshot of this is you actually have a much better understanding of the different way your script needs to work if you're adapting it for a third use instance.