Rob Pike’s Rules of Programming (1989) (users.ece.utexas.edu)

Article summary

The article discusses Rob Pike's rules of programming from 1989, but the content is not available. However, the comments reveal a discussion on the importance of data structures and relationships in programming. Good programmers focus on data structures, while bad programmers worry about code. The discussion also touches on the idea of avoiding hasty abstractions and the need for a consistent coding style.

Main themes

• data structures
• coding style
• abstractions
• code review
• collaboration
• productivity

What commenters say

• Good programmers should focus on data structures and relationships rather than code.
• Avoiding hasty abstractions is crucial for writing good code.
• A consistent coding style is essential for efficient collaboration and code review.
• Automated linting tools can help eliminate style-related discussions and improve productivity.
• Enforcing a consistent style with automated tools can be beneficial, but may have downsides for large-scale refactoring.
• The value of consistency in coding style is marginal unless many people need to read or modify the code.
• Style discussions in code reviews indicate a failure to automate style checks.
• Automated style checks can reduce frustration and improve the code review process, but may not be practical for all projects.