[taurath]

You don't. You need to set reasonable expectations and approach a coding job as a "new" task instead of one you perceive you've failed at - you probably know more than many intermediate developers but it sounds like your ability to ship code is the biggest problem. Being a programmer doesn't mean knowing the entire stack and each and every piece of it, its about being able to pick out whats important to the task at hand.

I've run into a frequent roadblock in that I always want to know all the elements of what I'm getting into. I'm finding that in MOST cases its not important at all, until you're architecting a new system. Leave that to senior level folks for now, just find a place you can fix or work on UI elements or clear bugs - theres no need to be so stressed about a programming job, just reach for a branch that you can grasp firmly.