I build software products alone, between classes, while doing a BS in Software Engineering. No team, no funding, no roadmap meetings. Just me deciding what to build on a Tuesday night and shipping something by the weekend.
Here's what that actually looks like.
## The stack doesn't matter as much as you think
I use Next.js, Supabase, and Tailwind for almost everything. Not because they're the "best" tools, but because I stopped switching. Every time I picked up something new, I spent the first week relearning instead of building. Pick a stack you can build in without thinking, and stick with it until it's actually holding you back.
## Time is the real constraint, not skill
As a student, I don't lack ideas or technical ability. I lack hours. Between coursework and assignments, I get maybe 2-3 focused hours a day, if that. So the projects that actually ship are the ones scoped small enough to finish in a weekend or two. Anything bigger dies in a folder somewhere.
The lesson: cut scope until it's almost embarrassing how small the first version is. Ship that. Add the rest later, if anyone even asks for it.
## Nobody cares about your product on day one
I used to think launching meant a spike of users and instant feedback. It doesn't. Most of what I ship gets a handful of visitors in the first week, if that. The ones that eventually find traction do it slowly, through search, through someone stumbling on it months later, not through a big launch moment.
So I stopped chasing launch day hype and started building things I'd actually keep maintaining even with zero users, because that's the default state for a long time.
## Payments and infra are a solved problem now
This is the part that's genuinely different from five years ago. Setting up auth, a database, and payment processing used to take real time. Now it's mostly configuration. I spend almost no time on infrastructure and almost all my time on the actual product logic and whether it solves a real problem.
That shift matters a lot for someone building solo with limited hours. The boring parts got cheap. Use that.
## What I'd tell myself a year ago
Ship smaller than feels comfortable. Don't wait to "learn more" before starting — you learn by shipping broken things and fixing them in public. And don't confuse being a student with having an excuse. Limited time is a constraint, not a disqualifier.
I'm still doing this the same way: one small project at a time, mostly at night, mostly alone. It works.
Loading article