Leading a team in an academic setting
The FATEC Itu capstone brought the whole class together and split it into frontend and backend squads. I took on the frontend lead role — distributing tasks among the ~4 teammates, ensuring integration with the API the backend squad was building in parallel, and presenting progress at each milestone to faculty and the class.
The people-management side was as demanding as the technical work: aligning different paces, handling delayed deliverables, and keeping the interface coherent while components were developed in parallel required constant communication and frequent code reviews.
The main technical challenge
Conflict validation for bookings stayed on the backend — deliberately. Moving that logic to the client would have seemed faster, but it would create inconsistency with multiple users booking simultaneously. Using JWT with roles (admin, professor, student) required guard layers on both sides, forcing the team to think early about attack surface and least-privilege access.
On the frontend, we built a custom calendar component instead of pulling in a third-party library — more work, but we learned the control-versus-maintenance-cost trade-off first-hand rather than in theory.
Lighthouse scores and test coverage will be collected after the live deploy (pending — Phase 7). Any number reported before that would be speculation.