Уровень 0 · материалов: 7
Сюда входят документы о технических стандартах написания читаемого и поддерживаемого кода, но не входят документы об архитектурном проектировании систем или управлении проектами.
Общие признаки: принципы чистого кода, поддерживаемость программного обеспечения, стандарты именования и форматирования, снижение когнитивной нагрузки, профессиональная гигиена разработки
Группа выше: Чистый код и читаемость
Смысл: The main idea is that writing clean, readable, and structured code is a professional necessity that ensures software maintainability, scalability, and effective collaboration among developers.
A guide outlining eight essential coding standards—from naming conventions to architectural patterns—designed to make software readable, maintainable, and robust.
Смысл: The main idea is that writing readable, well-formatted code is a professional necessity because code is read far more often than it is written. By following standardized naming conventions and structural rules, developers can reduce errors and improve team productivity.
A guide to improving code maintainability through strict naming conventions and structural standards, largely based on the principles of 'Code Complete'.
Смысл: The main idea is that professional software development requires a disciplined approach to code cleanliness, where readability, simplicity, and the Single Responsibility Principle are prioritized to ensure the software remains maintainable and adaptable over time.
A detailed synthesis of 'Clean Code' principles focusing on naming, function brevity, the Single Responsibility Principle, and the belief that code should be as readable as well-written prose.
Смысл: The main idea is that code readability is a critical component of software quality, achieved through strict adherence to formatting, naming, and documentation standards to minimize the effort required for others to understand the logic.
Readable code is code that allows a developer to quickly grasp its purpose and logic without deep scrutiny through consistent naming, modularity, and purposeful documentation.
Смысл: The main idea is that software maintainability depends on code being easy to understand for humans, not on following rigid rules. Developers should strive for 'rational cleanliness' and pragmatism, ensuring that code is simple and self-explanatory to reduce long-term technical debt.
Focus on writing simple, readable code that others can easily maintain rather than obsessing over academic 'clean code' perfection.
Смысл: The main idea is that code quality is defined by its readability, which can be systematically improved by extracting logic into small, uniquely and descriptively named functions to lower cognitive load.
Improve code quality by extracting any logic that can be named into its own function, transforming 'how it works' into 'what it does'.
Смысл: The main idea is that professional software development requires a baseline of 'code hygiene' (removing dead code, avoiding duplication, and limiting function size) that transcends complex design patterns; ignoring these basics is an inexcusable failure of professionalism.
The author defines four 'criminal' code quality violations—commented-out code, dead code, copy-pasting, and oversized methods—that signify an unprofessional codebase regardless of the project's complexity.