18

My fellow dev (a younger guy) and I have been having a lot of disagreements with the lead dev (obviously a more experienced, older guy).
We can have arguments with him all day long, to explain and convince him that he's not that right, or not right at all.
Or we can keep silent and wait for shit to happen.
I'm already applying the stfu strategy myself... Because the other way round is exhausting.
At the same time, naturally, I'm looking for opportunities somewhere else. And, naturally, in those job ads, they state "X years of experience".
This further sets me off.
I'm sick of having an argument shut down because someone has X more years of experience, at a higher position, thinks he is better.
I am starting to hate people who boasts his years of experience instead of having the real knowledge and skills to create value.

Comments
  • 3
    I feel your pain. Just don't get frustrated. Keep on doing what you do best and hope things will work out for you.
  • 6
    I think you should being up disagreements each time but dont fight over it. Just get it out so that you are heard. As time goes on some one else will hear or he will realize. Not saying anything or fighting too much are both bad strategies imo.
  • 2
    @Santaclauze fully agree with you
  • 2
    Two things :
    * You'll meet people who think they are better than you everwhere you go. They'll have more experience or less and trust me on this, both are equally annoying. The ignorant shit unable to see he's wrong pisses me off just as much as the old fool stuck in his ways.
    * being able to explain why your solution is the best suited for the job is valuable, like @Santaclauze said, argue every time and practice.

    To sum it up, there's room to turn this unpleasant experience into an opportunity.
  • 5
    Also. Don't assume me you are necessarily right. Be open to being proven wrong too.
  • 6
    @Sekhat is correct here. If I had a couple of junior devs taking up large swathes of my time most days to moan and argue about everything we were doing, I'd have a rather short shrift too.

    You need to start picking your battles, and phrasing things in a "I think I'm misunderstanding, can you clarify" rather than "You're wrong and here's why". You may then have much more luck with productive conversations.
  • 0
    Sometimes it's really hard to say whose solution is right out better without trying them out. It's just frustrating out of my suggestion and his, he has the power to decide which way to go. And since we do not have the luxury to research, we pretty much only have time to have one go. That means my suggestion doesn't even get a chance to be proven better or worse. But hey, if our position swapped I'll probably do what he does. Except, I wouldn't say "I have experience before and it's the standard." Call me a noob. Every time this happens I feel like the "standard" is defined on the spot...
    Work being work, I have to implement his decision/design. Being told to do something I don't agree on feels bad. Does it go well or not at the end, I don't have any credit, nor responsibility... I can't get any motivation.
  • 3
    Statistically seen, juniors fuck up more often than not if left on their own, especially if they think they know how shit works. Dunning-Kruger effect, they know so little that they think they are experts.

    However, it just must suck to be a junior who actually has enough experience from a lot of side projects as to be the exception to the statistics - but still getting pushed over.
  • 1
    @Fast-Nop I may sound like I am full of myself but I did think about "what if I'm wrong". Just at the end I can't come to that conclusion lol
Add Comment