Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
I've realized that giving feedback to others has traditionally been a weakness for me, because I was too afraid of offending other people. I see a lot of people in consulting who are afraid to rock the boat...they will come into a project and instantly start nodding along to whatever the client says and praising their organizational processes. It's really easy; everyone likes to be praised and you can get through an engagement without solving anything significant.
In the long-term, it's an awful strategy. If a company has a terrible business model or development practices that don't scale, they need to know ASAP. These things can be said with tact, but that still doesn't guarantee that they will be received well. I'd rather have someone be pissed off at me than worry about whether it is partially my fault when their business collapses two years later.
The opposite also applies: when someone else criticizes me, even if they do so rudely, it could be the piece of guidance that saves me from making a major mistake.
Thank you for your comment! 🙏
Because of the listed reasons above it's important to provide constructive feedback with explanations and an action plan on how to solve occurring problems.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've realized that giving feedback to others has traditionally been a weakness for me, because I was too afraid of offending other people. I see a lot of people in consulting who are afraid to rock the boat...they will come into a project and instantly start nodding along to whatever the client says and praising their organizational processes. It's really easy; everyone likes to be praised and you can get through an engagement without solving anything significant.
In the long-term, it's an awful strategy. If a company has a terrible business model or development practices that don't scale, they need to know ASAP. These things can be said with tact, but that still doesn't guarantee that they will be received well. I'd rather have someone be pissed off at me than worry about whether it is partially my fault when their business collapses two years later.
The opposite also applies: when someone else criticizes me, even if they do so rudely, it could be the piece of guidance that saves me from making a major mistake.
Thank you for your comment! 🙏
Because of the listed reasons above it's important to provide constructive feedback with explanations and an action plan on how to solve occurring problems.