Re:Experiment: The costs of slow build times
by chasinglogic on Friday December 09, 2022 @07:22AM
(#33920473)
Definitely, it's also important to remember how salaries vs. infrastructure costs show up on a P&L sheet.
Salaries are going to be considered largely immovable and they won't "go down" or show as a lower number on the P&L as a result of your devs getting some time back. Whereas your infrastructure costs jumping up (even by a small amount, esp if you have any amount of scale) will set of alarms, rightly IMO, in the Finance department.
Re:Experiment: The costs of slow build times
by pron on Friday December 09, 2022 @07:46AM
(#33920632)
Yep. In developer-targeted products the users are usually not the customers. Making the product appealing to users is (often) necessary, but it's insufficient to convince the actual customer. Sometimes the problem is in the product itself, but often it's just a matter of shaping the marketing message.
Re:Experiment: The costs of slow build times
by DrScientist on Friday December 09, 2022 @06:25AM
(#33920153)
Totally agree.
What matters is development velocity and quality - these are the things you will be competing on - not really cost of production.
Slow builds impact both of the above of course.
What could be more convincing is the effect on product value that build times could have, and they certainly could (and I, for one, believe that they do, especially if they can be made to be less than 15 seconds or so). For example, it's certainly conceivable that very short build times make it easier to write more tests, which could result in more correct software with better features and/or a shorter time-to-market.
Some products targeted at developers also make the mistake of focusing their marketing message on the cost, perhaps because that's the part of the business that developers personally feel, but it's not the message that would convince their employers.