The peril of laziness lost (bcantrill.dtrace.org)

Article summary

The article discusses the concept of laziness as a virtue in programming, as described by Larry Wall in his book Programming Perl. It argues that true laziness in programming leads to simplicity and abstraction, making software easier to write and maintain. However, the rise of Large Language Models (LLMs) and the emphasis on productivity have led to a false sense of industriousness, prioritizing quantity over quality. This shift is exemplified by the story of Garry Tan, who bragged about writing 37,000 lines of code per day using an LLM.

Main themes

• programming virtues
• LLMs and productivity
• code quality and maintainability
• abstraction and simplicity
• software development values
• business interests and motivations

What commenters say

• Some commenters agree that writing code twice before abstracting is a good practice, as it helps to ensure that the abstraction is necessary and well-designed.
• Others argue that this approach can lead to unnecessary complexity and that it's better to abstract sooner rather than later.
• The use of LLMs is seen as a threat to the traditional values of programming, such as simplicity and elegance, and as a potential source of low-quality code.
• A few commenters point out that the value of code should be judged on its usefulness and maintainability, rather than on the number of lines written or the speed at which it was produced.
• Some argue that the emphasis on productivity and lines of code written is driven by business interests and the desire to impress, rather than by a genuine desire to create good software.
• There is a debate about the role of LLMs in software development, with some seeing them as a useful tool and others as a potential hindrance to good programming practices.
• The importance of considering the long-term costs and consequences of software development, including maintenance and security, is also highlighted in the discussion.