[cratermoon]

> This is why data driven purchasing is key.

Many years ago I failed to convince my employer how buying their programmers less expensive computers with 5400rpm hard drives was an overall loss compared to 7200rpm disk drives. My argument was that any programming necessarily entailed reading and writing dozens to hundreds files all the time, especially during compile cycles. Maybe if I'd had data showing the actual time lost waiting? Or maybe I was a dumb kid trying to justify my desire to have a nicer computer for my daily driver.

[Aurornis]

> Maybe if I'd had data showing the actual time lost waiting?

This is exactly what works.

Adding analytics that reports duration of test runs to a central server makes it easy. Some developers panic at the thought of this because it feels like spying, but the data is immensely helpful.