Developer Diplomacy Gone Wrong. How Software Devs Are Demeaned

And How To Avoid This!

Effective communication seems to be something that gets ignored in a world where “radical honesty” seems an appropriate communication style across tech companies.

Some well-worn phrases used in tech can demean or undermine the efforts of a development team.

What are those common linguistic pitfalls, and how might they be avoided?

The issue: Using “actually” undermines expertise as it emphasizes that it is surprising. It’s a small intellectual leap to attach this surprise to the person who said it, therefore you’re surprised that a particular developer made a good point.

You should say: “That’s a great insight!”. This acknowledges the developer’s idea without undermining their expertise.

This offers a suggestion without making it seem like the task is trivial. Just is a diminishing word; its use diminishes a developer’s effort.

You should say: “Could you try implementing this approach?”

The issue: “Front End resource” or “Back End resource” might be a team of people. When you reduce them to a resource they are unlikely to give their all to the work you need them to complete. Worse, they may leave your company over time.

You should say: “Prem can you help me with this”.

Rather than reducing work to a simple deadline, show interest in it.

You should say: “How is the progress on this task?”

Related posts:

A factor not everyone considers about the humble learning management system is that it happily plays well with others. In fact, there’s one other system it works very well with — and you’re probably…

We can work as hard as we want, dream as great as we want, accumulate as much as we want, and rearrange it all as often as we want, and at the end of the day the substance of our lives will still…

Life is a borrowed journey with an unknown destination. Cherish moments of joy and sorrow, treasure loved ones, and make every moment count.