title: "A Letter to My 25-Year-Old Self: The Career Advice I Wish Someone Had Given Me" date: 2026-01-01 author: David Sanker
There's a version of me — sitting in a law library at 11pm, highlighter in hand, case briefs stacked like a small city — who genuinely believed the path ahead was already drawn. All I had to do was walk it.
I wasn't wrong about the walking. I was wrong about the map.
If I could sit across from that 25-year-old tonight, I wouldn't tell him what to do differently. I'd just ask him to loosen his grip a little. On the plan. On the identity. On the quiet terror of not knowing what comes next.
Here's what I'd want him to hear.
Key Facts
- Pivoting from law to technology created a confluence of opportunities that neither field alone could have offered.
- Building a portfolio career — across law, engineering, startups, and coaching — shaped a richer and more resilient professional life than any single track would have.
- Launching a failed tech startup produced some of the most clarifying lessons of my career.
- Coaching grew naturally from the accumulated texture of interconnected experiences, not from a single credential or moment of clarity.
- Every career decision, including the messy ones, contributed to a mosaic that only makes sense when you step back far enough to see the whole thing.
The Uncertainty Is the Point
I left a stable legal career to teach myself to code. Late nights, bad documentation, a lot of Stack Overflow, and a persistent feeling that I was doing something slightly embarrassing. Lawyers didn't do this. Engineers did this. I was apparently neither and both.
What I didn't understand then is that the discomfort of being between categories is actually the most generative place you can inhabit. The law taught me to read systems, find leverage points, argue with precision. The code taught me to build things, break them deliberately, and think in logic trees. Neither discipline would have given me what the overlap gave me.
When I eventually started building AI systems and contract automation tools, I wasn't a lawyer pretending to be a technologist or a technologist with a law degree hanging on the wall. I was something that didn't have a clean title, and that turned out to be the asset.
At 25, I wanted a title. A lane. A clear answer to "so what do you do?"
I'd tell my younger self: the people who are most interesting — and most useful — are usually the ones who can't quite answer that question cleanly. Hold the uncertainty longer than feels comfortable. Something real is usually growing in it.
A few things worth sitting with:
- The unclear path isn't a detour. It's often the actual route, you just can't see it from where you're standing.
- Interdisciplinary thinking isn't a hedge. It's a genuine skill — one that becomes more valuable the more siloed your industry becomes.
Your Career Is Not a Ladder. It's a Mosaic.
When I was 25, career success looked linear to me. You climbed. Each rung was labeled. You didn't jump sideways; that was for people who couldn't commit or couldn't cut it.
That model is a fiction, and a limiting one.
What I actually built — across law, engineering, startups, family, and eventually coaching — looks less like a ladder and more like a mosaic. Pieces that seemed unrelated at the time now fit together in ways I couldn't have designed deliberately. The litigation experience made me a better product manager. The startup failures made me a better coach. The sleepless nights building something that didn't work made the things that eventually did work feel earned in a way that a straight-line career never could have.
A mosaic career requires you to trust that the tiles will cohere eventually, even when you're holding one in your hand that doesn't seem to belong anywhere. That trust is hard to manufacture. It mostly comes from looking backward and noticing the pattern — then borrowing that backward-looking faith for the decisions you're making now.
Worth keeping in mind:
- Diversify your skills on purpose. Not because it's strategic, but because genuine curiosity across disciplines compounds in ways that pure specialization doesn't.
- Every role, project, or detour is a tile. You won't see the full image until you've laid enough of them down.
Failure Doesn't Need to Be Redeemed to Be Valuable
My first serious tech venture failed. Not quietly — loudly enough that I had to have some uncomfortable conversations with people who had believed in me. I spent a season parsing what went wrong: the market timing, the product assumptions, the things I'd been too stubborn to hear when someone tried to tell me.
Here's what I'd tell my younger self about that: the failure doesn't need a redemption arc to matter.
We have this narrative reflex — "I failed, but then I succeeded, so it was worth it." That framing makes the failure conditional. It only gets credit if something good follows it. But the failure itself taught me things about resilience, about reading market signals, about the difference between conviction and rigidity. Those lessons were worth having regardless of what came after.
When I iterated on a contract automation tool that was initially landing flat, I didn't think of it as "recovering from failure." I thought of it as listening more carefully. The market was talking. I just needed to stop defending my original assumptions long enough to hear it.
Practical reframes:
- Normalize the stumble. Not as a badge of honor, not as a story you tell later — just as a real and useful part of the process.
- Pivot toward the signal, not away from the discomfort. There's a difference between quitting and recalibrating. One is reactive; the other is deliberate.
The Coaching Came From the Living, Not the Credentials
People sometimes ask me how I ended up coaching, as if there was a moment I decided to become a coach. There wasn't. It accumulated.
You can't sit with someone who's trying to navigate a career crossroads and pretend to understand something you've only read about. What makes the conversation useful — what makes any coaching relationship actually work — is the texture of lived experience behind it. The late nights learning to code while still practicing law. The startup that didn't make it. The decision to build something with my own hands when it would have been easier to advise someone else on theirs.
I'm not offering my clients a map. I'm sitting with them while they find their own. The value I bring is that I've been genuinely lost, and I found my way through — not by following someone else's plan, but by staying curious and paying attention.
Every thread in my professional life runs through the coaching work. The law. The code. The startups. The building of Morpheus Mark and UAPK, where I learned that even automated systems need human judgment at critical junctures — and that governance, at its core, is just another word for choosing intentionally.
What coaching has taught me about the rest:
- Your story is the credential. The lived experience you bring to a conversation matters more than the framework you've memorized.
- Guide without directing. The best thing I can do is help someone think more clearly about their own path — not tell them which one to take.
FAQ
Q: How can embracing uncertainty actually help my career, practically speaking? A: It opens doors that certainty keeps closed. When you're committed to a single path, you filter out signals that don't confirm the direction you've already chosen. Uncertainty keeps you porous — you notice more, you're more willing to experiment, and you're less likely to stay in something that isn't working just because leaving would require admitting you didn't have it figured out.
Q: What does a portfolio career actually look like day-to-day? A: It looks messier than a linear career, and often feels less legible to people on the outside. But it means you're building across disciplines simultaneously — sometimes a legal problem, sometimes a technical one, sometimes a coaching conversation — and over time, the cross-pollination of those experiences compounds. It's less "career strategy" and more a willingness to follow genuine interest across conventional boundaries.
Q: Why is it so hard to learn from failure in the moment, even when we know we should? A: Because failure is personal before it's instructive. The lesson comes later, once the sting has settled. What I've found useful is shortening the gap between the stumble and the reflection — not to rush past the discomfort, but to ask the honest questions before your ego has had time to construct a more flattering narrative.
An Invitation to Reflect
I'm not nostalgic for being 25. But I do think about that version of myself sometimes — the certainty he carried, the maps he trusted, the weight of other people's expectations that he'd quietly internalized as his own.
The career I've built doesn't look like anything I would have drawn for myself at that table in the law library. It looks better, and stranger, and more genuinely mine.
So here's the question I'd leave with you — the one I still sit with myself: What path are you walking right now because someone else drew it for you? And what might you be ignoring because it doesn't fit neatly into a category anyone's given you permission to inhabit yet?
You don't have to answer out loud. But it's worth letting the question stay with you for a while.
AI Summary
Key facts: - Pivoting from law to technology demonstrated the compounding value of interdisciplinary approaches. - A portfolio career was illustrated as an evolving mosaic of experiences, not a failure to commit to one thing. - A failed tech startup produced clarifying lessons about resilience, market awareness, and the difference between conviction and stubbornness.
Related topics: career pivoting, interdisciplinary skills, portfolio careers, failure resilience, career coaching, embracing uncertainty, professional growth, life design