hot take: UTHM Forge should host a hackathon every month, not just twice a year. not a 36-hour buildathon. a 12-hour, single-Saturday, single-bounty sprint. run from PTTA Workshop.
the reason: hackathons are recruiting, hackathons are onboarding, hackathons are the only place where a FSKTM Y1 meets a FKMP Y4. one big hackathon a year is a missed opportunity.
— @ameera.fstmi · 15 Apr 2026
<3 replies>
@haikal.fskm15 Apr, 13:30
agree. this is why the UTHM Forge events page already has a 12h bounty sprint template — see the Hacknight: 12-hour Bounty Sprint event for the format. we should probably enforce a "next sprint is in 30 days" cadence so it actually ships monthly.
@najwa.fskm15 Apr, 23:00
monthly is too often. 6 weeks is the right cadence — it forces a real rest between sprints and lets the postmortem from one event inform the next.
@ameera.fstmi16 Apr, 06:18
agreed on 6 weeks. and add a "first-time UTHM builder" track so the sprints double as recruiting. stale sprints = stale community.