3 ms·
Just to use your example, you would have a VERY hard time convincing me to spend $3,000 a month to speed up testing time. Running tests isn't exactly dead time.
by issa 4y ago
Just to use your example, you would have a VERY hard time convincing me to spend $3,000 a month to speed up testing time. Running tests isn't exactly dead time. It gives engineers a break, they can think about other things while running them, get coffee, etc. There is DEFINITELY value there, but not $3k a month worth.
That said, pricing correctly is hard and requires a lot of experimentation. Growth and adoption might be more important at this stage.
- tasuki 4y agoFrom my experience, it depends... Is this a test suite I run during my development cycle? If so, I get distracted if it takes more than half a minute, open HN, and lose a bunch of time. Is this a test suite that runs once I open a pull request? It can run an hour or two, I don't mind. I'll move on to the next thing and check tomorrow morning if it's passed. If it failed I start my day by investigating why. I care very little about speed here.