| >People with bad communication skills often think they are communicating big estimate, while no one else in the room got it from what they said. I've literally never had this happen once during a planning meeting. >Nope, showing the code is not enough to explain to other developers It's always worked for me. I can read code, grasp the structure and spot code smells with a glance. If it's really bad I'll be able to tell. Usually I will just trust the people I work with if they say "it's bad" though. >And PM IS interested, good one that is. Good PMs learn to stay out of technical issues and trust their developers just as good developers learn not to second guess their PMs. >Have you even consider entry that PM can react to reasons why something take long Uh, was that English? >On your last point - given that developers with bad communication skills ask badly phrased questions or don't ask anything at all (just generically complain about bad analysis and insult pm - true story), yep it matters. As I said before I've worked with several developers who rarely ask questions and just do the work (and do it well). All stellar developers and highly underrated. >You jumped from "bad social skills" to "average" there. We were always arguing about whether it was a priority for developers to have especially good (or even above average) soft skills, not whether it was ok to work with developers with cripplingly bad communication problems. |