Make the deadline part of the business rules
Prediction editing depends on the race deadline. This connects the interface to the application rules, so the saved prediction and what a participant can edit follow the same workflow.
PRODUCTION · FREELANCE TEAM
P1Grid
A Formula 1 prediction platform, built and delivered with a freelance team.
December 2025 — September 2026
The problem
A race-weekend prediction game needs more than a form: participants need to save and revise their picks before a deadline, see rankings, and receive timely communications. Those rules must stay consistent across the application.
My contribution
As a Full Stack Developer at I.Tech, I contributed backend business logic and responsive interfaces using Rails, PostgreSQL, and Tailwind. My work included prediction deadlines, rankings, and scheduled emails, with delivery coordinated through the team’s Git and GitHub workflow.
How the system connects
Engineering decisions
Keep the product inside a cohesive Rails stack
Rails and PostgreSQL support the domain and persistence, while ERB, Turbo, and Stimulus provide the web interface. This keeps the prediction workflow within one application rather than requiring a separate frontend API for every interaction.
Schedule communications separately
Active Job and GoodJob handle scheduled emails. The application can coordinate communications with the race schedule without tying that work to a participant keeping a page open.
What was delivered
- The team delivered a production platform with real users.
- My contribution covered backend rules and responsive interfaces.
- The product includes predictions, rankings, administrative controls, and scheduled communications.
Delivered with the I.Tech freelance team, from client requirements through a shared Git and GitHub workflow.