In Spring 2026 I left the Rochester Institute of Technology mid-semester to build for clients full-time. Two months later I had two production sites live and a third in client review. People want to know if I'd recommend it. The honest answer is: only if a specific version of the math works for you.
The decision was about leverage, not school
I wasn't unhappy at RIT. The CS coursework was solid, on top of a 4.0 in computer science from Orange Coast College. The professors were good. The campus is in Rochester, which is where I want to be.
But I noticed something around the start of the semester: every time I shipped something real outside class — a contact form, a member portal prototype, a small marketing site — the loop closed faster than any assignment ever had. Twelve hours of focused work would produce a clickable thing a real person could touch. The same twelve hours of class work produced a problem set graded a week later.
That's the leverage question. Not "is school bad" — school is fine. "What's the rate at which I'm building real things?" was the question. The answer was clearly: not high enough.
The math has to work
Leaving school is not a romantic gesture. It's a budget question. The numbers I ran:
- I had one foot in two client engagements that were ready to convert to paid work if I had the bandwidth.
- The savings runway was about four months.
- The realistic break-even point was project two — i.e., if I closed two paying projects in two months, I'd be sustainable.
I left after I had a verbal yes from client one and a signed scope on client two. Not before.
If I'd left on vibes, this post would read very differently. The leverage was there; the runway was sufficient; the conversion path was already in motion. All three had to be true.
The first two weeks felt wrong
The hardest part wasn't the work. The hardest part was the silence. No 9 AM lecture, no problem set deadline, no roommate's class schedule pulling me into the world. Just me and a build queue.
I had to invent the structure. I picked these rules and kept them:
- 9 AM start, every day. No exceptions.
- Lighthouse audit on every commit. Pre-merge, not post-deploy.
- One hour of cold outreach per day in the first month. Two emails minimum.
- Friday: ship something to a client, even if it's a draft they can scroll through.
These are not productivity hacks. They are the substitute scaffold that replaced what school was providing for free.
What I learned
Shipping is the curriculum. Every site I built taught me something the prior site didn't surface — RBAC patterns, CSP nonce tradeoffs, Cloudflare-vs-Vercel routing surprises, IndexNow gotchas, schema validation edge cases. Each of those costs you a half-day on the project where it bites, and saves you a half-day on every future project. The compounding is real.
The other thing: clients pay for results, not for the AI tooling, not for the framework choice, not for the GitHub commits. They pay for a thing that does the job. The faster I learned to lead conversations with "what's the outcome you're paying for," the faster scoping calls closed.
What I'd tell you
If you're a CS student wondering whether to do this:
- Don't leave for the romance of it. Leave for the math.
- Have at least one signed engagement before you leave. Two is better.
- Pick a stack and stop switching. The stack is not the moat; the cadence is.
- Build a public artifact you can point at — a live URL with the client's name on it, not a personal project. Real client work compounds in conversations.
I'm available now for full-time, contract, and freelance roles. If you have a build you want shipped, I reply within a day.