10x engineer: 10% of the time

The post looks for patterns behind perceived productivity in software engineering and treats productivity as hard to measure directly. It argues that the workflow side of the craft can be improved through practice, especially by focusing on debugging, avoiding blocks, deciding when to automate, and reading code well.

Reading notes

#

• Good debugging skill is presented as something that pays off throughout a software engineer’s career, and the author says it should be a top priority for newcomers.
• The post argues that engineers should keep another task ready whenever the current one is blocked, since waiting on other people or releases is common in software work.
• It says choosing between manual work and building a tool is a major sign of seniority, and that engineers often misjudge the cost of tooling in both directions.
• The author notes that many engineers do too much manual work when a small tool would save time, but that over-automating can also create maintenance burden.
• Reading code is described as more important than it is often treated, partly because documentation is usually bad and engineers need to work independently of it.
• The author says code reading improves when one tries to understand the original author’s approach and patterns from the code itself.
• The post frames programming as a craft that improves with practice and says this piece focuses only on workflow, not on coding or software design.