More Than Code: What a Hackathon Actually Taught Us
Bug fixes at 3 AM, a server that would not listen, and a team that refused to give up. Our journey at the Environmental Hacks hackathon - what we built on AWS, and everything it taught us beyond code.
When we joined the Environmental Hacks hackathon, we thought the hard part would be writing the code. It was not. The code was the easy part. Everything around it deploying, debugging, deciding, and doing it all as a team against a deadline is where the real learning happened.
The sleepless nights were real
There is something about a 3 AM bug that a classroom never teaches you. The night before our demo, we were still on the server, still fixing things. Our frontend build kept failing because an environment key was missing on the server - the site just refused to update, and for a while we did not know why. Our git history got tangled because database files were accidentally tracked, and every pull became a small adventure. At one point SSH simply stopped connecting, right when we needed to deploy.
None of these problems were in any tutorial. Every one of them had to be understood, not just Googled. And when the fix finally worked at some odd hour, that small "it is live now" feeling was worth every lost hour of sleep.
AWS was a teacher of its own
We went in thinking we would just host the app. We ended up learning how cloud actually works. Our EC2 instance in Mumbai runs everything, and giving it an IAM role instead of access keys taught us how permissions should really be done. We set up SNS for alerts, SES for receipts, CloudWatch for logs, Backup for safety, and Budgets so our student wallets do not get surprised.
Not everything went smoothly. We originally built our AI photo check on Amazon Bedrock, but it was not available on our new account, so we had to redesign that part on a deadline and make the provider switchable. CloudWatch setup fought back before it worked. These were frustrating moments, but they forced us to actually understand the services instead of just following steps.
Bugs, fixes, and more bugs
Our app went through a lot. A full frontend redesign days before the deadline. A language default that refused to change until we traced it to one line. A theme fix that taught us how builds and caching actually work. A payment flow, a handover code system, an admin panel - each one had bugs that only showed up when we tested like real users.
Every fix made the app better, but more importantly, every fix made us better. Debugging as a team - one person reading logs, another testing the flow, someone else checking the database - is a skill we did not have before this hackathon.
The team carried everything
Managing a team through this was a lesson in itself. I learned that a leader's real job is not assigning tasks - it is keeping everyone standing when things fall apart. And my team, they were incredible. Supportive at every step. Even at 3 in the night, when a new bug showed up hours before submission, everyone was ready. Nobody said "mera part to ho gaya." Everyone just asked "kya karna hai?"
I will be honest - there was a moment when we genuinely thought, "ab humse nahi hoga". Too many bugs, too little time, everything breaking at once. But we sat together, took one problem at a time, and kept going. And finally, we submitted our project. That one word - submitted - carries all of it.
What we really take away
Yes, we built a working app that connects scrap collectors to certified recyclers, and we are proud of it. But the bigger outcome is invisible in the demo video. We learned how to break a big problem into pieces and divide them. We learned to trust each other's work. We learned that "it works on my laptop" means nothing until it works on a server, for a real user, in another city.
We came in as four students who could code. We are leaving as a team that can ship.
Thank you WeMakeDevs and AWS for pushing us this hard. It was worth it.
Pratik Solanke
Team Leader, Payload Pirates
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article