this post was submitted on 18 Jan 2024
499 points (95.3% liked)

Technology

59207 readers
3264 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

People often ask why I contribute to open source projects or otherwise work on building automated tooling. They see me spending hours to automate a task or fix a bug that take seconds to do or avoid manually, in a way that the original XKCD comic says won't pay off. The disconnect seems to be that the comic and those people only consider time it saves me, not time it saves the tens to thousands to millions of other people who will use the script or patch or whatever when I publish it. So, here's a version of xkcd.com/1205 updated for making decisions that benefit a thousand people instead of just one.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 9 months ago

This! The point of automation is rarely saving time. The point of automation is increasing quality.

It can be a data quality, it can be mitigating a production risk, can be avoiding regression.

Heck even unit tests are automation (you may just manually test your code once and call the day).

I am not saying that automation is always good, but the evaluation should be

  1. what is the cost of production/data quality/regression gone wild? (Possibly in€/$/¥)
  2. what is the cost of the person/team performing the task over 1 Year (Again, £€$¥)
  3. what is the expected cost of the person/team implementing automation?

Then you do (3)*3 - (1) *3 - (2). Is it positive? You do, is it negative you? You don’t. The more it’s positive the higher the priority of doing.

Why the *3? The first because the expected cost of automation is always massively underestimated The second because it takes multiple times something goes wrong till the decision is reconsidered 🙂

Why 1 year? Because generally the task to automatize changes or disappear