Personal blog

Tag: automation

Don’t automate everything. Go Elon instead.

If you “automate everything” you end up with cargo-cult of your process.

What you should do instead is employing Elon’s 5 steps protocol (“the Algorithm”) that consists of in order:

  1. Question (requirements)
  2. Delete
  3. Simplify / Optimize
  4. Accelerate (cycle time) 
  5. Automate

Always. In. That. Order.

If you automate something that meets unnecessary requirements – you’re doing it wrong.

If you automate something that shouldn’t even exist – you’re doing it wrong.

If you automate something before you try and simplify it real hard – you’re doing it wrong.

If you automate something prior to accelerating it’s cycle time – you’re doing it wrong.

Every such automation helps cultivate current pathology.

Possibly the most common error of a smart engineer is to optimise a thing that should not exist,

Elon

What a waste it is to automate “everything”!

Automate aggressively but first own the progress and make sure you automate the right thing.

“Automate everything” is a scam

Nowadays I see people going crazy about automation. Everything must be in Docker containers, If it’s not in docker, I ain’t touch it.

Every task must be performed on the CI server, every repetitive task must be converted to a script, nothing in the MVP can the back office do manually. People are praised when they claim: “automate everything”!

I am on the very opposite side. I think automation generally isn’t worth it. It can be harmful to your project and see the trend of “automate everything” kinda crazy. Let me explain why.

Continue reading

© 2024 Bartosz Krajka

Theme by Anders NorenUp ↑