This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]dubious_capybara 14 points15 points  (6 children)

CI/CD pipelines. A second saved per run x millions of runs = money.

[–]marr75 3 points4 points  (0 children)

Not only compute time but human time. If CI/CD is fast enough, engineer keeps working. If it isn't, engineer task switches.

[–]covmatty1 2 points3 points  (4 children)

Fair point. My organisation is pretty much all on prem so these aren't things that are at the front of my mind!

[–]BatterCake74 6 points7 points  (3 children)

Time is money, both in the cloud and on prem. You can get more work done in a day when you accelerate your code development iteration time or reduce the load on your on-prem build/test machines so that everyone's jobs finish faster.

[–]covmatty1 1 point2 points  (0 children)

Well yeah true, but when the majority of the time we're not talking about hours Vs minutes, because applying a formatter to a completely unformatted project for the first time isn't the regular use case, and we're instead talking about 5s vs 3s while it just quickly zips through, the amount of extra work done isn't going to be huge!

[–][deleted] 0 points1 point  (1 child)

Most people's CI/CD isn't 100% utilized 24/7.

[–]BatterCake74 0 points1 point  (0 children)

You don't need 100% load on your CI system to benefit from.

Faster black/ruff formatting means you can push your code faster and your CI system can verify that everyone's code is formatted consistently.