I don't think there can be an absolute measure of how good of a programmer one is; it is a function of how well acquainted one is with the problem at hand. A p

I don't think there can be an absolute measure of how good of a programmer one is; it is a function of how well acquainted one is with the problem at hand. A problem is not only defined by stuff like the core routines of the program, but also everything surrounding it, like the structure of the code and of the program as a whole, the environment the program is supposed to be running in, and how to collaborate or manage the other people who are working on the program. Though at this point it's probably better to use a broader term like "software engineer". A programmer who has enough experience across the whole stack for a certain problem is going to be able to deliver good, readable and efficient code in a timely fashion.