We want a simple, friendly platform where HITSZ students can find someone to study with, ask a senior for help before an exam, or just share notes without the hassle. CS students come first. That's it. Build it your way.
WindowFriday 00:00 → Sunday 23:00 (Shenzhen)
--
hours
--
min
--
sec
Solo? No problem.
Join the pot
Don't have a teammate yet? Drop your name in. One hour before the hackathon starts, everyone in the pot gets paired into teams of two. You'll see your partner's name here, then it's on you two to talk and start building.
Hack Hive members only — the access code is your proof of membership. Matching happens Thursday 23:00 Shenzhen time. Teams are exactly two people. Names sync live: what you see, everyone sees.
In the pot
you're in as
You're paired with . Find them. Say hi. Start building.
The brief
What you're building
A platform — desktop only — that does at least one of these well. You don't need all four. Pick what matters, do it properly. Helping CS students is the top priority; everything else is decoration.
01Find a study buddyMatch by course, schedule, or just who's free tonight.
02Ask a seniorA way to get help from someone who already survived the course.
03Share resourcesNotes, past papers, links to HITSZCS repos. Keep it simple.
04Study togetherRooms, timers, group chat — whatever makes "let's study" real.
Timeline
How the 71 hours go
Thu 23:00Matching. Solo participants get paired into teams of two.
Fri 00:00Start. Portal opens. Meet your teammate, pick an idea, go.
Fri 12:00Optional check-in. Post a screenshot if you want. No pressure.
Sun 18:00Five hours left. Wrap up, test, screenshot your work.
Sun 23:00Done. Push your repo, submit the link. Judging starts.
Rules
House rules
Two per team. Exactly two — no solos, no trios. Coming alone? The pot pairs you up.
Hack Hive members only. This is an in-house event. The access code is your proof of membership.
Vibecoding counts. AI-assisted or hand-written, both are fine. Ship however you work — just understand every line you submit.
Desktop only. Web or native, but it runs on a desktop. Mobile is out of scope; don't burn hours on it.
Repo link + image. No live demo session — screenshots are your demo. And write real documentation: setup, architecture, decisions, all in README.md.
Frontend and architecture carry weight. Judges look hard at how it looks and how it's structured. Sloppy folders cost points.
CS students come first. If it doesn't actually help a CS student survive the semester, it misses the point.
Judges' decisions are final. Criteria: does it work, is it usable, is it thoughtful. No appeals, no hard feelings.
Grab a friend, or don't — the pot will find you one. Either way, build something you'd actually use next semester.