this post was submitted on 09 Sep 2024
567 points (97.6% liked)
memes
9852 readers
3877 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.