best-practices - Concepts
Explore concepts tagged with "best-practices"
Total concepts: 34
Concepts
- Convention Over Configuration - A software design paradigm that reduces decisions developers need to make by providing sensible defaults based on conventions.
- Commit - A snapshot of changes in version control, representing a specific point in the project's history.
- 3-2-1 Backup Rule - A data protection strategy requiring three copies of data on two different media types, with one copy stored offsite.
- Clean Code - Code that is easy to understand, maintain, and modify, following principles of readability, simplicity, and expressiveness.
- Premature Optimization - The practice of trying to improve code performance before it's necessary, often at the expense of clarity and maintainability.
- Code Review - A quality assurance practice where one or more developers examine code written by a peer before it's merged into the codebase.
- Clean Architecture - A software architecture pattern that emphasizes separation of concerns through concentric layers with dependencies pointing inward.
- Design Patterns - Reusable solutions to commonly occurring problems in software design, providing templates for solving design challenges.
- PKM Anti-patterns - Common mistakes and pitfalls that prevent people from benefiting from personal knowledge management.
- Fault Tolerance - The ability of a system to continue operating correctly even when some of its components fail.
- Error Handling - The practice of anticipating, detecting, and responding to errors in software to maintain system stability and provide meaningful feedback.
- Silent Failure - When a system fails without providing any visible indication, making problems difficult to detect and debug.
- Don't Repeat Yourself (DRY) - The principle of avoiding information duplication.
- Defensive Programming - A coding practice that anticipates potential errors and edge cases, writing code that fails safely and provides clear error information.
- Characteristics of Good Notes - The key qualities that make notes valuable, findable, and useful over time, including atomicity, clarity, connectivity, and sufficient context.
- Personal Organization System Principles - Five key principles for building effective personal organization systems: safety, holistic design, life integration, simplicity, and agility.
- Golden Path - The optimal, recommended, and well-supported way to accomplish a task or achieve a goal.
- Documentation - The practice of creating written records and explanations of systems, code, processes, and decisions to preserve knowledge and context.
- Boy Scout Rule - Leave things better than you found them.
- Self-Documenting Code - Code written so clearly that it explains itself without requiring extensive external documentation.
- Graceful Degradation - A design approach where systems continue to function with reduced capability when components fail, rather than failing completely.
- Semantic Versioning - A versioning scheme using MAJOR.MINOR.PATCH numbers to communicate the nature and impact of changes in software releases.
- Pros and Cons of Tags - A balanced view of tag-based organization: the benefits of flexibility and cross-categorization versus the challenges of decision fatigue and recall.
- Refactoring - The process of restructuring existing code without changing its external behavior to improve readability, maintainability, and design.
- Note Naming Conventions - Consistent rules for naming notes that improve findability, scanning, and organization within a knowledge management system.
- Breaking Loudly - A software design principle where failures produce visible errors, exceptions, or warnings rather than silently continuing.
- Design Systems - A collection of reusable components, guidelines, and standards that enable teams to build consistent user interfaces at scale.
- Separation of Concerns - A design principle for dividing a system into distinct sections, each addressing a separate concern or responsibility.
- Architecture Decision Records - A systematic method for documenting architectural and technical decisions, their context, and rationale to preserve knowledge for future maintainers.
- Rebase - Reapplying commits on top of another base commit to create a linear history in version control.
- Key Principles of a Good Personal Organization System - Five essential principles for building an effective personal organization system: safety, holism, integration, simplicity, and agility.
- Personal Organization Roadmap - A step-by-step guide for building your personal organization system, from basic tools to a comprehensive LifeOS.
- Staging Area - An intermediate space in Git where you prepare and review changes before committing them to the repository.
- Code Smell - Surface-level indicators in source code that suggest deeper problems in the design or implementation.
← Back to all concepts