Keep a glossary. Everyones needs to be speaking the same language. Make sure everybody is using one name for specific features, patterns, ideas, etc. Reducing conceptual debt is crucial.
Capture the "whys" of all major decisions. It is much easier to pick up where someone left off if you understand the rationale behind the decisions they have made. It let's you reframe the problem from their perspective and inhibits new folks from bikeshedding or exploring already-solved problems.
Create tickets for everything, with explicit "Definitions of Done." I always try to create tickets for every task - partially because I'm forgetful, but mostly because it creates visibility and accountability. Don't define how something should be done step-by-step, instead detail exactly what the expected outputs are, with zero ambiguity. It takes time and care to create the tickets, but you make up for it by removing confusion and ambiguity.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A few tactics:
Keep a glossary. Everyones needs to be speaking the same language. Make sure everybody is using one name for specific features, patterns, ideas, etc. Reducing conceptual debt is crucial.
Capture the "whys" of all major decisions. It is much easier to pick up where someone left off if you understand the rationale behind the decisions they have made. It let's you reframe the problem from their perspective and inhibits new folks from bikeshedding or exploring already-solved problems.
Create tickets for everything, with explicit "Definitions of Done." I always try to create tickets for every task - partially because I'm forgetful, but mostly because it creates visibility and accountability. Don't define how something should be done step-by-step, instead detail exactly what the expected outputs are, with zero ambiguity. It takes time and care to create the tickets, but you make up for it by removing confusion and ambiguity.