Software Development at 1 Hz
I wrote numerical code for a while, it simulated a magnetic material. It would take hours to run a simulation long enough to be able to verify that it was correct. Make a change, wait five hours, check if the change worked.<p>I eventually started keeping a journal of every code change I made, along with the hash of the binary that it created. I could use this to make several independent changes and run them all at the same time. When one run finished, I would verify its behavior, look at the binary&#x27;s hash, and then know that my code change was safe. It was a very slow process, but effective. After doing this kind of development for a while I&#x27;m weary of claims like this that imply that feedback with a latency &lt;10s is actually a good thing. High latency feedback forces you to be more methodical in your development and think about the changes you&#x27;re making.