Balancing College, Freelancing, and a Flagship Project: My Semester Playbook

A semester with coursework, active client freelancing, and building InfraFlow as a flagship project all at once sounds like a recipe for something quietly failing. The playbook that kept all three moving wasn't about finding more hours — it was about not treating them as equally interruptible.

Time-block by commitment type, not by task

Instead of a flexible to-do list I'd reorder daily, I fixed which days had client-work blocks, which had coursework blocks, and which had flagship-project blocks — and protected each block from the others. The instinct to "just quickly check on the client project" during a coursework block was the single biggest silent time-sink before I started treating blocks as non-negotiable boundaries, not suggestions.

Client work gets fixed availability windows, not "whenever"

Clients weren't told "I'll get to it when I can" — they were told which days I was responsive and which I wasn't, upfront, as part of scoping the engagement. That turned an ambiguous, anxiety-inducing "I should probably check Slack" background hum into actual, boundaried focus time on the days I wasn't client-facing.

The flagship project got the worst time slots on purpose

Coursework has externally enforced deadlines; clients have contractually implied ones. A personal project has neither, which means it's the first thing that silently slips when things get busy — unless it's deliberately given protected time even when that time is inconvenient (early mornings, in my case), specifically because nothing else will protect it for you.

What I dropped, and don't regret

Most extracurricular commitments that weren't directly building toward the DevOps specialization I cared about. Not every opportunity is worth saying yes to, and the ones I said no to that semester weren't ones I look back on with regret — the honest test wasn't "would this have been valuable" but "valuable compared to what it would have displaced."

What I'd do differently

Build in slack for the weeks that inevitably don't go to plan — a client emergency, a harder-than-expected assignment. My first attempt at this schedule had zero buffer, which meant any single disruption cascaded into the next week's plan instead of absorbing cleanly.

Takeaway

The playbook wasn't a time-management trick — it was treating three genuinely important commitments as each deserving protected, non-negotiable time, instead of letting whichever one shouted loudest that day win by default.