I used to say that being a great programmer was being a professional forgetter -- in that you had to know how to forget vital details without getting yourself hurt. So, like a professional tumbler, or a stunt-person specializing in falls. It isn't about the falling. Anyone can fall. It's the expert who can fall without getting hurt.

If you structure code correctly, you can forget about all the details you need to know to keep from getting hurt, but rediscover those things quickly when you need them. This is a great way to talk about program design in a nutshell, but it's also a terrible way, since it's prone to make people with short attention spans think you're nuts!