3 ms·
As a viewer, I generously read all six paragraphs. And I learned nothing about the product. ~~~ If you're going to spend six paragraphs making claims, which
by simonsarris 14y ago
As a viewer, I generously read all six paragraphs.
And I learned nothing about the product.
~~~
If you're going to spend six paragraphs making claims, which is in my opinion a dangerous thing to do[1], you better have the user saying "yeah!" in their head successively louder as each paragraph goes by, because you're delaying the part where you actually tell the user about the product. But this page doesn't really say anything about the product.
[1] Making one claim after another is dangerous because it gives you a chance to say something stupid or disagreeable. For instance their claim:
> I’ll wager that Facebookers spend 50% of their times on tests, time which could – in an ideal world – be spent on product.
Serves to make them look a bit ridiculous. If the product is a polished app then spending time on tests is spending time on the product. It seems silly to suggest otherwise.
Stop claiming things and tell me what your damn product does. If I have to look it up what it does I'll probably find a list of competitors alongside it.
(edit: which is exactly what wikipedia shows http://en.wikipedia.org/wiki/Continuous_integration#Software http://en.wikipedia.org/wiki/Continuous_integration#Software)
- pbiggar 14y agoGood point. We didn't want to make this a sales pitch - we wanted to make it a call to action about the state of testing. But I can see how pitching the product would help. So here goes: - incredibly easy to set up, you'll probably have your tests running in one click - very fast - our users report tests run faster than on their own machines - Supports parallelism - you can reduce your test times by up to about 7x.
- kourge 14y agoThe author spent 5 paragraphs making claims. The sixth one tells you exactly what the product does.