Ask questions as a junior developer?
Hello everyone,
As a junior developer, especially in your first real job, are you "allowed" to ask the senior questions and get things explained, or is the answer simply "Figure it out yourself," "Teach yourself," etc.?
Thank you and kind regards
(3 rating, 3 votes, rated)You need to be a registered member to rate this.
Loading...
Who doesn't ask, he doesn't learn anything. Of course you shouldn't let everything go passively, but it's better to ask than tap into the dark forever or build crap.
If this is not possible in your company, it might be the wrong company.
Depending on the company or on your colleagues, they should usually help you and support you
Of course you can. The balance is crucial.
If you don't get any more after hours, that's just as little worth for the company as you keep asking someone.
Unfortunately, this is not always easy and also strongly dependent on workload of experienced colleagues how good and motivated they are to help. Don't always smell as good as it should.
Find how finds itself out also very un Collegey, better I just don't have time coming in x time again if you can't solve it yourself, or just say where to find a solution. Apart from these, don't look in the docu next time, I asked what they didn't understand at the docue and if there was nothing left.
Meal!
No law has been known to me so far that the question itself is prohibited.
On the one hand, the things that you learn in education or in studies rarely have something to do with practice. On the other hand, no master has fallen from heaven. Furthermore, work processes, departments, instructions, projects, customer requests, processes and co. differ from company to company.
In this respect, it is actually normal in all professions that new employees must first introduce themselves into the usual company structures. In this respect, questions arise logically. And, just because one can or has learned something "theoretical", it does not mean that what one has learned demands 100% everywhere worldwide or exactly so is implemented. Old hares or people who have been in the company for a long time already know internal structures and have a better insight and experience.
Depending on the order, employees, company philosophy, money, time-pensum and co., one will give help to self-help or demand and promote self-employment and self-employment. Some employees have more or less pleasure. You have to infect yourself, research yourself, bring in and ask questions. Being inactive and constantly asking questions is not good.
It is also about the commitment/the attempt.
Basically, it's logical. Before making a mistake or being uncertain, you ask. That's what supervisors and colleagues are there for.
I always ask in the work. Everything you cannot know and practice often reveals other things. You can still have so much "theoretical" knowledge.
Good luck!
Find this classification between Junior, Intermediate, Senior etc. eh nonsense. What are you going to do? Especially since it is usually only in a small area of expertise.
But a good "senior" is like a teacher and helps you get a way to the solution, because as a computer scientist, the ability to solve problems systematically is much more important than huge expertise.
Therefore, ask in any case, and if such an answer comes back, you know who you don't have to ask in the future and ask someone else.
This depends entirely on the Senior Developer.
But in principle it is never wrong to ask questions.
So I'm a junior and I'm asking things every day. That's normal.
So if that's your concerns, I'd change the operation… Just ask him and if there is a stupid answer I advise you to change the operation, because you probably won't learn a lot
You should ask questions, but you should ask yourself. The senior programmer will probably ask you questions like you've already tried.
Why not? Even a senior should be allowed to ask questions.