This blog post is a draft. Please don't share it in its current state.

An Argument for Automation

February 10th, 2020 1 min read

frosted glass window
frosted glass window

We all have workflows we go through regularly to get our job done. When we start working we need to open a few applications, websites, and start a few servers. When we commit code we want to make sure we didn't break tests or fail linting.

Saving time is not the only reason to automate workflows

You could take time to automate all of this stuff, but is it really worth it? I mean, how long does it take to open a few apps, copy/paste some skeleton code, etc.? Let's say it takes 4 hours to automate creating all the files and things I need for a new blog post (index.mdx with metadata content and optimized banner image) — a task that takes about 60 seconds. I'd have to do that 240 times to make it worth it, right?

Sunil Samuel
Written by Sunil Samuel

Sunil Samuel is a JavaScript software engineer and teacher. Sunil's taught hundreds of people how to make the world a better place with quality software development tools and practices. He lives with his wife and his son in Bangalore, India.

Learn more about Sunil

If you found this article helpful.

You will love these ones as well.