3 ms·

Juniors also generally do not understand how a piece fits in a larger system nor are they are expected to.

by notus 7y ago

drdeadringer 7y ago
I have always had a "problem" of needing to understand how something fits into a larger system and "not being allowed to" ... because "Junior" or "new guy". Yes, I do need to know "why" this is or "why" that is. "Just because" has never sat well with me, ever. This could be my own "problem" but really: when I ask "why", give a real answer -- I'll even take a Cliff Notes answer, but just give a real answer. "Don't worry about it" doesn't do me any favors.
- mooreds 7y ago
  I saw a post from someone on a slack (that I reposted here: https://letterstoanewdeveloper.com/2019/06/21/balance-questions-with-banging-your-head/ https://letterstoanewdeveloper.com/2019/06/21/balance-questi... ). He suggested waiting for 3-6 months before you press on the "just because".
- notus 7y ago
  It's hard to give good advice because I don't know what the culture is like where you work. Sometimes this behavior is because they are feeling you out for a few months and making sure you stick around before investing a lot in you. Other times it could be because the more senior devs like being in control and making decisions. You have to learn to work around these behaviors because directly confronting them won't always go so well. The reality of the situation is they are just making their own lives more difficult by not enabling more developers to help out but that's how people are. Do you do 1 on 1's with your manager? That is the best place IMO to express what you want to do and if you're feeling left our from knowledge or conversations. A good manager will help you out and make the senior devs be more inclusive it makes sense. If they are not helping then go to the director. If the director doesn't help then you should reassess your future in the company. Note that I'm not saying quit, because sometimes, especially when just starting out, you have to work a less than ideal job to build up some experience. As long as you're still learning and growing you can benefit from it, but the second you feel like you're stagnating and you're sure it's not you it's them, then leave. Next time you will have something to discuss at the interview too about what kind of place you want to work at.

Juniors also generally do not understand how a piece fits in a larger system nor are they are expected to.

by notus 7y ago

Juniors also generally do not understand how a piece fits in a larger system nor are they are expected to.

I have always had a "problem" of needing to understand how something fits into a larger system and "not being allowed to" ... because "Junior" or "new guy". Yes, I do need to know "why" this is or "why" that is. "Just because" has never sat well with me, ever. This could be my own "problem" but really: when I ask "why", give a real answer -- I'll even take a Cliff Notes answer, but just give a real answer. "Don't worry about it" doesn't do me any favors.

mooreds 7y ago
I saw a post from someone on a slack (that I reposted here: https://letterstoanewdeveloper.com/2019/06/21/balance-questions-with-banging-your-head/ https://letterstoanewdeveloper.com/2019/06/21/balance-questi... ). He suggested waiting for 3-6 months before you press on the "just because".
notus 7y ago
It's hard to give good advice because I don't know what the culture is like where you work. Sometimes this behavior is because they are feeling you out for a few months and making sure you stick around before investing a lot in you. Other times it could be because the more senior devs like being in control and making decisions. You have to learn to work around these behaviors because directly confronting them won't always go so well. The reality of the situation is they are just making their own lives more difficult by not enabling more developers to help out but that's how people are. Do you do 1 on 1's with your manager? That is the best place IMO to express what you want to do and if you're feeling left our from knowledge or conversations. A good manager will help you out and make the senior devs be more inclusive it makes sense. If they are not helping then go to the director. If the director doesn't help then you should reassess your future in the company. Note that I'm not saying quit, because sometimes, especially when just starting out, you have to work a less than ideal job to build up some experience. As long as you're still learning and growing you can benefit from it, but the second you feel like you're stagnating and you're sure it's not you it's them, then leave. Next time you will have something to discuss at the interview too about what kind of place you want to work at.