What actually slows engineering down more: writing code, or waiting on experiments?

What do think about this?

A lot of the time, writing the code is not the slow part.

The slow part is everything after that. You run something. Wait. Check the results. Realize one assumption was wrong. Change a few things. Run it again.That loop eats hours. Sometimes days.

Especially in ML, robotics, and anything experimental, it can feel like engineers spend less time building and more time waiting to learn whether the last attempt worked.

Curious how this feels for other teams:

What actually slows you down more today, writing the code itself, or waiting on experiments, evals, and feedback loops?

this is what Eemoroo does, launching tomorrow.