Building products while in school: an honest operating manual
Exams don't negotiate and neither do servers. The systems I use to build seriously without failing at either thing.
By Nzubechukwu Cyprian · Pharmacy student at UNN, full-stack developer
Studying Pharmacy while building products means living with two sets of deadlines, and one of them (exams) has no slack, no extensions, and real consequences. Over time I've built an operating manual that keeps both alive. Here it is, honestly.
The systems
Seasons, not balance. There is no daily "balance." There are build seasons and exam seasons, and the switch between them is explicit and planned. Fighting for balance every day produced guilt; planning seasons produced shipped products and passed exams.
Boring infrastructure only. Exams mean three weeks of not touching the server. Everything I run must survive that: managed hosting, automatic backups, no exotic dependencies that need babysitting. My stack is boring by design, and it's the reason products stay up while I'm in the library.
Small scopes, always. The unit of work is a task that fits in a gap between lectures. Nothing that requires "a free weekend" — free weekends are a myth in school.
Status over ambition. Users forgive slow. They don't forgive silence. A status page and honest changelogs cost minutes and buy patience.
The honest part
Some things lose. My social time lost for a while. Some product ideas lost — killed by the season system, which is the point: the system kills ideas I can't resource, so I don't die proving it.
Keep reading
- Product building
Shipping is a skill, and I practised it badly for years
Finishing things is not a personality trait — it's a practice with techniques. The ones that turned my graveyard of half-projects into shipped products.
- Product building
Nobody told me product decisions are reversible or not
The single question that unblocked my decision paralysis: is this door one-way or two-way? Everything else is noise.
- Product building
The pricing page taught me more about users than the analytics did
Data told me what people clicked. The pricing page told me what they believed. Convincing beats tracking.