java-coding-standards

Coding standards for readable, maintainable Java 17+ in Spring Boot services. Standards for readable, maintainable Java (17+) code in Spring Boot services. Remember : Keep code intentional, typed, and observable. Optimize for maintainability over micro-optimizations unless proven necessary. - Covers naming conventions (PascalCase for classes, camelCase for methods, UPPER_SNAKE_CASE for constants), immutability patterns with records and final fields, and Optional usage with map/flatMap - Establishes best practices for streams, exception handling with domain-specific exceptions, and type-safe generics - Includes project structure guidance (Maven/Gradle layout), formatting rules, and code smells to avoid (long parameter lists, deep nesting, static mutable state) - Recommends null handling with annotations, logging patterns, and testing expectations (JUnit 5, AssertJ, Mockito) - Writing or reviewing Java code in Spring Boot projects - Enforcing naming, immutability, or exception handling conventions - Working with records, sealed classes, or pattern matching (Java 17+) - Reviewing use of Optional, streams, or generics - Structuring packages and project layout - Prefer clarity over cleverness - Immutable by default; minimize shared mutable state - Fail fast with meaningful exceptions - Consistent naming and package structure - Use unchecked exceptions for domain errors; wrap...