2 ms·
I push the new guys to fix project documentation once they’ve figured out a tricky bit. It helps solidify their knowledge, and helps us double check that they u
by hinkley 2y ago
I push the new guys to fix project documentation once they’ve figured out a tricky bit. It helps solidify their knowledge, and helps us double check that they understood, and it’s something they can contribute when they still haven’t become part of the bus number on anything yet.
That all sounds reasonable and smart, but the real reason I do it is the Curse of Knowledge. People in a system can’t see it from the outside. They make assumptions, use opaque or even misleading jargon, and employ circular logic. The new guy doesn’t know the lingo, or the circular logic. Their explanation will make more sense to the next hire than anything I can say. And having it written down this way can also give me new perspective on the system. Maybe it doesn’t have to work this way.
- zoogeny 2y agoAdding a new smart person to the team is one of those golden moments for a team, IMO. You get a tiny window of watching them struggle until the tribal team knowledge seeps into them by osmosis. During that time they don't yet know who to ask the questions to directly so they will post to team slack channels or the lead directly. One must capitalize on this brief period because smart programmers are flexible and adaptable. Very quickly they will acclimatize themselves to the mess that surrounds them and they will become as blind to the deficiencies as the rest of the team.
- hinkley 2y agoAdjacent to this: ignore criticism as feedback, but treat questions as feedback. People who don’t “get” the code ask questions that contain feedback they often don’t even register as feedback. By the time they distill it to an actual criticism, they’re often so wrapped up in the problem they can’t be constructive, or they present an XY problem. But if three people ask you the same question about your code? You have a design issue. Fix it. Fix it now. That puts me in a weird relationship with FAQs. FAQs aren’t informational, they’re confessional. Here’s all the times I fucked up and won’t admit it. Let me explain why I am right and you are wrong.
- maerF0x0 2y agoFunny enough, many organizations will actually punish questions due to optics, noise, or RTFM (which fair enough do read it, but also don't presume the asker didn't just because you understand what you wrote. Being written down doesn't mean it's understandable by a new reader, or that it's optimally setup for discovery)
- specialist 2y agoNice. Somewhere I picked up the phrase "problem of assumed knowledge" for the phenomenon you describe. But your phrase is spot on, well defined, and the subject of ongoing research. https://en.wikipedia.org/wiki/Curse_of_knowledge https://en.wikipedia.org/wiki/Curse_of_knowledge Cheers.