Hey, if it ends up saving time and stress after those two days it was worthwhile.
Seems to have become one of the fundamental rules of the Internet now, I approve 👍
it wont, it’s just more enjoyable to automate a task than to do it manually
There’s something really satisfying about running a script that you know would save time. Even if the overall time is probably a negative.
I wrote a script that would log me into our AWS EKS stuff. I typically would have to copy these 7 lines and look up which cluster version I’d need. One of my lines just pulls all the clusters and I use fzf to select the cluster I wanted. Takes away all the pain and makes me feel smug. Love it.
It’s a two minute task, but it happens randomly between the hours of “romantic dinner with my wife” and “ten minutes after the baby finally went down for a nap”.
Automation also cuts down on mistakes.
Or greatly amplifies them if you coded it wrong.
I don’t understand why you are attacking me …
/s
Test 1: Locking process. Unexpected error encountered. Exiting immediately. Test 2: Waiting for process unlock to proceed. Test 3: Waiting for process unlock to proceed. Test ...
The exception is if it’s open source and can save thousands of people two seconds.
Doesn’t even have to be the case. A 2min task done every (work)day, takes up a bit over 7 hours/year. After 2½ years it will be a benefit to have automated it!
The benefit of automating is really measured in hair loss and extra time to grab another coffee.
Only if the requirements stay the same for 2.5 years. Otherwise there’s probably another week of time trying to update the initial work, then just throwing it away and making a new solution that’s theoretically easier to update.
If changing requirements mean you need to update the script, then updating the script is part of your job. QED. I don’t see the problem with a little job security.
Yeah, just add it to the ‘amount of work you are putting’.
When setting up git hooks for my project, I looked at other’s OSS hooks first. That shaved off significant hours off of my Research.
Yeah, and you build skills and reusable code base that’ll be useful for automating/ simplifying future tasks 😎
Some years of this, you get to the point where you can solve damn near everything quickly and people think you’re some magical shit-wizard
I don’t know how to code, but I’m already a shit wizard.
you get to the point where you can solve damn near everything quickly and people think you’re some magical shit-wizard
This is basically my work life, and its almost a problem because I’m the first guy people call when they need something done.
The perils of being competent. /s
Fucking competence. I wish I was bumbling fool with severe Dunning-Kruger more often than I care to admit.
And if it’s a task that will need to be done thousands of times a month or even year, you should thank them for it.
Obviusly it has to be done once evey year…or a decade.
A long time ago when I handed off my duties when leaving, my replacement (in house) was absolutely astonished at how little I was doing. I had taken the global fleet of bar/retail/hotel/restaurant/office printers (minus properties in China) from around 30% of total being OOS to less than 3% in 18 months. Everything from giant plotters to the fry cooks’ line printers.
What my replacement didn’t see was the 3 months I spent not sleeping. Worth every second.
Automate the living fuck out of everything (that’s ok to automate) & read reports / logs.
[edit] A love letter to Bash, Korn (pdksh) & Cron [dbl edit] And Tail. [tpl edit] and I guess all of /var
Any shell is the duct tape of computers.
The best engineers can do anything with duct tape.
With this as a guide, it would be enough if the task needed to be done twice per day to break even after five years.
That’s also only assuming that one person is doing that 2 minute task. If you automate a 2 minute task for 5 people, then it’s only 1 year.
I just realised I was being waay more efficient than I needed to be.
I can spend 2 minutes scanning a page for a certain word every time I need to search for something.
But I’m very happy somebody spent the time to code Ctrl+F.
Ctrl+f code has to be some of the most efficient automation ever written. Time spent was probably about day and the time saved in work hours is probably in the trillions at this point.
Yes, but since it runs automatically every day and emails my team the results, I don’t have to remember to do it on my own. I don’t even have to be working that day. Taking “my ADHD memory” out of the system is always a win.
If you choose to do a task manually over and over instead of automating it, you might as well go dig ditches and hammer nails.
Non automated tasks remain in the inbox for a week, so spending 2 days automating them means they’re finished earlier.
Programmers after slacking off for two days to improve their factories in Shapez2 because they already automated all their tasks.
One more advantage is that you now have the full process well documented (via code) and if you realize some change is needed you can repeat the task quickly.
Eggcelent
