The documentation bit is interesting because often, as with code, an improvement to documentation means making it shorter. Or spending hours understanding all the contingencies and edge cases enough to feel comfortable directing users to do a single thing.
I'm a software developer based in Newcastle Upon Tyne, England. I've got a wide range of experience in companies of varying sizes and cultures, and in roles of varying degrees of responsibility.
Yeah, I understand where you're coming from. Our situation though is that we're a team with remote workers (one of whom is myself!), and a lot of domain-specific stuff that should have been documented wasn't.
Something I'm pretty keen on is thinking about things from the perspective of someone on their first day, and this thought process re: "just" has really helped highlight things that could and should be documented, but weren't.
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.
The documentation bit is interesting because often, as with code, an improvement to documentation means making it shorter. Or spending hours understanding all the contingencies and edge cases enough to feel comfortable directing users to do a single thing.
Yeah, I understand where you're coming from. Our situation though is that we're a team with remote workers (one of whom is myself!), and a lot of domain-specific stuff that should have been documented wasn't.
Something I'm pretty keen on is thinking about things from the perspective of someone on their first day, and this thought process re: "just" has really helped highlight things that could and should be documented, but weren't.