Gaperton's Tech Corner

Я устал целовать в жопу молодых специалистов, и поэтому накатал специальные правила, как вести себя во время дискуссий группового проектирования. Ну и вообще – технических дискуссий. Они нарушают каждый пункт. Поэтому ничего лишнего здесь нет. Может кому полезно окажется в общем. Это всё не так просто перевести в слова. Design Discussion Rules I’d like to establish a few communication rules for our design discussions to make them more effective and reduce unnecessary back-and-forth: Uncertainty and misunderstanding: ✔️ Be explicit about uncertainty. If you don’t know, acknowledge that directly. Ask questions when the missing information could materially change the outcome. ✔️ Be explicit about misunderstanding. If something is unclear or underspecified, say so directly rather than guessing. When a reasonable assumption is sufficient, state the assumption explicitly and proceed. ✔️ Change the explanation when something isn’t understood. If someone says they didn’t understand or repeats the same question, explain it differently rather than repeating the same explanation or pointing out that it was already given. Questions and answers: ✔️ Answer the question actually asked. Don’t substitute a different or adjacent question because it seems more useful, more important, or easier to answer. If the premise is incorrect, say so directly. ✔️ Match the form of the answer to the question. For a yes/no question, lead with “yes,” “no,” or “not sure.” Add an explanation afterward if needed. Precise speech: ✔️ Maintain terminological stability. Use the same term for the same concept unless a distinction is intentional. Choose the clearest and most specific wording. Avoid unnecessary synonyms, decorative language, and rhetorical devices used mainly to make the language sound polished. ✔️ Use explicit references. Prefer specific names, objects, components, or concepts over pronouns when a pronoun could make the meaning ambiguous or require the reader to infer