awesome-repositories.com
© 2026 Bringes Technology SRL·VAT RO45896025·hello@bringes.io
MCPSitemapPrivacyTerms
Code Quality and Maintenance Philosophies · Awesome GitHub Repositories

1 repo

Awesome GitHub RepositoriesCode Quality and Maintenance Philosophies

High-level behavioral guidelines for developers to reduce technical debt and improve long-term system health.

Explore 1 awesome GitHub repository matching software engineering & architecture · Code Quality and Maintenance Philosophies. Refine with filters or upvote what's useful.

  1. Home
  2. Software Engineering & Architecture
  3. Software Architecture Patterns
  4. Foundational Theory and Guidance
  5. Software Architecture Principles
  6. Code Quality and Maintenance Philosophies

Awesome Code Quality and Maintenance Philosophies GitHub Repositories

Describe the repository you're looking for…
We'll search the best matching repositories with AI.
  • iluwatar/java-design-patterns

    iluwatar/java-design-patterns

    93,757GitHubView on GitHub↗

    This project is a comprehensive educational knowledge base designed to help developers master software engineering excellence through a structured catalog of design patterns and architectural principles. It provides a curated repository of best practices, programming heuristics, and implementation examples, all organiz

    Javaawesome-listdesign-patternshacktoberfest

Explore sub-tags

  • Boy-Scout RulesDevelopment philosophies focused on incrementally improving code quality by leaving the codebase cleaner than it was found.
  • DRY PrinciplesDesign principles requiring that every piece of knowledge has a single, authoritative representation within a system.
  • Maintainability PrinciplesArchitectural strategies aimed at reducing long-term project costs by prioritizing ease of future code maintenance.
Simplicity PrinciplesDesign philosophies that prioritize solving immediate problems directly to maximize progress and minimize unnecessary complexity.
  • YAGNI PrinciplesDevelopment principles advising against the implementation of features or functionality until they are strictly necessary.