3 ms·
What "authority"? Different people have different roles. If I know tons about implementing caches, I probably end up making most of the decisions about that so
by RogerL 13y ago
What "authority"?
Different people have different roles. If I know tons about implementing caches, I probably end up making most of the decisions about that sort of thing. If you know a lot about scheduling projects, probably you'll end up doing a lot of that. A junior person probably won't get to make a lot of decisions, except in whatever rather small area they are contributing in. And so on. Management doesn't mean you are an authority, it just means you have different responsibilities (and I manage as well as develop, I don't write this solely as a developer).
We can all come up with counterexamples to the above. What if someone is not pulling their weight? What if a group decides to drink (heavily) at the job? And so on. Sure, at some point somebody needs to make decisions about hire/fire/probation, and so on, but the hope and desire is to build a team that self directs itself in as much as that is possible.
I don't know, the whole 'authority' thing comes off as weird to me.
- ansgri 13y agoMaybe there's some linguistic problem (English being not my native), but I wrote about the power of making decisions, of telling you what to do and what not to. It really isn't applicable to junior positions, but if you're one of the most senior developers on a project, you might well doubt the competence of the project manager to make tech-related decisions. Micromanagement aside, you and PM may have serious disagreements on what technology stack to move to or buy-vs-build decisions.