The Thirty Minute Rule

The article argues that the Thirty Minute Rule should be used for coding and related work. If someone is stuck for more than 30 minutes, they should ask for help. The author says this can uncover missing knowledge, reduce frustration, sometimes help the person solve the problem by phrasing the question, and lower business costs by avoiding long delays.

Reading notes

#

• If a person is stuck for more than 30 minutes, they should ask for help.
• Being stuck often means there is something they do not know.
• Asking for help can prevent long frustration.
• Formulating the question can sometimes lead to the answer.
• From a business view, it can reduce costs by avoiding hours, days, or weeks of delay.
• Help can come from co-workers, collaborators, forums, groups, or social media.
• The original use case mentioned is Stack Overflow.
• If no one can answer, the problem is genuinely hard.
• The author says people cannot always figure things out on their own.
• One example given is a deployment packaging problem that depended on details written in a system administrator’s notebook, not the group wiki.
• The author argues for compassion and says people should not be made to repeat the same frustration others experienced.
• If someone asks a question and the answer is unknown, they should be told that politely and directed to others or online help.
• If someone is too busy to answer, they should redirect the person or suggest a better time.