Craftsmanship

Writing clean, readable, maintainable code. Practices distilled from Clean Code, The Pragmatic Programmer, and decades of industry experience.

Naming

• Meaningful Names - Choosing names that reveal intent

Functions

• Small Functions - Keeping functions focused and readable
• Single Responsibility - One reason to change

Principles

• DRY Principle - Don’t repeat yourself
• Don’t Repeat Yourself - The DRY principle in depth
• Boy Scout Rule - Leave code cleaner than you found it
• KISS Principle - Keep it simple, stupid
• YAGNI Principle - You aren’t gonna need it
• Composition Over Inheritance - Favor assembly over hierarchy

Code Quality

• Code Reviews - Systematic peer examination of source code
• Code Comments - Writing useful comments and documentation
• Code Inspection - Formal code examination techniques
• Code Metrics - Quantitative measures of code quality

Pragmatic Practices

• Design by Contract - Preconditions, postconditions, and invariants
• Pair Programming - Collaborative development practices

Related Resources

• Swift Conventions - Language-specific practices
• TypeScript Conventions - Language-specific practices
• TDD Workflow - Test-driven development approach

Sources

Primary references for this domain:

• Clean Code - Robert C. Martin
• The Pragmatic Programmer - Andrew Hunt & David Thomas
• Code Complete - Steve McConnell
• Refactoring - Martin Fowler