I doubt it. John worries about performance all the time, but if he's spending his development hours on getting 600 FPS instead of 500 FPS, I don't see why he should. 60 FPS instead of 50 FPS I can see, as it's within the realm of the visible. I'm usually concerned with minimizing the number of billable hours to the client. If I can meet the client's need without writing efficient or reusable code, I do so. If later on they decide they want it efficient and/or reusable, they can pay me more for that. I'm not hoodwinking them, as vetting an actual working design makes it easier to figure out what is actually efficient or reusable. When requirements change, they waste a lot of optimization work.