https://github.com/chemaclass/php-best-practices
What I consider the best practices for web and software development.
https://github.com/chemaclass/php-best-practices
agile agile-development best-practices clean-code continual-learning discover knowledge knowledge-sharing learning php php-best-practices quality quality-improvement strict-types team-work web-development
Last synced: 7 months ago
JSON representation
What I consider the best practices for web and software development.
- Host: GitHub
- URL: https://github.com/chemaclass/php-best-practices
- Owner: Chemaclass
- Created: 2019-10-08T09:56:31.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2023-10-09T10:28:59.000Z (about 2 years ago)
- Last Synced: 2025-04-05T07:33:26.659Z (8 months ago)
- Topics: agile, agile-development, best-practices, clean-code, continual-learning, discover, knowledge, knowledge-sharing, learning, php, php-best-practices, quality, quality-improvement, strict-types, team-work, web-development
- Homepage:
- Size: 1.43 MB
- Stars: 78
- Watchers: 8
- Forks: 10
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# PHP Best Practices
Apart from consulting:
* [PHP The Right Way](https://phptherightway.com/)
* [Clean Code adapted for PHP](https://github.com/jupeter/clean-code-php)
* [Awesome PHP libraries and resources](https://github.com/ziadoz/awesome-php)
* [My personal blog](https://chemaclass.com/blog)
## Teamwork
| | |
|------------------------------------------------------|-----------------------------------|
| [Agile](/team-work/agile.md) | Agile software development values |
| [Agreements](/team-work/agreements.md) | We need conventions |
| [Code Reviews](/team-work/code-reviews.md) | Pair Programming & Pull Request |
| [Documentation](/team-work/documentation.md) | Document your knowledge |
| [Estimations](/team-work/estimations.md) | Discover the unknowns |
| [Knowledge sharing](/team-work/knowledge-sharing.md) | Follow the news of your stack |
## Technical skills
| | |
|---------------------------------------------------------------------------|---------------------------------------------------|
| [Comments](/technical-skills/comments.md) | They are not always updated |
| [Decoupled business logic](/technical-skills/decoupled-business-logic.md) | Abstraction, concretions, layers and dependencies |
| [Final Classes](/technical-skills/final-classes.md) | Composition over inheritance |
| [Functions](/technical-skills/functions.md) | They should be small |
| [Git Mastering](/technical-skills/git-mastering.md) | The best software version control |
| [IDE](/technical-skills/ide.md) | Know your IDE |
| [Immutability](/technical-skills/immutability.md) | It makes the code more predictable |
| [Meaningful Names](/technical-skills/meaningful-names.md) | It should tell you why it exists and what it does |
| [Minimum Scope](/technical-skills/minimum-scope.md) | For your variables, methods, and classes |
| [Performance Tips](/technical-skills/performance-tips.md) | Use strict comparison |
| [Strict Types](/technical-skills/strict-types.md) | Use strict_types constant when possible |
| [Static Analysis](/technical-skills/static-analysis.md) | Identify bugs in your code |
| [Testing](/technical-skills/testing.md) | Test what your software does |