Coding Workflow Best Practices
Code Review Approach
- •Understand before changing: Read the code thoroughly before suggesting modifications
- •Check for patterns: Look for existing patterns in the codebase and follow them
- •Consider edge cases: Think about null, empty, boundary conditions
- •Security awareness: Watch for injection, XSS, improper auth patterns
Debugging Strategy
- •Reproduce first: Confirm the issue before attempting fixes
- •Isolate the problem: Narrow down to the smallest reproducible case
- •Read error messages carefully: They often contain the solution
- •Check recent changes: What changed since it last worked?
- •Verify assumptions: Test each assumption individually
Refactoring Guidelines
- •Tests first: Ensure tests exist before refactoring
- •Small steps: Make incremental changes, verify each step
- •One thing at a time: Don't mix refactoring with feature changes
- •Preserve behavior: Refactoring should not change functionality
Common Pitfalls
- •Fixing symptoms instead of root causes
- •Over-engineering simple solutions
- •Ignoring existing patterns in the codebase
- •Making changes without understanding context
- •Skipping validation of user inputs at boundaries
Accumulated Learnings
See learnings.md for session-learned insights that supplement these guidelines.