3 ms·
Why do we even go into negative descriptions? Why don't we go thinking about people strengths and think how we create a team that is composed of people with di
by ozim 5y ago
Why do we even go into negative descriptions?
Why don't we go thinking about people strengths and think how we create a team that is composed of people with different strengths?
Manager will have to make sure he makes it clear in the team that:
Joe might not be whipping perfect code but he is good at figuring out users vague requests and putting those into action.
Jane might be obsessed with her language of choice and does not like vague requirements, she likes something like we are having 20 requests per second make system to handle 50.
You don't want to describe people as "bad in something" because that is not productive. For a manager that should be obvious.
But even if someone is working in a team, describing colleagues/projects/workplace in negative ways is bad and not productive. While yes there are instances where it is bad and people should call bad things out, but most of what I see are mere annoyances that one can gloss over.
- kqr 5y agoFor the same reason I talk about security weaknesses, and not security strengths: pointing out a weakness is the first step to fixing them. Even if you have no interest in fixing a weakness, it is absolutely essential that you're aware of it, and can engage in compensating behaviour.
- ozim 5y agoWhat I see in "software engineer who is bad at business" is that is broad and not useful. We can discuss specific flaws with specific person and think about course of action to fix it. Telling someone "you suck" is not first step to fixing anything. Just like laughing someones system has so many holes as Swiss cheese. You want to be specific like you have an XSS here and here, those are steps to fix it.
- nickm12 5y agoAgreed. I don't think everyone can be great at everything. There are some basic levels of competencies that are required though and, most importantly, people need to be able to respect the strengths of others that don't align with their own. My own examples were driven by working with developers who were actively disdainful for people and ideas that were not on their single axis of focus, which was bad for the team and for the product.