{"id":61988,"url":"https://github.com/ParanoidUser/awesome-practices","name":"awesome-practices","description":"Practices and standards that shape how software gets built","projects_count":72,"last_synced_at":"2026-07-30T14:00:22.711Z","repository":{"id":108281801,"uuid":"590694679","full_name":"ParanoidUser/awesome-practices","owner":"ParanoidUser","description":"Practices and standards that shape how software gets built","archived":false,"fork":false,"pushed_at":"2026-04-20T08:22:09.000Z","size":172,"stargazers_count":18,"open_issues_count":2,"forks_count":2,"subscribers_count":1,"default_branch":"main","last_synced_at":"2026-07-11T13:04:13.895Z","etag":null,"topics":["awesome","awesome-list","best-practices","coding-standards","conventions","developer-tools","guidelines","software-development","software-engineering","standards"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"cc0-1.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/ParanoidUser.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":".github/CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":".github/CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2023-01-19T01:20:26.000Z","updated_at":"2026-06-09T16:20:52.000Z","dependencies_parsed_at":"2026-05-21T01:00:41.619Z","dependency_job_id":null,"html_url":"https://github.com/ParanoidUser/awesome-practices","commit_stats":{"total_commits":84,"total_committers":2,"mean_commits":42.0,"dds":"0.22619047619047616","last_synced_commit":"75f4abbcdc2f1b4ad96bb2bece3d2b3708cd1a3b"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/ParanoidUser/awesome-practices","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ParanoidUser%2Fawesome-practices","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ParanoidUser%2Fawesome-practices/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ParanoidUser%2Fawesome-practices/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ParanoidUser%2Fawesome-practices/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ParanoidUser","download_url":"https://codeload.github.com/ParanoidUser/awesome-practices/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ParanoidUser%2Fawesome-practices/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":36079865,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-07-20T02:08:10.276Z","status":"online","status_checked_at":"2026-07-30T02:00:05.956Z","response_time":106,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"created_at":"2024-06-16T00:00:17.041Z","updated_at":"2026-07-30T14:00:22.711Z","primary_language":null,"list_of_lists":false,"displayable":true,"categories":["Teamwork","Process","Design","Development","Security","Methodology","Tools","Culture"],"sub_categories":[],"readme":"# Awesome Practices [![Awesome](https://awesome.re/badge.svg)](https://awesome.re)\n\nGuidelines, standards, and conventions that shape how software gets built.\n\n## Design\n\n*Creating interfaces that are usable and accessible.*\n\n- [A11Y Project](https://www.a11yproject.com/checklist/) - Checklist and resources for implementing web accessibility.\n- [BEM Methodology](https://getbem.com) - Naming convention for organizing CSS classes into reusable components.\n- [Contrast Rebellion](https://contrastrebellion.com) - Manifesto advocating for readable, high-contrast text in web design.\n- [Guide to Accessible Form Validation](https://www.smashingmagazine.com/2023/02/guide-accessible-form-validation/) - Patterns for creating form validation that works for all users.\n- [Laws of UX](https://lawsofux.com) - Psychological principles that influence user interface design.\n- [Material Design Guidelines](https://m2.material.io/design/guidelines-overview) - Google's design system for building consistent, accessible interfaces.\n\n## Development\n\n*Writing code with languages, frameworks, and platforms.*\n\n- [Android Developer Guides](https://developer.android.com/get-started/overview) - Official guidance for building Android apps with framework APIs.\n- [AWS Well-Architected](https://aws.amazon.com/architecture/well-architected/) - Framework for building secure, resilient, and efficient cloud infrastructure.\n- [Best practices for writing Dockerfiles](https://docs.docker.com/build/building/best-practices/) - Recommendations for building efficient and maintainable container images.\n- [Command Line Interface Guidelines](https://clig.dev) - Patterns for designing user-friendly command-line programs.\n- [EKS Best Practices Guides](https://aws.github.io/aws-eks-best-practices/) - Operational guidance for running Kubernetes on Amazon EKS.\n- [Google API Design Guide](https://docs.cloud.google.com/apis/design) - Standards for designing consistent and intuitive APIs.\n- [Go Optimization Guide](https://goperf.dev) - Techniques for writing high-performance Go applications.\n- [Google Best Practices for Java Libraries](https://jlbp.dev) - Rules for building compatible and maintainable Java libraries.\n- [Google Cloud Architecture Framework](https://docs.cloud.google.com/architecture/framework) - Principles for designing and operating cloud infrastructure.\n- [Google Engineering Practices](https://google.github.io/eng-practices/) - Guidelines for code review and development workflows at Google.\n- [Google Style Guides](https://google.github.io/styleguide/) - Coding standards for multiple programming languages.\n- [Guiding Principles of REST](https://restfulapi.net/rest-architectural-constraints/) - Architectural constraints for designing RESTful APIs.\n- [Hitchhiker's Guide to Python!](https://docs.python-guide.org) - Opinionated guide for Python installation, configuration, and usage.\n- [Java Version Almanac](https://javaalmanac.io) - Reference for Java version history and feature changes.\n- [OpenFeature](https://openfeature.dev) - Vendor-agnostic specification for feature flag management.\n- [Prompt Engineering](https://www.promptingguide.ai) - Techniques for crafting effective prompts for language models.\n- [Style Guide for Protobuf](https://buf.build/docs/best-practices/style-guide/) - Conventions for writing Protocol Buffer schemas.\n- [Java Design Patterns](https://java-design-patterns.com) - Catalog of software design patterns with Java examples.\n- [Kubernetes Configuration Best Practices](https://kubernetes.io/blog/2025/11/25/configuration-good-practices/) - Guidelines for configuring Kubernetes workloads.\n- [Maven Code Style and Code Conventions](https://maven.apache.org/developers/conventions/code.html) - Formatting standards for Maven project source code.\n- [Terraform Best Practices](https://www.terraform-best-practices.com) - Patterns for writing maintainable infrastructure as code.\n\n## Process\n\n*Shipping releases from development to production.*\n\n- [C4 Model](https://c4model.com) - Approach for visualizing software architecture at different levels of detail.\n- [Conventional Commits](https://www.conventionalcommits.org) - Specification for structured, machine-readable commit messages.\n- [Conventional Comments](https://conventionalcomments.org) - Format for labeling and categorizing code review comments.\n- [Conventional Logs](https://www.conventionallogs.org) - Specification for structured, machine-readable log messages.\n- [DORA Guides](https://dora.dev/guides/) - Research-backed practices that drive software delivery performance.\n- [Functional Documentation](https://heydonworks.com/article/functional-documentation/) - Approach for writing maintainable documentation for design systems.\n- [GitLab Documentation Style Guide](https://docs.gitlab.com/development/documentation/styleguide/) - Standards for grammar, formatting, and structure in technical writing.\n- [Kanban Guides](https://kanbanguides.org) - Framework for optimizing workflow and delivery through visual management.\n- [Keep Changelog](https://keepachangelog.com) - Format for maintaining human-readable project change history.\n- [Manifesto for Agile Software Development](https://agilemanifesto.org/iso/en/manifesto.html) - Core values and principles behind Agile methodologies.\n- [Manifesto for Fluid Software Development](https://fluidmanifesto.org) - Principles for adaptive, flow-focused software development.\n- [Minimum Viable CD](https://minimumcd.org) - Essential practices required for continuous delivery adoption.\n- [MLOps Principles](https://ml-ops.org/content/mlops-principles) - Practices for deploying and managing machine learning models in production.\n- [Open GitOps](https://opengitops.dev) - Standards for implementing GitOps-based delivery workflows.\n- [Patterns for Managing Source Code Branches](https://martinfowler.com/articles/branching-patterns.html) - Strategies for effective branching and integration workflows.\n- [Scrum Guides](https://scrumguides.org) - Official definition of the Scrum framework for product development.\n- [Semantic Versioning](https://semver.org) - Convention for communicating compatibility through version numbers.\n- [The Twelve-Factor App](https://12factor.net) - Methodology for building scalable, maintainable SaaS applications.\n- [Transparent Telemetry](https://research.swtch.com/telemetry) - Principles for collecting useful telemetry while respecting user privacy.\n- [Trunk Based Development](https://trunkbaseddevelopment.com) - Branching strategy using short-lived branches merged frequently to main.\n- [Write the Docs](https://www.writethedocs.org/guide/) - Community guide for creating effective software documentation.\n- [Writing Better Release Notes](https://simonwillison.net/2022/Jan/31/release-notes/) - Practices for communicating changes clearly to users.\n\n## Tools\n\n*Tackling routine tasks and technical choices.*\n\n- [Choose a License](https://choosealicense.com) - Guidance for selecting an open source license for your project.\n- [Command-not-found](https://command-not-found.com) - Lookup tool for finding package installation commands across operating systems.\n- [Dangit, Git!?!](https://dangitgit.com) - Solutions for common Git mistakes and how to fix them.\n- [End-of-life](https://endoflife.date) - Reference for product EOL dates and support lifecycles.\n- [Gitignore](https://www.toptal.com/developers/gitignore/) - Generator for creating .gitignore files for any tech stack.\n- [IP Guide](https://ip.guide) - API for looking up IP addresses, networks, and ASN data.\n- [JSON Resume](https://jsonresume.org) - Standard format for creating machine-readable resumes.\n- [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org) - Generator for secure TLS configurations across web servers.\n- [Think Like (a) Git](https://think-like-a-git.net) - Conceptual guide for understanding Git's internal model.\n- [Typograms](https://google.github.io/typograms/) - Lightweight format for creating diagrams from ASCII art.\n- [Which Version of JDK Should I Use?](https://whichjdk.com) - Opinionated guide for choosing a JDK distribution.\n\n## Security\n\n*Protecting systems from vulnerabilities and attacks.*\n\n- [Node.js Security Best Practices](https://nodejs.org/en/learn/getting-started/security-best-practices) - Guidelines for securing Node.js applications against common threats.\n- [OWASP Top 10](https://owasp.org/Top10/) - Ranking of the most critical web application security risks.\n- [security.txt](https://securitytxt.org) - Standard for publishing security contact information on websites.\n- [TLS Cipher Suite Search](https://ciphersuite.info) - Reference for TLS cipher suites and their security properties.\n\n## Teamwork\n\n*Growing professionally through collaboration and community.*\n\n- [Amazon Leadership Principles](https://www.amazon.jobs/content/en/our-workplace/leadership-principles) - Decision-making principles used across Amazon's engineering culture.\n- [Code of Conduct for Open Source Communities](https://www.contributor-covenant.org) - Template for establishing inclusive community standards.\n- [Developer Marketing Guide](https://www.devmarketingguide.com) - Strategies for creating content and building developer communities.\n- [Developer Roadmaps](https://roadmap.sh) - Learning paths for various technologies and engineering roles.\n- [Hacker Laws](https://hacker-laws.com) - Mental models and principles relevant to software development.\n- [Open Source Guides](https://opensource.guide) - Resources for starting and contributing to open source projects.\n- [Principles of Green Software Engineering](https://principles.green) - Practices for building environmentally sustainable software.\n- [StaffEng](https://staffeng.com/guides/) - Guidance for reaching and succeeding in Staff-plus engineering roles.\n","projects_url":"https://awesome.ecosyste.ms/api/v1/lists/paranoiduser%2Fawesome-practices/projects"}