What is your philosophy and framework for conducting constructive, high-velocity code reviews?

In Simple Words: Code reviews are a teaching and alignment mechanism, not a gatekeeping hurdle. Keep Pull Requests small (<400 lines), automate style checks via linters/CI, and distinguish blocking architectural defects from non-blocking stylistic suggestions.

Best Practice Framework:

1. Automate the Mundane: Never debate code formatting, import order, or indentation in PR reviews; enforce these via Prettier, ESLint, and Husky pre-commit hooks.
2. Review in Layers: Focus first on architecture, data models, concurrency, and security. Then check error handling and edge cases.
3. Prefix Feedback with Intent: Use prefixes like blocking:, suggestion:, question:, and nit:.
4. Fast Turnaround SLA: Aim to review team PRs within 4 business hours to maintain delivery flow.

Practical Script & Summary Template

### PR Review Checklist & Intent Taxonomy:
- **[BLOCKING]**: "blocking: This query is unindexed and will cause a sequential scan across 10M rows in production."
- **[SUGGESTION]**: "suggestion: We could use Array.prototype.reduce() here to avoid creating intermediate arrays."
- **[QUESTION]**: "question: What happens if the external payment webhook returns a 504 timeout?"
- **[NIT]**: "nit: Typo in variable name 'recievedData' -> 'receivedData' (non-blocking)."
- **[PRAISE]**: "praise: Excellent test coverage for the concurrent race condition edge case!"