As a junior in my current tech stack but senior in general I can be in both sides at the same time. (aka the Schrödinger's seniority 😂)
It's very important to show the senior how commited you are with this, that you're ok knowing you don't know but you tried to solve by yourself... but... the next question could be, did I spent too much time on this task?
That's why you ALWAYS should try hard to ask as much as you can before start the task even the easyest ones, because at that time the senior is mentally prepared for your question storm, and really WANT to help you.
Where this feature should be placed in code?
What is this bug causing exactly? How the end user usually notice this bug?
What is the expected behavior? And the current one?
Where is a similar object/component/piece-of-code that does something similar than this? Why aren't we using that and creating this new code instead?
That generic questions can help you, junior, to have a smooth start and ask better questions later.
That's why you ALWAYS should try hard to ask as much as you can before start the task even the easyest ones, because at that time the senior is mentally prepared for your question storm, and really WANT to help you.
I love this tip and I agree. Questions in the beginning is a lot more welcome than questions in the end.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think you nailed it.
As a junior in my current tech stack but senior in general I can be in both sides at the same time. (aka the Schrödinger's seniority 😂)
It's very important to show the senior how commited you are with this, that you're ok knowing you don't know but you tried to solve by yourself... but... the next question could be, did I spent too much time on this task?
That's why you ALWAYS should try hard to ask as much as you can before start the task even the easyest ones, because at that time the senior is mentally prepared for your question storm, and really WANT to help you.
Where this feature should be placed in code?
What is this bug causing exactly? How the end user usually notice this bug?
What is the expected behavior? And the current one?
Where is a similar object/component/piece-of-code that does something similar than this? Why aren't we using that and creating this new code instead?
That generic questions can help you, junior, to have a smooth start and ask better questions later.
I love this tip and I agree. Questions in the beginning is a lot more welcome than questions in the end.