Comment by grumpyprole
2 years ago
If it were only that simple. Often one needs to be at least a team lead to set the technical direction. As an IC, I sometimes found myself being asked to implement a solution in a form that I did not agree with.
2 years ago
If it were only that simple. Often one needs to be at least a team lead to set the technical direction. As an IC, I sometimes found myself being asked to implement a solution in a form that I did not agree with.
With the right team/leader, there'd be room for your inputs on the matter. Even if you find yourself in a not-so-good team setup, I'd argue there's still merit in letting your opinion be known, regardless of whether you end up implementing said solution in the way you were told or not.
You can only have that shot down so many times before you give up.
Very much this. And when people give up it can take one of two forms:
Either the person quits.
Or the person resigns to giving mediocre output and coasts.
Neither is good for the business and yet people keep pushing workers (not even just in tech) into that position to the point it's now a cliché.
I don't think that changes much. To oversimplify; by telling you how to do it, the team lead is taking responsibility for the outcome of your output. You are just responsible for doing it how they said.