Or let the Junior rewrite the docs while they're scratching their head, and push an update once they've figured it out.

Lalabadie 5 days ago | parent | next [-]

I'm a senior designer who often contributes to front-end code when it's convenient for my client.

Fixing and updating the README when I join a new team and set up their dev environment is always extremely well-received.

	▲	aDyslecticCrow 3 days ago \| parent [-]
		If i'm gonna untangle something, i may as-well write some notes. If i'm writing notes on it already, i may as-well refine the grammar a bit and update the docs. It's really quite small effort compared to the main work of learning the system, so i don't quite get why so few people do it.

▲

efitz 5 days ago | parent | prev [-]

Wow, way to double down on “I really hate everyone who doesn’t have exactly my skill set and experience.”

▲

aDyslecticCrow 5 days ago | parent | next [-]

I'm ... confused what you mean. If the junior is gonna untangle the docs anyway, why not make them directly update the parts that confused them once they're through it.

	▲	efitz 2 days ago \| parent [-]
		I apologize; I misunderstood. I thought you were making a “fend for yourself” argument; I was not associating “junior devs on the team making the docs, need to fix docs or make good ones”.

▲

turtleyacht 4 days ago | parent | prev | next [-]

They're not necessarily prohibited from asking questions if they're stuck, though. But also search in the chat channels for similar issues.

Updating docs in source control also onboards folks to code review. It would be weird to update docs and get a hostile reception.

While nice to walk through with someone and conduct a usability study, just leave it better for the next person (who could be yourself, if you forget). That has happened before.

▲

trashymctrash 5 days ago | parent | prev [-]

I think you are misreading the parent comment here.