title: "A Day in My Life: Navigating Three Worlds from Dawn to Dusk" date: 2026-01-30 author: David Sanker
There's a particular kind of quiet at 5:47 in the morning — before the kids wake, before the notifications start, before the day makes its demands. I sit with my coffee and a stack of case files, and for a few minutes, the three worlds I inhabit feel less like competing claims on my time and more like different instruments in the same piece of music. They don't always play in harmony. But when they do, something clicks that I struggle to describe any other way.
I'm a lawyer. I'm an engineer. I'm a coach. On most days, I'm all three before dinner.
People ask how that works. Honestly, some days it doesn't — not gracefully, anyway. But I've come to believe that the friction between these identities is less a problem to solve and more a signal to pay attention to. The discomfort of context-switching, the mental effort of holding legal logic in one hand and algorithmic thinking in the other — that tension has taught me more about myself and the people I work with than any single career ever could.
TL;DR
- How legal, engineering, and coaching work actually coexist in a single day
- Practical strategies for managing transitions between demanding, distinct roles
- Why the overlap between these worlds creates value that no one of them could alone
Key Facts
- The author practices law, builds software, and coaches — often within the same calendar day
- Legal and compliance work gets the sharpest morning hours
- Engineering and technical execution picks up after lunch
- Coaching sessions happen in the evening, where the day's accumulated thinking gets distilled into conversation
- GDPR compliance has been directly integrated into client tech workflows, requiring both legal and engineering fluency simultaneously
Morning: The Legal Mind at Work
The law rewards early risers, or at least it rewards people who read carefully before the rest of the world starts talking.
My mornings are reserved for legal work — case files, regulatory updates, drafting, correspondence that requires precision rather than speed. There's something about that first hour before the house wakes up that suits contract review and statutory interpretation. The mind is clean. There's no residue from a hundred small decisions yet.
A recent morning looked like this: a tech client needed their data handling practices updated to reflect the EU's General Data Protection Regulation. On its face, that sounds like a pure legal task — read the regulation, advise on compliance, done. But GDPR doesn't exist in the abstract. It lands inside actual systems, actual databases, actual engineering choices someone already made. So the morning wasn't just about legal research and drafting advice notes. It was about understanding the client's technical architecture well enough to know where the regulation actually touched their workflow.
That's where having an engineering background matters. I'm not just translating legal text into plain language — I'm mapping it onto code, onto data pipelines, onto decisions their developers made eighteen months ago when nobody was thinking about Article 17 right-to-erasure requirements.
By the time most people are on their second coffee, I've laid the legal groundwork and I know what the afternoon will need to address.
Afternoon: Shifting into Engineering
There's a ritual I've developed for the transition from legal to technical work. I close every browser tab. I make a second cup of coffee. I sit for about three minutes doing nothing in particular.
It sounds small. But the mental shift from legal reasoning — where precision and precedent govern everything — to engineering thinking — where you're trying to build something that actually runs — is more demanding than it looks. The modes are genuinely different. Law asks: what does this mean? Engineering asks: what does this do?
Post-lunch, I'm usually in code, architecture diagrams, or technical problem-solving. The afternoon's challenge often runs parallel to the morning's legal work, which is part of what makes the overlap generative rather than exhausting. That same GDPR project, for instance, required designing an anonymization layer for a machine learning pipeline — structuring data collection so that user information could still train predictive models without exposing personal identifiers. That's simultaneously a legal problem, an engineering problem, and a design problem.
I couldn't solve the engineering piece without understanding the legal constraints. I couldn't have advised on the legal piece without understanding what the engineering would and wouldn't support. The lawyer in me kept asking: does this hold up? The engineer kept asking: does this actually work?
That conversation between the two — happening inside a single person, in real time — is, I think, the thing that makes the interdisciplinary path worth the complexity.
Evening: The Coaching Hour
By the time evening arrives, something has shifted. The transactional work of the day — the analysis, the building, the problem-solving — gives way to something harder to quantify but just as real.
Coaching is where the day's learning gets tested against human experience.
I work with people navigating career transitions, professional identity questions, the particular vertigo that comes from being good at multiple things and not knowing which one to commit to. I know that vertigo. I've lived inside it. And there's something about arriving at a coaching conversation after a day that has already moved through law and engineering — I'm not speaking theoretically. I'm drawing on decisions I actually made that day, trade-offs I actually wrestled with.
The best coaching sessions I've had aren't the ones where I dispensed wisdom. They're the ones where something a client said caused me to see my own experience differently. A person trying to decide whether to leave a stable legal career for a tech role will ask me something, and in trying to answer honestly, I'll understand my own path a little more clearly than I did that morning.
That's what the evenings give me. Not just the chance to help someone else think through their choices, but a mirror that keeps my own self-knowledge current.
The Part Nobody Talks About
Let me be honest about the difficulty, because it's real and I don't want to romanticize it.
Context-switching at this level is cognitively expensive. There are days when the three worlds don't feel like harmony — they feel like three people pulling in three directions. Time-blocking helps. So does treating the transitions as actual events rather than just moving from one browser window to another. Mindfulness practices that I once thought were soft now strike me as basic cognitive hygiene.
What I've learned is that the challenge isn't managing three separate identities. It's maintaining the coherence of one person who moves through three domains. The thread running through the morning's legal work, the afternoon's code, and the evening's conversation is me — my values, my curiosity, my particular way of seeing problems. When I lose that thread, the day becomes fragmented and exhausting. When I hold it, even the friction feels purposeful.
Key Takeaways
- Work with your energy curve. Legal analysis gets my sharpest hours. Engineering gets focused blocks after lunch. Coaching gets the evening, when I'm thinking in stories rather than arguments.
- Let the roles talk to each other. The legal insight often improves the engineering decision. The coaching conversation often clarifies the strategic question. The separation between the roles is artificial — the integration is where the value lives.
- Transitions are real work. Don't underestimate the cost of switching modes, and don't skip the mental rituals that help you shift.
FAQ
Q: How can someone effectively balance multiple professional roles like lawyer, engineer, and coach? A: The honest answer is: imperfectly, and by design. The key is assigning each role its own time and protecting those blocks genuinely. Transitions matter — give yourself actual space to shift modes rather than multitasking between identities. And pay attention to which role energizes you and which one drains you at different points in the day. That information is worth more than any productivity framework.
Q: What strategies can lawyers use to integrate legal knowledge with engineering? A: Start by learning enough about engineering workflows to understand where legal questions actually land. You don't need to be a developer, but you need to understand how data moves, how systems are built, and where compliance requirements create real constraints rather than abstract ones. The lawyers who add the most value in tech contexts are the ones who can speak both languages — not fluently in both, but conversationally enough to be useful.
Q: How does coaching add value to a day already filled with technical and legal tasks? A: It keeps me honest. Legal and engineering work can become very interior — it's easy to spend a day entirely inside your own head. Coaching forces me into genuine dialogue with another person's experience. It's less about what I know and more about what I can help someone else see. That shift in orientation is, paradoxically, what keeps my own thinking fresh.
Where This Leaves Me
I don't think the three-worlds life is for everyone, and I'd never suggest it is. Some of the most fulfilled people I know found one thing and went deep. That's a legitimate path — maybe the more sensible one.
But for those of us who keep finding ourselves at unexpected intersections, who trained for one thing and got curious about three others, who keep saying yes to the less obvious opportunity — there's a different kind of coherence available. Not the coherence of a single clear identity, but the coherence of a person who has learned to carry multiple truths without dropping any of them.
Most mornings, that feels like enough.
What does your own version of this look like? Are there parts of your professional life that feel like they're in conversation with each other — or parts you've been keeping carefully separated that might actually belong together?
I'm curious what you're navigating.
AI Summary
Key facts: - The author practices law, builds software, and coaches clients — frequently within the same day - Morning hours are reserved for legal work; afternoons shift to engineering; evenings are dedicated to coaching - GDPR compliance work served as a case study in combining legal and technical expertise simultaneously - The post explores the cognitive and personal cost of context-switching alongside its generative benefits
Related topics: legal tech, time management, career transitions, GDPR compliance, interdisciplinary careers, coaching, productivity, professional identity