code quality
DESCRIPTION
TRANSCRIPT
SOFTWARE
DEFECTS(BUGS)
VIOLATIONS
DEFECTS VIOLATIONS
CODE QUALITY
CODE
COST
ENGINEERING
WORKING CODE
CLE
AN
CO
DE
CODENIRVANA
YOU
MS
ENGINEERIN
G EFF
ORT
RULE #1ALWAYS HAVE A
WORKING SYSTEM
RULE #2DO NOT ATTEMPT
TO FUTURE-PROOF
IMPROVINGCODE QUALITY
EXPERTISE
SOFTWAREPROCESS
REUSE
REFACTORING
VERSIONING
ANALYSIS
BUILDMANAGEMENT
ISSUETRACKING
SUMMARY
• Violations are not visible to stakeholders
• Violations have a greater effect on code quality
• Remove a defect/violation only if doing so costs less
• Over a longer timeframe, avoiding/removing violations dominates, resulting in higher code quality
• Over a shorter timeframe, avoiding/removing defects dominates, resulting in lower code quality
• The timeframe of a startup should be short
• Rule #1: Always have a working system
• Rule #2: Do not attempt to future-proof your code
• Use the development stack to improve code quality