AikiWeb Aikido Forums - View Single Post

cguzik · 12-21-2000, 05:02 PM

In software engineering, when your program works, you run it at full speed. When it's not working, you run it slowly, in a debugger, stepping through the code a bit at a time. Sometimes you think it's going to work and run it at full speed, and then find it doesn't actually work -- and then you go back to the slow debugging process to figure out where things didn't go quite right.

I don't know about you all, but this seems to fit the way my aikido training goes pretty well.

So, to answer the original question, I think we learn how and where our errors occur at slow speeds and I think we discover that those errors exist at faster speeds. Efficient training needs a bit of both I suspect.

Chris Guzik

[Edited by cguzik on December 21, 2000 at 05:12pm]

12-21-2000, 05:02 PM	#13
cguzik Location: Tulsa, OK Join Date: Aug 2000 Posts: 166 Offline	Running Speed Versus Debugging Speed In software engineering, when your program works, you run it at full speed. When it's not working, you run it slowly, in a debugger, stepping through the code a bit at a time. Sometimes you think it's going to work and run it at full speed, and then find it doesn't actually work -- and then you go back to the slow debugging process to figure out where things didn't go quite right. I don't know about you all, but this seems to fit the way my aikido training goes pretty well. So, to answer the original question, I think we learn how and where our errors occur at slow speeds and I think we discover that those errors exist at faster speeds. Efficient training needs a bit of both I suspect. Chris Guzik [Edited by cguzik on December 21, 2000 at 05:12pm]