Participant code of conduct

Whoa, before we jump into hacking and building and cheering each other on, we need one simple thing that keeps the whole room from tipping over. A participant code of conduct. It is not here to kill fun. It is here so people can actually do their best work without getting pushed around, talked over, or made to feel small.

Hack to the rescue feels like a living market stall line. Ideas calling out, teams trading skills, mentors moving fast, someone debugging at 2 a.m., someone else pitching with shaky hands. When it works, it is amazing. When it goes wrong, it goes wrong fast. So this code is our shared deal. We treat people with respect. We listen. We keep jokes safe. We stop problems early instead of letting them grow.

This also means being honest about what we know and what we do not know in the moment. If you are unsure about a rule or a boundary, ask. If something feels off, say it early. If you mess up, own it and fix it quick. That is how trust stays real during the event.

At the end of the day, this code is about making space for everyone to build, learn, and show up as themselves without fear. If we follow it together, the best parts of hack to the rescue get louder and the worst parts do not get a chance.