I did not set out to spend 10,000 hours writing code. I set out to play soccer without my knees hurting. The 10,000 hours is just what it turned out to cost.
Why the hours were necessary
The shoe I wanted did not exist. Nothing on the market accounted for the actual shape of my feet, let alone adapted to how I moved or what position I played. So I had two options: keep buying shoes built for someone else's feet, or build the tool that could design one for mine. I picked the second one without fully understanding what it would take.
What it took was a Grasshopper 3D algorithm that could read a foot scan and turn it into printable shoe geometry, and I had no idea how to write one. I taught myself, mostly through online resources and courses, a stack of YouTube tutorials, and a handful of college classes that happened to cover the right fundamentals. None of it was a straight line. Most of the early hours were spent being wrong in new ways.
The loop that ate the hours
Coding and 3D printing started at the same time and never really separated. I would write logic, print the result, put it on my own feet or a teammate's, and find out exactly where it was wrong. Then back to the code. Fit, comfort, durability, performance, each prototype got measured against all four, and almost every one of them failed at something useful to learn from.
That loop, code, print, test, measure, repeat, is the actual reason this took 10,000 hours instead of 100. Feet are not a simple design problem. A fix for one issue routinely broke something else three steps downstream, and the only way to find that out was to run the loop again. There was no shortcut through it, just enough repetitions that the algorithm slowly stopped being wrong in the ways it used to be.
Grasshopper's open source advantage
I did not do this entirely alone, even if it felt that way at 1am with a failed print in my hand. Grasshopper is open source, and its plugin ecosystem and the ongoing work of the global coding community handed me tools and capabilities I would never have had time to build from scratch. That ecosystem let the foot scan to shoe geometry pipeline keep absorbing the latest advancements instead of stalling out on my own bandwidth.
What those hours built
Ten thousand hours of coding, printing, testing and measuring is why Prevolve's custom-fit cleats exist at all, and why every pair since has been built on top of everything the ones before it taught us. If you want to see exactly what that decade of saves actually looks like, down to the day-by-day history of the file itself, I mined the whole archive and wrote it up in the data-mined sequel to this post.