Earlier quoted context omitted.
Yes. That's why I mentioned not only type trickery but the one domain specific example where I can claim to be an expert in (mathematical optimization). I guess, the original ten years was hyperbole?
I think you're missing the point completely. Patrick's comment wasn't about a specific for loop and how hard it is to understand. Knowing what types of problems people have and how to write code to solve them is much harder than learning the JVM spec and much more valuable. How long did it take you to become an expert in mathematical optimization, for example? I doubt very much that that's something you picked up in…
But here's where my contention lies: Making those choices is hard. But you should be able to explain the logic behind them (or how you came up with a solution) in a few weeks.
To give an analogy: The first task is like acquiring a map of a territory. That needs painstaking surveying of the whole area. The second is describing a path you took through that territory. You needed the whole map to choose the right path, but describing the path should be faster than acquiring (or describing) the whole map.