Things to say when you're losing a technical argument (2001)

Re:Things to say when you're losing a technical argument (2001) by sitkack on Friday November 05, 2021 @02:33PM (#29123102)

I have seen google design docs at google, most are trash. Most design docs everywhere are trash. The confuse more than they explain. I don't care if the idea is good, if the design doc stinks, it will kill a good idea.

[ Parent | on HN ]

Re:Things to say when you're losing a technical argument (2001) by Ancapistani on Friday November 05, 2021 @03:15PM (#29123609)

Effectively communicating a complex idea is a skill that's orthogonal to coming up with good ideas.

I advise other engineers, especially those early in their careers, to actively develop and hone their communication skills. It deserves far more focus than most people seem to give it.

[ Parent | on HN ]

Re:Things to say when you're losing a technical argument (2001) by xpe on Friday November 05, 2021 @10:47PM (#29127072)

What are some of the key problems you've seen?

[ Parent | on HN ]

Re:Things to say when you're losing a technical argument (2001) by sitkack on Saturday November 13, 2021 @11:39AM (#29211039)

You can't _build_ anything from them. They talk around things, kinda layout the problem, talk nebulously about a way to solve it and then ... nothing.

The appear to be an artifact of a policy, the problem they solve is 'not having a design document' and nothing more.

[ Parent | on HN ]