[ambicapter]

The trouble isn't that they would convince me with their reality distortion (they don't), the issue is that they are satisfied with their "progress" while I'm still asking crucial questions (which they ignore, b/c they don't see the importance).

[kube-system]

Part of the soft skills that are useful for a developer is being able to frame your crucial questions in a way that makes their importance relevant to their world.

[hypeatei]

Perhaps soft skills are too squishy and/or broad of a term to be useful then. It seems like these discussions always go "maybe you, as the developer, just need to learn how to do soft skills properly?" in response to business types exhibiting an undesirable behavior. Sure, smooth talking and playing into someones personality might be more successful (albeit with a lot more hot air), but all of you are supposed to be working towards a goal. If someone gets hung up because you weren't smooth enough, I would think they're a bad faith actor who doesn't actually want to get something done.

[kube-system]

Soft skills are broad in scope, for sure.

But I’m not talking about “smooth talking” here; in response to the above example —- where engineering is asking questions that that the business things had not answered because they are presumably “unimportant” —- there is almost certainly a communication breakdown happening.

Likely, one of the following is happening:

* The questions are important to the business but engineering has failed to articulate why getting the answers are critical to the business. (Some engineers have a tendency to describe problems in the scope of how it affects their own job or task, but neglect the larger picture or fail to articulate any consequences)

* The questions actually aren’t important for the business to answer and the engineer fails to understand how their task supports the goals of the business

* The questions are important but they cannot be answered by the business. The engineer might need to gather more information before to generate actionable questions, or maybe the questions should be answered by engineering themselves.

[marcosdumay]

Remember, technical workers, you must grind all you soft skills in addition to the technical ones, so that you can successfully interact with those people hired exclusively to use their soft skills.

[kube-system]

Engineers just need to have good enough soft skills to effectively communicate.

Engineers who struggle to do that are just as bad at their job as business managers who aren’t technical enough to operate Microsoft Office. There’s a minimum of both hard and soft skills that anyone in a professional environment should have.

[lolive]

Bizness needs to understand that scalable reliable durable solutions take time to craft properly. https://www.youtube.com/watch?v=x9wn633vl_c

[kube-system]

Engineers need to understand that those requirements don’t apply to every project.

https://res.cloudinary.com/monday-blogs/w_1000,h_561,c_fit/f...

[lolive]

How does an engineer know that he is involved in a bozo-driven PoC or in a technical deathtrap that will end up as the core business of the company?