Remix.run Logo
▲ ManBeardPc 3 hours ago

No, but if we go from data to experiment faster we see earlier if something is wrong. Once we get data we quickly can fix the data pipeline and get results. If there are issues we can quickly show what/why and discuss it with them in detail and make changes based on their response faster.

▲0c3ca83 3 hours ago | parent [-]

??

But the problem identified that is talking to people and having them record data.

▲ManBeardPc 3 hours ago | parent [-]

Yes, but they tell things and maybe forget to mention certain things or contradict other data they have given you. Now we may not notice it initially until we make an experiment and get the results. Something is wrong and we have to find out what. Talk to the customer again. Fix experiment. Repeat. Faster experiments means the latency from new data to results is less and we finish the project faster. Errors become less expensive and cause less delays. People make errors and data quality is often horrible so the shorter iterations are nice.

▲0c3ca83 2 hours ago | parent [-]

But the experiments aren't two weeks of boilerplate. Or if they are, something else is really fucked up in the stack.