[jedberg]

At one of my jobs, the very first thing I did when I arrived was redo the code deployment system to get the deploys from 30 minutes to 30 seconds.

Cutting deployment time makes a huge impact because it makes everything go faster. You can iterate faster, which means getting bugs fixed faster, getting data to product managers faster, etc.

It also has an effect on reliability. The faster you can make changes, the faster you can fix errors (as long as you aren't introducing them faster too!).

It's always the first thing I focus on.

[Elixyrs]

> At one of my jobs, the very first thing I did when I arrived was redo the code deployment system to get the deploys from 30 minutes to 30 seconds.

We have the exact same issue in my company. Could you explain how you managed this?

[jedberg]

The way I did it then probably wouldn't work now. I literally just wrote a perl script to automate pushing copies out to all the servers. They were doing all by hand before I got there.

If I had to do it today, I'd be looking at GitHub actions or some other similar CI/CD tool. If you're already using those, then I'd ask what is the slowest part of the process, and how can we speed it up?

To answer that question you obviously first need telemetry and monitoring to track each step of deployment. That telemetry will be useful in not only finding slow spots but tracking your improvement, which will help you both in operating as well as justifying your work to others.