noydb Goto Github PK

1. STAGNATION IS THE MIGHTIEST FOE
2. DO IT YOURSELF; WRITE CODE FROM SCRATCH WHERE POSSIBLE
3. THE MOST CRITICAL TOOL IS A MIND WELL EDUCATED IN DESIGN PRINCIPLES
4. THE ABILITY TO DISCOVER IS CARDINAL
5. ALWAYS BE THE WORST GUY IN EVERY BAND THAT YOU’RE IN
6. AVOID TEMPORARY FIXES BECOMING PERMANENT
7. OPTIMIZATION WITHOUT FIRST MEASURING IS ALMOST ALWAYS PREMATURE
8. WHAT IS RIGHT IS NOT ALWAYS POPULAR AND WHAT IS POPULAR IS NOT ALWAYS RIGHT
9. CONSISTENCY IS A REFUGE FOR THE PEOPLE WHO MUST READ MY CODE LATER ON
10. LEAVE THE CAMP SITE BETTER THAN YOU FOUND IT
11. LIMIT USE & CUSTOMIZATION OF THIRD-PARTY TOOLS/FRAMEWORKS/LIBRARIES (TO AVOID SUPPORT AND SECURITY ISSUES).

1. Encapsulation
2. Separation of Concerns
3. Single Responsibility
4. Modularity. High Cohesion. Low Coupling
5. Interface Segregation
6. Name as short as possible but as long as necessary
7. YAGNI/KISS/Gall's Law
8. Tests must replicate how the software is used
9. Principle of Least Astonishment
10. DOCUMENTATION DOCUMENTATION DOCUMENTATION

1. Principle of Least Privilege
2. Secure Defaults
3. Defense in Depth
4. Fail-Secure
5. Input Validation

1. Empathy Mapping (think, feel, see, hear, say, and do)
2. Walk A Mile
3. Minimalism; any visible element must have a purpose
4. Clear, Informative Communication
5. Visual Hierarchy
6. Accessibility
7. Emotion
8. Flexibility (Customisability) & Efficiency (Shortcuts)
9. Quick & Inexpensive Prototyping For Testing
10. Constant User Testing & feedback

“I'm not a great programmer; I'm just a good programmer with great habits.”