Hence the caveat: conduct yourself accordingly. Just because you don't use specifications doesn't make you a bad programmer but you must be aware of your own s

Hence the caveat: conduct yourself accordingly. Just because you don't use specifications doesn't make you a bad programmer but you must be aware of your own short-comings and plan for them. If you're not allowed to use specifications you're being told you're not allowed to think. If that's the case you know there are going to be errors produced by the team either in the design itself or in the implementation.