How to Be Lazy and Stay Calm

The post says that in software development, especially with unfamiliar legacy code, the developer should not try to understand everything before acting. The suggested approach is to stay lazy, keep calm, and focus on the paid task rather than on improving the project without pay.

Reading notes

#

• When a bug is hard to understand, the author says not to blame yourself, because the project does not expect you to be an expert in its code.
• If the code base is messy or unclear, you should blame the code base itself by opening tickets about missing documentation, unclear classes, complex methods, or unclear rules.
• The author warns against using tickets to ask for explanations or help, because the project is not a school and should fix the code instead.
• After reporting the problem, you wait for the tickets to be resolved, and if they return to you, the scope of work changes into documentation or refactoring.
• The post lists five obstacles to this approach: shame, perfectionism, lack of passion, fear, and lack of time.
• Software development is described as a good place for cutting corners, being lazy, and staying calm because the work is often discrete and incremental.