Oct 29, 2023·edited Oct 29, 2023Liked by Jordan Cutler, Raviraj Achar
Sure! I would add one more suggestion to handling conversations with the “perfectionist”: Adding automated linting or static analysis on PRs to standardise best practices and leveraging CI to avoid not picking minor comments. As an iOS Developer, I automated SwiftFormat on every PR with pre-commit hooks and this greatly reduced the number of style comments (see https://www.codewithkasetti.com/posts/swiftformat_integration_automation/ for more details).
what an exceptional article! You both have done an incredible job covering all types of difficult coworkers and providing practical tips to navigate those situations. The depth of your insights is truly impressive. Thank you both for sharing your expertise in such a valuable way!
I think the approach of seeking first to understand is key. And this is the hardest part, at least for me: Finding the real motives behind the other person's actions. It's easy to see the actions, it's harder to dive into the next layer.
A curious question for both: As you work with more and more people, is it easier to identify patterns and cluster them together into these archetypes of developer? Or the idea that "everyone is unique" holds and it's hard to identify their motives?
Also, even if you know where they come from, it can be mentally demanding to keep up with the actions suggested.
This is a good question and perhaps a lot of people also have it.
It is hard to understand other people. So, I hear you! Though my approach is not to intentionally bucket them. The thing that works for me is - trying to understand the reasons that motivates someone to do what they do. This involves asking empathizing questions and openness to understand their point of view. As long as your actions are towards "solving the problem" you will build the muscle to do the "right" thing. It won't feel as demanding.
Having said that, you will find folks that are on the extreme end of the spectrum. It will be hard and feel tiring. However, once you come out of it successfully you will deal with future issues better.
How I do it? Over time, it has gotten easier for me to identify what folks are focusing and where they come from. (So, yes I can bucket their traits but I am not thinking about the buckets on a day to day basis). It is muscle memory for me to choose the best next step. Though for someone just starting, you need to be intentional and do the hardwork.
Definitely not an easy task, but I find relief into seeing that with engineers it's the same as with any human. It's all about showing empathy and interest. Simple concepts, but not easy to apply :)
And I totally agree about the end of the spectrum. I had some and in those situations you have to be super intentional with your words and actions, to the point I defined some affirmations on how I act in them and they become muscle memory later, I put a name to my way of acting.
This is outstanding content! Keep it up
Glad you liked it.
Sure! I would add one more suggestion to handling conversations with the “perfectionist”: Adding automated linting or static analysis on PRs to standardise best practices and leveraging CI to avoid not picking minor comments. As an iOS Developer, I automated SwiftFormat on every PR with pre-commit hooks and this greatly reduced the number of style comments (see https://www.codewithkasetti.com/posts/swiftformat_integration_automation/ for more details).
Great callout. Definitely agree there
Pure practical situations! For sure, I'll put on actions a lot of tips from this post.
Thank you, Rafael! Love this
This was a great essay, Jordan. Great work from both :)
Thank you, Sairam! Appreciate it a lot ❤️
Helpful in understanding the other side of difficult co-workers. Thank you Jordan and Reviraj!
Thank you, Amy. Totally agree and really appreciate that
Yea that mostly works. Thank you!
what an exceptional article! You both have done an incredible job covering all types of difficult coworkers and providing practical tips to navigate those situations. The depth of your insights is truly impressive. Thank you both for sharing your expertise in such a valuable way!
Thank you. Glad you found it helpful!
Thank you for such a kind compliment, Omsai. So glad you enjoyed it.
I know I learned a lot from the process of writing all this up as well. So I'm right with you
Loved the tip about sign-off checkboxes! Will definitely try it out :)
I think you covered any difficult intercation I ever had with those 7 types, great article!
Yea it’s a good forcing factor to get folks to think about their concerns.
So nice to hear that, Anton. Thanks, man. I appreciate it 🙏
This was good brain food!
I think the approach of seeking first to understand is key. And this is the hardest part, at least for me: Finding the real motives behind the other person's actions. It's easy to see the actions, it's harder to dive into the next layer.
A curious question for both: As you work with more and more people, is it easier to identify patterns and cluster them together into these archetypes of developer? Or the idea that "everyone is unique" holds and it's hard to identify their motives?
Also, even if you know where they come from, it can be mentally demanding to keep up with the actions suggested.
This is a good question and perhaps a lot of people also have it.
It is hard to understand other people. So, I hear you! Though my approach is not to intentionally bucket them. The thing that works for me is - trying to understand the reasons that motivates someone to do what they do. This involves asking empathizing questions and openness to understand their point of view. As long as your actions are towards "solving the problem" you will build the muscle to do the "right" thing. It won't feel as demanding.
Having said that, you will find folks that are on the extreme end of the spectrum. It will be hard and feel tiring. However, once you come out of it successfully you will deal with future issues better.
How I do it? Over time, it has gotten easier for me to identify what folks are focusing and where they come from. (So, yes I can bucket their traits but I am not thinking about the buckets on a day to day basis). It is muscle memory for me to choose the best next step. Though for someone just starting, you need to be intentional and do the hardwork.
Thanks for the thoughtful reply, Raviraj.
Definitely not an easy task, but I find relief into seeing that with engineers it's the same as with any human. It's all about showing empathy and interest. Simple concepts, but not easy to apply :)
And I totally agree about the end of the spectrum. I had some and in those situations you have to be super intentional with your words and actions, to the point I defined some affirmations on how I act in them and they become muscle memory later, I put a name to my way of acting.