Build archive
Ideas built under a deadline.
Notes from hackathons, builder tracks, and short experiments—what we tried, what changed, and what was worth carrying forward.
- Entries
- 8
- Focus areas
- 7
- Continued
- 2
Filter by focus
1 shown
Jump to2025
2025
1 note
48-Hour Hackathon Build
CampOps
Full Case StudySolo Sprint · Ops Software · Solo build
Problem
Student and community events often rely on scattered spreadsheets, messages, and manual follow-ups, which makes volunteer coordination, sponsorship tracking, and event execution harder than it should be.
Build
I built CampOps, an event management CRM with Next.js, Express, Prisma, PostgreSQL, Clerk, Redux Toolkit, and AI-powered risk analysis to centralize planning, operations, and communication in one workflow.
Takeaways
- For operational software, workflow clarity matters just as much as adding more dashboard features.
- Combining frontend state management, auth, and database tooling in a short sprint required strong boundaries between product scope and infrastructure work.
- A hackathon build can still feel production-minded when the system is organized around real team operations.