Beginning with the decision
Hackathons create a strange combination of freedom and pressure. There are many possible ideas and almost no time to build them. During NASA Space Apps, our team focused on a real-time astronaut health monitoring dashboard that could bring vital and environmental information into one view. The first important choice was not technical. It was agreeing on the smallest story we could demonstrate clearly within the event.
Dividing the build
We used Flask REST APIs for the backend and a dynamic JavaScript frontend for visualization. The backend produced consistent health and environment records, while the interface emphasized trends and status changes. Splitting the work at a clear API boundary helped the team move in parallel. We defined sample payloads early so frontend progress did not have to wait for every backend feature.
Making data readable under pressure
A monitoring screen can become a wall of numbers. We prioritized a few signals, clear labels, visible changes, and a narrative the audience could follow. Real-time updates made the demonstration feel alive, but the interface still needed to communicate when data was simulated or incomplete. We tested the complete presentation flow instead of spending the final hours adding disconnected features.
What stayed with me
The challenge taught me that shipping under pressure is mostly about scope and communication. A smaller working system with a clear purpose is stronger than an ambitious collection of half-finished screens. It also showed me how much good teamwork depends on interfaces between people: shared definitions, honest status updates, and the willingness to cut a favorite idea so the whole project can succeed.