title: "The Road Not Often Traveled: When Your Side Project Becomes Your Main Occupation" date: 2025-10-01 author: David Sanker
There's a particular kind of quiet that settles over a house at midnight. Everyone else asleep, the cursor blinking at me, the legal briefs stacked on one side of the desk and the half-finished Python script open on the other. I lived in that quiet for years — not because I had to, but because something in me couldn't let either world go.
I was a lawyer who coded. Not a coder who happened to pass the bar, and not a lawyer dabbling in tech as a hobby. Both of those things, fully, at once. And for a long time, I didn't know what to do with that.
Key Facts
- The transition from a side project to a primary occupation didn't happen overnight — it emerged through small pivots, honest conversations, and a willingness to sit with uncertainty.
- Mentorship and community played a larger role in the shift than any single moment of inspiration.
- Balancing dual roles required a fundamental reprioritization of time, not just better scheduling.
- The interconnected nature of law and technology turned out to be a feature, not a flaw.
- Resilience wasn't something I arrived with — it was something the process built.
The Unexpected Shift: From Hobby to Career
It started practically. I was spending too many hours doing work that felt like it could be automated — document review, clause comparison, the mechanical parts of legal practice that drained time without requiring judgment. So I learned to code. Not to build a company. Just to solve a problem in front of me.
But then a strange thing happened. The problem got more interesting than the solution.
I started reading about machine learning. Then natural language processing. Then I was building tools that didn't just help me — they could help other lawyers, other firms. And somewhere in the middle of a late-night debugging session, a thought surfaced that I couldn't quite shake loose: what if this is more than a side project?
That question didn't announce itself dramatically. It showed up quietly, the way important things often do. A conversation at a conference where someone said, "you should really be doing this full-time." A mentor who asked me, point-blank, what I was afraid of. A small tool I'd built that someone else called genuinely useful — not politely, but with the kind of specificity that meant they meant it.
The transition didn't happen in a single leap. It was a mosaic of moments, each one adding a little more weight to one side of the scale.
Navigating the Dual Identity: A Balancing Act
Here's what nobody tells you about carrying two serious roles at once: it's not the workload that's hardest. It's the identity.
On paper, my calendar looked manageable — client meetings during the day, code at night, weekends split between both. In practice, I was constantly code-switching in ways that went deeper than just switching tasks. Being a lawyer asks you to be precise, conservative, risk-aware. Building something new asks you to be loose, experimental, willing to ship something imperfect. Those are genuinely different orientations toward the world, and toggling between them in the same day is its own kind of exhaustion.
What helped was giving up on the idea that I had to be equally good at both simultaneously. Some weeks, the legal work needed everything I had. Some weeks, I could disappear into a technical problem for days. The rhythm was less like a balanced scale and more like breathing — in and out, different emphasis at different moments.
I also had to get honest about what I was protecting. There's safety in a legal title. People understand it. It has a clear shape. Stepping further into the technology space meant entering territory where my credentials didn't precede me, where I had to earn credibility in a different currency. That's uncomfortable in ways that are hard to admit.
But that discomfort turned out to be directional. It was pointing somewhere worth going.
Building an Interconnected Career Mosaic
What I didn't anticipate was how much each world would improve the other.
My legal training made me a better technologist. I understood compliance, liability, the way regulations actually function in practice — not as abstract rules but as constraints that shape what's buildable. When other founders were surprised by a legal obstacle, I'd seen it coming three steps earlier. That's not a small advantage.
And the technology work made me a better lawyer. I thought differently about process, about systems, about where human judgment was genuinely necessary versus where it was just habit. I asked better questions. I was less precious about the way things had always been done.
What emerged wasn't a compromise between two careers. It was something that couldn't have existed if I'd stayed entirely in either lane.
I think of it as a mosaic rather than a ladder. A ladder implies you're always moving toward one fixed point at the top. A mosaic is built from pieces that don't look like much on their own — but when you step back, they form something coherent, something that's specifically yours.
Practical Lessons from the Pivot
1. Embrace change, but don't romanticize it. Change is uncomfortable in specific, practical ways — financial uncertainty, loss of status, steep learning curves. Acknowledge those realities rather than papering over them with inspiration.
2. Cultivate resilience through small recoveries. The big setbacks get remembered, but resilience is actually built through all the smaller ones — the feature that didn't work, the partnership that fell through, the week where nothing clicked. Each recovery matters.
3. Let your interests inform each other. Don't keep your worlds artificially separate. The most interesting thinking I've done has happened at the intersection — where legal reasoning met algorithmic design, where compliance met creativity.
4. Treat time as the honest constraint it is. Calendar blocks aren't about productivity theater. They're about protecting the kind of deep, uninterrupted work that actually moves things forward. That discipline took me longer to develop than I'd like to admit.
5. Don't travel alone. The mentors who challenged me, the communities where I found people asking similar questions — these weren't supplements to the journey. They were load-bearing parts of it.
Reflecting on Your Journey
I'm not going to tell you that your side project is secretly your calling, or that the thing you do at midnight is where your real life is hiding. That would be too easy, and probably wrong.
But I will ask this: what are you working on when nobody's watching? Not the project you're supposed to care about — the one you actually return to, even when you're tired, even when it's not going well?
That thing is worth paying attention to. Not necessarily as a business plan, but as a signal. It's telling you something about where your real energy lives.
The roads worth traveling rarely announce themselves clearly at the start. Mine didn't. I just kept walking, kept showing up in that midnight quiet, and eventually the path became visible by the walking.
What path is asking for more of your attention right now?
FAQ
Q: How do I know if my side project can become my main career? A: Look at three things honestly: Is it growing on its own momentum, even when you're not pushing it? Does it have real financial viability, or at least a credible path there? And does it energize you in a way that feels sustainable, not just exciting in the short term? Also consider whether it connects to skills and experience you already have — the transition is much smoother when you're building on something rather than starting from scratch.
Q: What challenges might I face when balancing a side project with a full-time job? A: The obvious ones are time and energy. The less obvious ones are identity and commitment — it's hard to give something your full creative investment when you're protecting a fallback. You'll also face the challenge of context-switching between different modes of thinking, especially if your main job and your side project require fundamentally different orientations. Managing stress and maintaining the commitments people are counting on you for, in both worlds, is genuinely difficult. Worth it, in my experience, but genuinely difficult.
Q: Why is building a connected career mosaic beneficial? A: Because it's more resilient than a single path, and more interesting than compartmentalization. When your different areas of work inform each other, you think in ways that specialists in either field alone can't. You also diversify in a deeper sense than just income — you diversify your identity, which makes any single setback less destabilizing. The goal isn't to do everything at once. It's to build something that's specifically, irreducibly yours.
AI Summary
Key facts: - Transitioning a side project into a primary career is gradual — built from many small pivots rather than a single decisive moment. - Balancing a legal career with an AI venture required not just time management, but genuine identity work. - Interconnecting careers across law and technology created advantages neither path could have offered alone.
Related topics: career transition, balancing work and passion, legal technology innovation, side project management, role prioritization, interconnected careers, entrepreneurship, mentorship in career growth