3 ms·
> A good technologist has grace. He will respectfully probe for intent in a way that doesn’t put the requester on the defensive. He will make it clear that this
by Jensson 5y ago
> A good technologist has grace. He will respectfully probe for intent in a way that doesn’t put the requester on the defensive. He will make it clear that this is a partnership, and that getting the job done is high on his list of priorities — it’s just that he needs some information in order to do a good job for you.
Sounds like a very toxic environment. What would put the tech worker that much on their toes, what would happen if they stepped out of line? Would the manager get angry because it looks like the tech worker tries to be lazy? Do people get angry when you ask questions unless you make it absolutely sure those questions are to help solve their problem? I'd really hate to work in such an environment where tech workers needs to tip-toe around issues because people gets angry if you don't.
Maybe it would be easier if you focused on hiring managers with soft skills first instead of putting in so much effort hiring tech workers with much better soft skills than those managers?
- hluska 5y agoI see your point but I'll caution you that I don't think this cat has any experience building software, so his concept of how things flow is a little off. I'd completely ignore this entire paragraph and just focus on becoming an active listener and learning how to ask questions.
- wvenable 5y agoPeople are people and many don't understand or are actively afraid of technology. They have jobs to do and if they don't know you, they may be skeptical about what you can do for them. They might even have been burned in past by developers who promise but don't deliver. Knowing how to talk to people to get your project done is a great skill.
- Jensson 5y ago> Knowing how to talk to people to get your project done is a great skill. Right, so why would your company hire people who are so bad at talking to people that the developer has to go to such lengths to save that persons project? I wouldn't want to work there.
- wvenable 5y agoSo your argument is companies should hire people who good at communication so they can hire a developer who isn't?
- Jensson 5y agoMy argument is that you can meet them halfway rather than dumping all the responsibility on the developer like this guy does. But as a consultant I guess his job is to help toxic managers hire people they can work with, if that is the case he doesn't have a choice to change the manager.
- jrochkind1 5y agoWould you say your discussion style in this thread is "meeting halfway", and typical of your discussion style at work? What would you say characterizes a "toxic" discussion style, or "being so bad at talking to people"?
- Jensson 5y agoNo, I am much more aggressive online since I want to point holes in things. I doubt many people talk the same way online as they do at their job. It isn't like you expect a sales person to be all happy when he is at home. > What would you say characterizes a "toxic" discussion style, or "being so bad at talking to people"? People who can't talk normally due to some of the following reasons, if these are issues you have to deal with at your job instead of they dealing with it themselves then you work with people who lack social skills: > People are people and many don't understand or are actively afraid of technology. They have jobs to do and if they don't know you, they may be skeptical about what you can do for them. They might even have been burned in past by developers who promise but don't deliver.
- wvenable 5y agoYou have a strange idea of what talking normally is. Fears, concerns, having different priorities, working under their own deadlines, and so on are all normal for other people.
- yobbo 5y ago> People are people and many don't understand or are actively afraid of technology. One possible alternative is that people are suspicious/defensive (sometimes justifiably) when techies ask questions about "what problems are you having?" and "what do you typically do when ___?" To them, it might seem like they are being interrogated by someone ostensibly below their rank. To be fair, this is sometimes exactly what is happening. A techie is sent in to investigate automating a bullshit job, but neither the techie or the person is told this in clear terms.
- wvenable 5y agoAlso these people are the experts and often you're the novice in their domain. Understanding that part of the relationship is important. In my experience, people are very happy when I automate some bullshit part of their job. However, you are going to waste their time getting that automation done. So you have to sell them that it's worth making their job worse in the short term to make it better in the long time. If you're a terrible communicator, they're not going to trust that it's worth it.
- jrochkind1 5y agoEquating "He will respectfully probe for intent in a way that doesn’t put the requester on the defensive" with "tip-toeing around issues" seems... not right to me.
- Jensson 5y agoYou took out a part, why would a developer ever need to say this except to calm a toxic manager? > He will make it clear that this is a partnership, and that getting the job done is high on his list of priorities
- jrochkind1 5y agoWell, I think one reason a developer would need to make that clear, is so many people have so much experience working with developers like you who make the opposite clear, that they assume the worst.