Define project goals

[srgpsk]

Learning Goals:

• [ ] Systems Design - diagram high level key components and understand their relationships and basic implementation
• [ ] Data design - model entire database showing all entities and their relationships
• [ ] UML - use UML as a tool for diagramming and sharing design before writing code
• [ ] OOP - learn how to think in terms of objects that adhere to SOLID principles
• [ ] API design - learn API design best practices

Process Goals:

• [ ] TDD - encourages writing testable, loosely-coupled code that tends to be more modular
• [ ] Continuous Integration (CI)
  • Commit early, commit often
  • Automate testing
  • Containerization and automation of environments
• [ ] Continuous Deployment (CD)

Application Goals:

• [ ] From scratch - No external packages. The project's main purpose of it is understand the nature of things. So if we need e.g. router - we won't do a composer install, but rather write our own router. The idea is to understand how it works to the level that you could write it yourself and explain how it works.
• [ ] Code quality - Rely on latest PHP features, PSRs and any good automation is fine, while we understand how it works.

[srgpsk]

About requirements, I was thinking about next:

• From scratch: No external packages, since this is a training the main purpose of it is understand the nature of things. So if we need e.g. router - we won't do a composer install, but rather write our own router. It's fine to look how it was done anywhere else and write it that way too. Hopefully not much copy-paste will happen. The idea is to understand how it works to the level that you could write it yourself and explain how it works.
• Tools: It's fine to bring external tools, things like PHPUnit, static analysis, code sniffers, formatters, whatever .
• Code quality: rely on latest PHP features, PSRs https://www.php-fig.org/ and any good automation is fine, while we understand how it works.

That's probably all I have right now.

[srgpsk]

And yeah, speaking of OOP and databases, I was thinking we could deliver the first MVP, let's say Cart + Checkout, without using any of that. Once we do that, we could start modeling something on top of the object and DB and see what benefits it may provide

[srgpsk]

CD part would involve deploying to an external server, so that would be somewhere at the second part of the journey I guess