Hacker News new | past | comments | ask | show | jobs | submit login

> Lead: I need you to implement “X”. > Teammate: No. > Lead: This is not a choice. I am telling you to do this. > Teammate: You need to convince me.

There will be times, even as a junior team member when you strongly disagree with a decision. I have always felt that there is a virtually unlimited supply of people out there who can implement what they're told to implement, but that if I wanted to justify the salary I wanted it was my obligation to share my expertise by pushing back against what I saw as bad architectural decisions.

Early in my career, this didn't work out so well for me :)

I think I've figured it out by this point. There is a balance to be struck between "you're the boss" and "I don't think this is the right path" - and that balance differs from person to person. There are some key factors that remain constant:

1. It's not personal. I'm careful not to imply that something is wrong with the person who made the decision, merely that I disagree with the decision. If it feels like egos are getting involved - including my own! - I drop it

2. Organizational structure exists for a reason. I'm very explicit in acknowledging that I will perform the task as given to the best of my abilities if that's what is asked of me.

3. Keep it private. Challenging your team lead in a meeting with a half-dozen other developers is a Bad Idea.

Basically, I don't think it's too much to ask that your leadership treat your professional opinions with respect. If you are working in an environment where the above seems impossible to you... you should change your environment.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: