A hackathon is not a fashion show. Everyone who has ever attended one knows this. The priority is the build — the idea, the team, the code, the demo that has to work in 48 hours regardless of how much sleep you've had or how many times the API went down.
And yet, what you wear to a hackathon matters more than most people admit. Not because anyone is judging your outfit — they're not, they're debugging something — but because the right clothing makes a 48-hour sprint significantly more survivable. The wrong clothing makes it worse in ways that compound slowly and become very obvious at hour 30.
This is the practical style guide for people who build things. Not fashion advice. Functional advice, with the occasional observation about identity and culture, because those things are real too.
The functional requirements first
Before anything else, a hackathon outfit has to pass a basic functionality test. You're going to be sitting for long stretches, moving between spaces, possibly sleeping on a couch or not at all, and presenting your work to judges at the end of it — potentially in the same clothes you've been wearing for two days. The outfit has to survive all of that.
Comfort is non-negotiable
This sounds obvious but gets ignored more often than you'd think, especially for first-time hackathon attendees who underestimate how long 48 hours actually is. Anything that requires adjustment — that rides up, that's stiff, that doesn't breathe, that becomes uncomfortable after four hours of sitting — will become a genuine problem by hour twelve. You will be actively annoyed by it at hour twenty. You will resent it at hour thirty.
The baseline: soft fabrics, relaxed fits, nothing that restricts movement or requires management. If you have to think about your clothes at any point during the hackathon, the clothes are wrong.
Layers are your friend
Hackathon venues are thermally unpredictable. The main hall is cold because of the servers. The quiet room is warm because it's small and full of people. The outdoor area is whatever the weather is doing. You will move between all of these spaces multiple times over 48 hours, and you will not always have time to go back to your bag for a different layer.
The solution is wearing the layers. A base layer you're comfortable in on its own. A mid layer — a hoodie, a zip-up, a light jacket — that you can add or remove in thirty seconds. This system has been independently discovered by every experienced hackathon attendee and is worth adopting immediately if you haven't already.
Pockets
You need pockets. Not decorative pockets. Real pockets, large enough to hold a phone, a charging cable, and whatever snack you've grabbed from the sponsor table. The number of times you need to move quickly between spaces with your hands free during a hackathon is higher than you expect. Pockets solve this. Lack of pockets creates friction at the worst possible moments.
Shoes you can wear for two days
Hackathon footwear is an underrated category. You're going to be on your feet more than you think — getting food, moving between rooms, walking to the presentation space, pacing while you think through an architecture decision. Clean, comfortable sneakers are the answer. Not new shoes you haven't broken in. Shoes you know.
The identity dimension
Once the functional requirements are met, there's a second dimension to hackathon dressing that's worth thinking about: identity. What you wear signals something about who you are and what you're about, and in a room full of developers who are all trying to figure out who to talk to and who to team up with, those signals matter.
The graphic tee as conversation starter
A well-chosen graphic tee at a hackathon functions as a conversation opener. Someone spots a reference they recognize — a specific language, a framework, a developer culture joke — and suddenly you have a starting point. You didn't have to introduce yourself or explain what you work on. The shirt did it for you.
This is why the quality of the reference matters. A generic "I love coding" shirt tells someone you write code. A shirt that references something specific — a particular error, a cultural moment, an inside joke that only lands if you've been in the weeds — tells them something about the kind of developer you are. That's a more useful signal in a room full of people trying to find their team.
The Code Crushes collections were built for exactly this context. No Downtime is for the builder who ships things and keeps moving — the energy that defines the best hackathon participants. Going Analog is for the person who knows when to close the laptop and reset, which is a skill that matters enormously in a 48-hour sprint. The right shirt from either collection is the kind of thing that makes someone stop and say "where did you get that" — which is exactly the kind of conversation you want to be having at a hackathon.
Represent something you actually believe in
Hackathons are full of sponsor t-shirts. You'll get them at registration, at booths, from companies hoping you'll wear their logo around the venue. There's nothing wrong with wearing them — free is free, and some of them are genuinely good quality. But the people who show up in their own gear, in something that actually reflects their identity rather than a sponsor's brand, tend to stand out in a specific way. They look like they know who they are. In a room full of people who are still figuring that out, that's a signal worth sending.
The 48-hour outfit strategy
Most hackathons run 24 to 48 hours. Here's a practical approach to dressing for the full duration.
Day one: arrive sharp
The first few hours of a hackathon are the social hours. You're meeting people, forming teams, pitching ideas, figuring out the space. This is when the identity dimension of your outfit matters most. Wear something that represents you well — a graphic tee you're proud of, clean layers, shoes that look intentional. You're making first impressions and you might as well make them with something that says something true about you.
Mid-hackathon: optimize for function
By hour twelve, nobody cares what anyone is wearing. The social phase is over and the building phase is fully underway. This is when the comfort requirements become paramount. If you've been wearing something slightly uncomfortable, now is when it starts to cost you focus. If you brought a change of clothes — which is worth doing for anything over 24 hours — this is a good time to use them. Fresh clothes at the midpoint of a long hackathon have a psychological effect that's hard to quantify but real.
Demo day: look intentional
The final presentation is the moment that matters most, and it's worth putting a small amount of thought into what you're wearing for it. Not a suit — that's wrong for the context. But something clean, something that looks like you made a choice rather than just whatever survived the sprint. A fresh t-shirt from your bag, or the same graphic tee you arrived in if it held up. The judges are evaluating your project, not your outfit, but looking like you're taking it seriously doesn't hurt.
What to pack
For any hackathon over 24 hours, a small bag with the right items makes a significant difference.
A change of clothes — at minimum, a fresh t-shirt and clean socks. The psychological value of fresh clothes at hour twenty is real and worth the minimal packing effort. A light packable layer for the temperature swings between spaces. Comfortable slip-on shoes or sandals for the moments when you're sitting for extended periods and your feet need a break from proper shoes. Basic toiletries — a toothbrush, deodorant, face wash — because these things matter more than you think after thirty hours in a conference center.
What not to pack: anything that requires special care, anything fragile, anything you'd be upset about getting coffee on. The hackathon environment is not gentle on belongings. Pack accordingly.
The team outfit moment
One underrated hackathon tradition is the team graphic tee. When a team shows up coordinated — not matching in a corporate way, but clearly wearing something they chose together — it signals something. Internal cohesion. A sense of shared identity before the build even starts. Judges notice it. Other participants notice it. And the team notices it about themselves, which is the part that actually matters.
If you're organizing a hackathon team and you want to do this, the window is narrow — you usually have at most a week of lead time. But a matching set of Code Crushes tees, chosen because they actually reflect what the team is about, is the kind of thing that makes the experience feel like more than just a sprint. It makes it feel like something you did together. That's worth something, especially when you're at hour thirty-six and you need a reason to keep going.
The going analog reset
One of the most underrated hackathon skills is knowing when to step away from the screen. Not for long — you don't have time for long — but for ten minutes. To walk outside, to eat something real, to stop looking at the problem directly and let your brain work on it sideways.
The Going Analog collection at Code Crushes was built for exactly this impulse — the recognition that stepping back from the screen is part of the work, not a break from it. The best hackathon participants know this. They wear their going analog energy as consciously as they wear their builder energy, and they know which one is needed at which moment.
A hoodie from the Going Analog collection at hour twenty-four, when you've stepped outside to reset, is exactly the right thing to be wearing. It's comfortable, it's intentional, and it's a small reminder that you're a whole person doing this — not just a machine trying to ship something by morning.
The Code Crushes hackathon kit
If you're building a hackathon wardrobe from scratch, here's the Code Crushes approach. Start with a graphic tee that says something true about you — something from the No Downtime collection if you're there to build and ship, something from the AI Prompters collection if you're working in the ML space, something from the Women in Tech collection if you want to represent that community in the room. Layer it with something comfortable and packable. Add clean sneakers you trust. Bring a second t-shirt for the midpoint reset.
That's it. That's the kit. Everything else is optional.
The outfit that ships
The best hackathon outfit is the one you don't think about after you put it on. The one that keeps you comfortable, keeps you warm or cool as needed, starts one good conversation in the first hour, and gets you through to the demo without becoming a problem.
The hackathon is about the build. The outfit is there to support the build. Get that relationship right and everything else follows.
Now go ship something.