> If you're not taking a major part in the final tasks of a project, how can you be so certain you are good at preparing it for the future?
I'm not the parent, but I'll answer, from my own experience.
The "final tasks" of a project aren't important, in the grand scheme of things, at least, not the way that I work. If I have an idea, let's say "Github" for example, what's the core of the application? Whatever your answer, I'd bet you dollars to doughnuts that it isn't "the login page", or "the frequently asked questions", or "what color the navigation bar is".
The 'core' of the application is the interface between git and github. That's also, generally speaking, the 'hard part'... and the developer that can take you from a blank screen to a demo, by his or herself, and can deliver that product to market, is the ideal developer. If you can hire a guy that can take you 95% of the way there, and then outsource the fiddly bits like login and navigation to oDesk or whomever, then you've got a real talent. That is the type of developer the parent seems to be describing, at least to me.
As to his self-understanding, I dramatically prefer working with developers that know where their limitations are, and know where they're not good. I find myself getting bored with the result of a QA report, and it doesn't excite me. Solving a problem excites me. Tweaking an animation to prevent flickery scrolling on IE7 does not excite me. It took me a lot of years to get from being the 95% guy to the 100% guy, but even my 100%ness is qualified -- it has to be within a given set of parameters. For somebody to acknowledge their weaknesses, in my opinion, demonstrates a higher degree of self-awareness than the average person who doesn't.