The Project

Problem: Hackathon projects usually fail for simple reasons, unclear scope, messy handoffs, and last-minute integration problems. Our goal was to ship an interactive experience within a tight deadline while keeping the build stable enough to demo. What we built: We created interactive modules that visualised real-world data using React and TypeScript, with Three.js for 3D rendering. The project focused on turning external API data into something users could explore quickly, with clear UI flows and responsive rendering. My contribution: I worked on implementation tasks that helped us move from concept to a working demo. That included integrating external APIs, shaping the data into UI-friendly structures, and building components that could be reused across the experience. I also helped keep the project organised through Git, splitting work into smaller pieces so we could review changes and reduce merge conflicts. How I approached it: I focused on reliability and clarity. I preferred predictable data flow, defensive handling for missing fields, and simple component boundaries. In a hackathon setting, that discipline matters because it prevents last-minute surprises. Outcome: We shipped a functional, interactive build under time pressure, with a codebase that still made sense after the event. This project also strengthened my comfort working in a team environment where speed matters but structure still pays off.