4 ms·
The problem with 20 minute rule, is that there is just so, so much arcane knowledge embedded into systems we really should not make everyone spend 20 minutes or
by jariel 6y ago
The problem with 20 minute rule, is that there is just so, so much arcane knowledge embedded into systems we really should not make everyone spend 20 minutes or more each time.
So many little things especially - it's the job of the people holding the knowledge to spread it so they can be unencumbered by it.
I never want my jdevs flailing around wondering why this or that was done, re-inventing things we've already done, going down rabbit holes we've already been down.
Batch them and ask.
Other devs have to get with the fact it's part of the job there's just now way around it.
Figure out a way to socialize it ie open hours, or extensive training etc. - or even - better documentation.
- CGamesPlay 6y agoTo add to your comment, when you do get a question that the junior dev has been sitting on, it's a good indication for you that this area of the system needs better documentation. If following the 20 minute rule, when you do get a question, it might be worth spending 20 minutes to answer it (and provide appropriate background) as well.