|
|
|
|
|
by Jensson
1708 days ago
|
|
As you make something cheaper demand for it goes up. Easy to forget about it when you try to calculate the value of automation. I'd say in most cases automation pays off if you do it properly, not to do the intended task but to do all the unintended tasks, reusing the automation code for later, reducing errors from manual work and opens up doors for new product design paths in the future. This assumes that you actually own the product, if you don't own the product and just have a job to do then why bother about saving time, so in this case you should still automate it because automation is more fun. |
|
Then I cut it to 7 minutes, saving an additional 30+ minutes, because everyone was now running the build 4-5 times a day.
What I really saved was wasting each other’s time and goodwill by reducing the frequency and severity of people checking in broken code that blocked everyone else. Because they were expected to test more often, and they made smaller commits because it wasn’t so painful.