4 ms·
Design can be split-tested by someone with average skills and end up with above average results. The same is not true of development. Throwing together a bunc
by viscanti 15y ago
Design can be split-tested by someone with average skills and end up with above average results. The same is not true of development. Throwing together a bunch of things and trying them in production leads to unmaintainable code and many hard to track down bugs. One requires time and persistence, the other requires knowledge, planning and problem solving.
- sidmitra 15y ago>Design can be split-tested by someone with average skills and end up with above average results. I do think split testing is not the answer in every case. Firstly you have to know what to split test. A product like Dropbox cannot be designed just by split testing for example. See MS Windows file copy as an example, i still think it's broken. With dropbox, somebody noticed a problem and wanted the product to be so easy to use, even to the extent of being invisible. I would imagine split testing would lead to dozen tabs of configuration of file sync rules.
- felipemnoa 15y agoI'll dare to say that the two are just as important. Think of it as one being a heart and the other being a liver. Both are just as important since without one of them you'll die. Have a poor heart or a poor liver and you'll live a sub-optimal existence.