re: 5 Things you should NOT be ASHAMED of as a developer VIEW POST

FULL DISCUSSION
 

This post made me really felt better. Thanks! But I have some questions still.

I'm self-taught programmer. I've been working as a full-stack developers for 6 years. But still, I can't explain some things easily some times. I'm good to find solutions and apply them and I know I can build everything if I have enough time but I feel bad when I did not answer a question easily and good. This question might come from a friend or interviewer.

For example: what is object-oriented programming?

It seems like easy question and actually I know how to write code with object oriented, data-hiding, interfaces, inheritance, isolation... But I might not put them together and tell a good answer sometimes.

Is that situation makes me bad programmer or junior? I can't say myself senior because of that. I think mid-level is better for me. If you think so, do you have any suggestion to solve that problem? There are a lot of things in programming, so how can I explain everything very well. I guess my memory is weak :|

 

Have you ever tried to teach a kid about anything?

I have the same feeling just like you, I remember there was one day I had to "teach" a room full of developers about Array in JavaScript.

I could say I understand clearly how array works at that moment. But it took me more than a week to prepare the presentation, and 3 days to practice on how to do the speech. Yet, it was horrible. I missed this, missed that. Someone asked some questions, and I stuck. They did not try to embarras me, we had great discussion later, but honestly, that was the day I've learned deeply about Array in Javascript.

 

Thanks for response. I like the idea. It may help me because I need to learn every detail to teach it someone. I'm gonna share the idea with my friends and gonna offer make this weekly or biweekly. Everyone can pick a topic and prepare a presentation and teach it to the others :)

 

This is a great point and drive for another article, I'm writing that covers the Feynman Technique which is exactly what you've mentioned above

Good on you for trying to teach people!

 

Sorry i forgot to reply, no it does't make you a senior or junior. There's tonnes of other factors that make you a senior other than being able to code or explain something (sure those are very important) but seniors take into consideration the business, the team and seniors are those who get things done when others can't in a better way.

No need to remember what OOPs definition is, but as long as you understand it well enough to explain it with your own words thats all that matters!

 

Thanks for response. It's so sensible. I started to write blog posts on that topics and trying to explain the topics with my own words. Hope it's gonna help me :)

Perfect! That realisation itself means you're going to smash it! All the best!

code of conduct - report abuse