PeterBucci

Led a multi-developer Agile/Scrum team in turning a real-time, audio-reactive rendering engine into a full-stack web platform for creating, saving, organizing, and launching interactive visual scenes; established the GitHub repositories, project board, sprint workflow, backlog, user stories, and code-review process.

Built core backend infrastructure with Java, Spring Boot, PostgreSQL, and Flyway, including REST APIs, authentication, scene persistence, tagging, and engagement features, with JUnit and Testcontainers integration testing against containerized PostgreSQL.

Developed and integrated React and TypeScript product features around the rendering engine, including scene creation and playback, authentication, discovery, user libraries, media controls, and reusable frontend architecture.

Containerized and deployed the application to AWS, implementing production configuration, reverse-proxy routing, object-storage workflows, and deployment fixes to move the project from local development to a working hosted application.

Recipe Lab is a version-controlled cooking platform I built around the idea that recipes should evolve without losing their history. Instead of overwriting a recipe when it changes, each published version keeps its history and links back to the exact version it came from. Ingredients use standardized identities rather than free-text names, and quantities, instructions, and cooking actions are stored in structured formats.

That structure lets users publish recipes, make their own version of another cook’s recipe, compare versions, follow recipe families, and discover alternatives that better match their tastes or dietary preferences.

It also gives me cleaner data for the recommendation side of the project. I can compare recipes using their ingredients and other structured features, learn from patterns in what people save, rate, and adapt, and combine those signals to experiment with content-based, collaborative, and hybrid recommendation models.