This capstone project was the most technically demanding work I've undertaken. Building a full-stack e-commerce application from scratch — with three user roles, a normalized 12-table database, Stripe payment integration, and a CI/CD deployment pipeline — required me to apply and extend every skill from my coursework in a single integrated project.
The biggest technical growth came in backend development. Writing complex SQL JOINs that pull product data with vendor names and category labels, building database transactions with rollback for order creation, and implementing session-based authentication with role-specific access control were all areas where I went from textbook understanding to practical fluency. The Stripe integration was a highlight — understanding the PaymentIntent workflow (create server-side, confirm client-side, verify server-side before touching the database) gave me real insight into how production payment systems work.
Security was a consistent theme throughout every phase, not an afterthought. By the time I documented the security audit, I had already been applying prepared statements, CSRF protection, output escaping, and bcrypt hashing from Phase 3 onward. The OWASP Top 10 mapping in the audit wasn't aspirational — it reflected what was already built.
The three XAMPP MySQL crashes this semester were frustrating but educational. Each recovery got faster as I refined the process, and the final consolidation of all seed data into a single importable SQL file was a direct response to the pain of running four separate patch files after every crash. That kind of iterative improvement — building better tools in response to real problems — is something I'll carry into professional work.
The GitHub Actions CI/CD pipeline transformed my workflow. Knowing that every push to main automatically deploys to production through lftp, with Composer installing dependencies and sed injecting secrets from GitHub's encrypted store, gave me confidence to ship changes quickly. The automated project board status updates in the README were a nice touch that kept the repository self-documenting.
Looking back, the project scope was ambitious for 48 estimated hours — the actual 51.5 hours reflects the reality of infrastructure work (hosting setup, CI/CD, three crash recoveries) that isn't visible in the feature list but is essential to a production-deployed application. I'm proud that the project shipped four days ahead of schedule with all 48 tasks complete, all 76 test cases passing, and a live production site that demonstrates every feature.
Virginia Market Square is the strongest piece in my portfolio — not just because of its technical scope, but because it represents a complete development lifecycle from charter to deployment, with documentation, testing, and security built in at every step.
