Initial Quality Inventory
-
1 What the Project Can Already Check80 min
-
2 `make qa` as a Single Checkpoint75 min
After Git, Docker, PHP, Laravel, DDD-lite, and Octane, the student already knows how to write working code and understand the application lifecycle. But working code is not the same as change readiness, review readiness, or deployment readiness. If quality depends on whether the developer remembered to run tests, rebuild the frontend, or catch an issue during review, the project remains fragile. This course treats quality as an engineering pipeline. The student takes an existing Laravel/Filament/Octane project and gradually builds a feedback system around it: local Make commands, automatic formatting, static analysis, controlled Rector usage, testing strategy, coverage reports, parallel tests, GitHub Actions, pre-commit hooks, structured logs, healthchecks, and simple architecture guards. The main result is a shift in thinking. Works on my machine is no longer a readiness criterion. Readiness means the project can be checked with one clear command, the same checks can run in CI, important runtime signals are visible, and the remaining manual risks can be named honestly.
Published version: modules, lessons, and duration.