Can't see a whole heck of a lot to
disagree with there.
Develop and develop and then develop some more. Each successive task, learn fom what you did right and what you did wrong last time. The more you do it, the quicker you catch your mistakes. Have no doubt there will be many, some only discernible in hindsight. Code that seemed 'ideal' six months ago now looks like the deluded scribblings of a moron. If it still looks good, change careers, or at least find a new role, switch languages or environments, work on a different sort of application.
In our job, change is a given, if you don't, can't or won't change along with it, do something else, you will always be a junior.
