You don’t need long hours to be a TOP software engineer. Make technology your ally, not your enemy

The page argues that software engineering is knowledge work, so the 40-hour workweek fits it poorly. It says productivity should be measured by output, not by hours at a desk, and points to shorter workweeks in Europe as evidence that less time can still support efficient work and balance.

It also says deep work is the main driver of high-impact output. The author recommends 60 to 90 minute focus sessions, fewer distractions, and time for recovery. AI and automation are presented as tools that can take over low-value tasks so engineers can reserve more time for critical thinking, walks, naps, and hobbies.

Reading notes

#

• The 40-hour workweek was built for factory labor during the Industrial Revolution, not for software engineering.
• Countries such as France and Denmark have shorter workweeks, and Spain has proposed a 37.5-hour week by 2025.
• Software engineers should be measured by the output they produce, not by the hours they are present.
• Deep work is described as allowing only 4 to 5 hours of focused, high-impact work per day.
• Focus sessions of 60 to 90 minutes are presented as more effective than longer stretches, because attention drops after that.
• Shallow work takes up too much time and reduces the space for high-impact tasks.
• AI can automate administrative work and routine tasks like looking up framework docs, formatting JSON, and writing code for machine execution.
• Using AI helps create time for recovery and personal activities such as walks, naps, and hobbies.