2 ms·
There's a lot wrong with this situation. Without knowing the person involved it's hard to say if they have an attitude problem, but it sounds like the team lead
by phkahler 9y ago
There's a lot wrong with this situation. Without knowing the person involved it's hard to say if they have an attitude problem, but it sounds like the team lead does.
>>Who is right? No one is right, but the lead has the authority to expect tasks to be accomplished when asked and has the responsibility of delivering the release on time.
There is something wrong when one has to defer to their authority to get things done. In this case it's even stated that there is no correct answer, so why does the lead need to have it their way?
There's also the small problem of what was asked. It's hard for me to believe that adding a private variable is actually implementing a product feature. This smells badly of telling someone HOW to do their job rather than WHAT you want.
And finally there is context. Sometimes when it comes to time pressure a phrase comes to mind "a lack of planning on your part does not constitute an emergency on my part." It would obviously be stupid to say that, but in some cases it's the right attitude to have. It's not at all clear from this piece what the overall context is, what the actual feature is, or which person is being unreasonable.
I'm actually leaning toward the author as the problem. This need to blog about a petty dispute over a variable declaration suggests that maybe the person not obeying orders could be pushing back against a larger problem.
TL;DR there's really not enough here to tell who the problem is, or if there is really much of a problem at all.
- deleted 9y ago[deleted]