In reality... Kara moves the goalposts, declares the icon a success, and implements more useless icons. Your objections are categorized as "crying wolf". Kara gets a promotion, you get managed out, company slowly bleeds cash while everyone rearranges icons.
Don't Get Your Coworker to Agree with You
11–20 of 112 posts
Re: Don't Get Your Coworker to Agree with You
#12The flaw here is that you assume that "Kara" will learn from her mistakes. Not always the case. Especially in "creative" personality types. Find a creative, rational person if you can.
At the end of the day, the question to ask is: who is responsible for the product? If the product owner/boss/ceo is okay with it, who are you to question it?
What I do is try to talk through the pros/cons of what the other person wants to do. I will try to challenge what they’re doing with data and/or ask them to show me their data. I am open to being wrong at any point in time (ie try not to come across as judgmental or saying it’s a bad thing). Also, if you’ve seen the same thing in the past, walk through what happened and what you think the worst case scenario is.
If your colleague is insecure/anti-social/not interested in learning, you don’t want to work w/ them. I’ve had my share of ‘cowboy’ coders that were ‘moving fast and breaking things’. That’s not sustainable. You need to try to do something about it and not just hopw they will learn their lesson. Huge difference between lack of experience and sloppiness.
Re: Don't Get Your Coworker to Agree with You
#13Edit: That being said, there are definitely tactful ways to deliver a code review. I also don't believe you can have a successful software team with individuals who can't give a code review respectfully.
Re: Don't Get Your Coworker to Agree with You
#14I went through this phase with a difficult coworker over code, would take code reviews personally, developed long running branches in an ivory tower with no input or discussion. Learned to let go and he has his parts of the code base and I have mine. Not ideal, but worked as we were a 2 man dev team at the time. Then he left and we grew the team. Now we got a few minefields left in the code base that anytime we need…
Got rid of the co-worker much earlier on, by the sounds of it.
Re: Don't Get Your Coworker to Agree with You
#15Re: Don't Get Your Coworker to Agree with You
#16Re: Don't Get Your Coworker to Agree with You
#17Re: Don't Get Your Coworker to Agree with You
#18I never understood this logic. How is Kara being offended a smart and socially conscious decision? A better way to handle criticism is to ask for people's opinions and not get defensive.
After reading couple of negotiation and similar articles, I started to try and reason with people with carefully crafted questions to guide them towards my goal. But the end result always is that once people realize what I am trying to do, have them remove an icon, they get defensive irrespective. And then argument ensues.
The only way I found around this was to build trust. And it takes time, you cannot arrive at a company and start a discussion with Kara. Small talk about family etc helps build some trust. Or if systems fails and resolving it without shaming the original developers helps too. This obviously is not perfect because the time you spend building trust, you are also acquiring issues. But it helps in long run.
Re: Don't Get Your Coworker to Agree with You
#19Shit quality will be shit quality. If you really know shit has been done, you need to say so. Not communicating it will just keep the shit flowing. Have some pride in your work!