Hi! I'm a recently hired Jr. Software Dev. One of the first things I was told by my Sr. Software Dev was to ask all of the questions in the world because there's going to be a lot that I don't know, and I've been following that advice. However, I do struggle with articulating certain problems that I run into while coding something new because I don't know how to phrase it all the time, and I'm scared to say the complete wrong phrase and sound stupid. Do you have any recommendations or advice?
That's the essential beauty of learning, it's okay to sound like you don't know what you're doing, because well, you don't know what you're doing!
Here's some pro tips to asking questions you don't know the answer to:
I don't know how to unpeel a banana.
How do you eat a banana? - You peel it like this!
Is there a reason this banana is green and not yellow? - It's not ready to eat yet!
I don't understand repositories.
Where do I declare all my tables and schema? - In the DbContext.
How does the DbContext know how to connect to the database? - The connection string in the web.config tells you everything you need to know.
Why are there so many web.configs? - One for every environment of course!
The key to asking a dumb question is doing your best to fill out your knowledge as best you can of what you do know so that your question only attempts to fill in the gap of what you couldn't figure out on your own. Continue to quest and be thirsty for self taught knowledge but don't waste mounds of time when you've hit a roadblock when you could have just asked a simple question and had it answered right away. That's what mentors are there for.
Wow, thank you so much! This is great advice and I'll be sure to follow it :)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.