Now, word of warning, I don't sugar coat things, I'm not gonna slap the rose coloured glasses on your head, blow smoke up your backside, and give you disingenuous soothing syrup words.
To be brutally frank, if you're "feeling inferior" or "scared" about your code, that's EXACTLY the time to have others looking at it!!! When others are critical LISTEN instead of packing up your toys like a child and running home to mommy.
You NEED negative feedback -- no matter how bad -- to get better! Don't practice alone, it only embeds your errors!
When someone says something negative, REGARDLESS of how it's being said, RESEARCH what they are telling you. Weigh the pro's and con's. Learn, adapt. DEAL WITH IT!!!
Mind you, said feedback has to have substance... It's ok for someone to say it sucks if they say WHY it sucks. That's how you separate the wheat from the chaff on feedback. If they use a term you don't know, RESEARCH it to find out what they are talking about -- FAR too many people right now take even the slightest negative feedback as a personal attack -- and that's BULLSHIT if there's actual advice being given... and if you don't understand the advice, LEARN!
Computing is an industry where on the hardware side three years is obsolete, five years is the scrapheap. Software is LUCKY if it can see double those numbers, and sometimes it's half that if you deal with anything security related.
So if you're not ready to change, keep learning, keep improving, and get feedback from others, you might as well just pack it in now. Otherwise, man up, take your punches, and get it done!