Guillermo Rauch Engineering Philosphy

From x.com: link

Copying here for Emphasis.

• Make it work, make it right, make it fast
• Progressive disclosure of complexity
• Minimize the number of concepts & modes
• Most ‘flukes’ aren’t… your tech just sucks
• Feedback must be given to users instantly
• Maximize user exposure hours
• Demo your software frequently to fresh eyes
• Sweat every word of product copy you render
• You’re never done working on performance
• You’re never done. Software ages like milk, not wine
• Visualizing traces of time is the best way to optimize it
• Ship frequently and strive to build in public
• Errors must have globally unique codes & hyperlinks
• Red is not enough to signal “error” (8% of men have red-green color blindness)

See also: Rob Pike’s Rules for Programming