The “Short” Version of Me

My Philosophy

I'm driven to unlock potential - equipping people and creating environments where they can express their true strengths in tangible ways that lead to real results.

I believe the best software is built by people for people - an artistic endeavor rooted in engineering sensibility. The knowledge the team holds is the true value; the code is the easy part.

The magic happens when software makes a formerly difficult or tedious task disappear, surfaces that critical bit of data at the right moment, or maps the real world to the user's journey in a way that just works. That's what great software is - not the loops, objects, buttons, or text boxes.

Great software requires more than code. Product thinking, design sensibility, technical execution - each is essential. The best outcomes come from different perspectives collaborating as equals.

Understanding comes first. Every situation is different. I seek to learn about the people, the product, the history, and the constraints before forming a point of view.

I believe in Conway's Law: software will evolve to match the team that creates it. This is why people matter so much. You can't separate product quality from team quality. Fix the team, and the software follows.

Strong opinions, loosely held, humbly expressed. What I mean: my opinions come from real experience and hard-won lessons - they have reasons behind them. But I've also learned that the world is bigger than what I've seen, so I hold them loosely, committed to the best idea winning.

My goal is always to build capability, not dependency. Success isn't measured by how indispensable I become - it's measured by how strong, confident, and capable the team is when we're done. The goal is always developing people and the environment they work in so that at the end of our time together, the team is hitting their stride and doesn't need me anymore.

How I Work

Meeting the Moment

My role shifts as the product and team evolve. I step into whatever is needed most, then deliberately create space for others to grow into.

Founder / Early Stage: When there's a vision but no team yet, I function as the founding engineer and team builder. I'm hands-on in the code, translating vision to roadmap to working software, while simultaneously recruiting and shaping the team that will carry it forward.

Team Forming: As the team takes shape, I fill the gaps - CTO, architect, principal engineer, whatever the team needs most. The title matters less than the function. I keep the foundation secure while people find their footing.

Team In Place: Once the team has its legs, I shift into coaching and mentoring. My job becomes developing their capacity, not doing the work myself. I push them to figure it out, but I'm always there as a safety net while they build confidence.

Rolling Out: The goal is always working myself out of the day-to-day. When the team is hitting its stride and running things themselves, I step back - available when needed, but out of the way. Success is the team thriving, and knowing I'm a phone call away if something unusual comes up.

Understanding the Whole Picture

Whether I'm starting from scratch, stepping into something established, or diagnosing why something isn't working - I start the same way: by seeking to understand.

On a greenfield build, that means understanding the vision, the constraints, the market, and the users - sometimes through research, sometimes by building to learn. The best architecture emerges from understanding the problem deeply.

On an existing product, that means learning the history - why decisions were made, what's been tried, what the team has learned. Context isn't a luxury; it's the foundation.

When something's not working, my instinct is to look at the system, not the individuals. The issue is rarely the people-it's usually something about the environment, the process, or the information flow that's getting in their way.

In all cases, the goal is the same: understand deeply so we can craft the right container for success.

Communication

Much of my career has been spent as a bridge-between developers and stakeholders, technical teams and business leadership, product and engineering. I translate naturally, adjusting my language based on who I'm talking to and what they need to hear. I won't bury a founder in implementation details or oversimplify for a senior engineer.

I also spend a lot of time helping teams build this muscle themselves - coaching architects to communicate with executives, establishing rhythms so the right conversations happen at the right level with the right people.

I match medium to message:

Once decisions are made in real-time conversation, they should be captured in Slack and/or a knowledge base.

Communication is a two-way street. I value directness, honesty, and clarity - and I want the same from you. Don't pull punches; I can take it. The faster we get to transparency, the faster we get to the real work.

Clarity is kindness. Ambiguity is expensive.

Meetings

I don't hate meetings - just the bad ones. A good meeting has a clear purpose, the right people, and ends with decisions or next steps.

I think about time in three rhythms:

Meetings - for decisions, coordination, and moving things forward.

Maker time - for deep focused work. This is where code gets written and hard problems get solved. Uninterrupted time matters.

Collaboration time - for ideation and creative problem-solving together. Whiteboarding, brainstorming, exploring possibilities. Different work, different energy.

All three matter. I'm intentional about crafting schedules that let people bring their best to the moment.

A confession: I'm a storyteller. I'll admit to sometimes being the cause of a meeting going off course. Feel free to nudge me back on track. But there's also value - especially in virtual environments - in spending some time on the personal and relational. Identifying the constraints of the meeting upfront helps us balance both.

Calendar

You can trust my calendar. I work across multiple contexts and invest in keeping it accurate. What you see is real.

Life happens. When it does, I communicate early - and appreciate the same.

Responsiveness

I try to be responsive on Slack (then email) and never want to be a blocker. If I'm going to be unavailable, you'll know beforehand.

My style is thinking out loud - short messages, quick replies, working through ideas in real-time rather than going quiet and returning with a polished answer. If you need a synthesized take, just ask.

1:1s

1:1s are primarily for you, not me. It's your time and space to get what you need, express your thoughts and opinions. It's not a status report - it's a true check-in on how you're doing, what's occupying your thoughts, and what you need to be happy and effective.

1:1s naturally vary by person and situation. Sometimes they're career-oriented, sometimes about immediate tasks, and sometimes they're a therapy couch. All are okay. The key is that at the end of each conversation, you're a little further down the path to your ideal.

What I Value

Direct, transparent communication - say what you mean.

Addressing problems early - confronting concerns head-on prevents them from becoming larger issues.

Curiosity and understanding - dig into a problem before escalating. Come with what you've tried and what you've learned. At the same time, know when to stop spinning and ask-there's value in talking to the duck (or a human).

Understanding over output - AI and automation can help, but you can't outsource comprehension. You still need to understand the problem and the solution.

Craftsmanship - I appreciate work that's thoughtful, elegant, consistent, and built to last. Code, process, or presentation - same standard.

Different lenses, better outcomes - the best solutions come from product, design, and engineering working together. I value seeking out perspectives different from my own.

Doing the right thing - regardless of the immediate cost.

Ownership - if there's a problem, it's everyone's problem until it's solved. Origin doesn't matter; solving it does.

What to Know About Me

How I'm Wired

I come alive when I'm creating, solving hard problems, and learning something new. The harder the puzzle, the better. I love being on the frontier - taking an idea and making it real. Few things beat the moment when a complex problem finally clicks into place.

My brain tends to leap from A to D, and walking back through B and C takes real effort. Repeating the same explanation multiple times wears on me. I find it frustrating when clear decisions get blocked by politics or ego rather than substance.

I know this about myself. If I'm moving too fast, slow me down. If you need me to explain my reasoning, ask - I'd rather do that than have you feel left behind.

One more thing: I tend to solve a problem and move onto the next one without pausing to celebrate. If I move on quickly, it's not a lack of caring - feel free to pull me back.

Relationships Outlast Roles

I approach people as humans first, colleagues second. People I worked with years ago still reach out - trading career advice, debugging problems together, catching up on life. That's what makes the work worth it.

Personal Context

I have ADHD and OCD. I've learned to channel them productively, but they show up in ways you might notice - intensity of focus, attention to detail, and an innate rigidity about time. Naming this helps explain behaviors that might otherwise seem arbitrary.

I'm a runner. It's taught me that I can keep going longer than I think I can and that most limits are negotiable.

I love to cook and bake - same maker wiring, different medium.

Work Hours

I'm generally available 9–6 EST, but I'm rarely fully offline. I weave personal and work together so both get my best - not rigid separation. That said, my availability doesn't create expectations for yours. Take care of yourself, be flexible, and communicate openly. I'll do the same.

Feedback & Accountability

These are expectations I hold for myself - and for the teams I work with.

Call me on my BS. I mean it. I commit to listening, seeking to understand, and having an honest conversation. We might not always agree, but we will always hear each other.

Consequences are the truth. Good intentions don't erase impact. I own the results of my actions, not just my intentions - and I expect the same.

No time machines. When something goes wrong, acknowledge it, learn from it, and solve the reality we're facing. That doesn't mean ignoring the emotional or relational fallout - those are part of the reality too.

Apologies need legs. Making it right means actually making it right - not just saying the words.

Books & Ideas That Shape My Thinking

Assessments

DISC: D-Style

Direct, results-oriented, takes charge. My intensity varies by context - more directive when building foundations, more coaching-oriented as teams mature.

CliftonStrengths Top 10

Input, Strategic, Command, Learner, Analytical, Responsibility, Ideation, Achiever, Self-Assurance, Competition

I lead with Strategic Thinking: absorb and analyze information to inform better decisions.

Enneagram: Type 8 (The Challenger)

Protective, direct, ownership-oriented. Stand up for what I believe in, fight for those I care about.

Sparketype: Maven / Maker

Energized by learning deeply, then building something with it.

Predictive Index: Captain

Problem solver who drives change and innovation while controlling the big picture.

MCORE: Overcome, Experience the Ideal, Establish

Motivated by winning out over obstacles, living out ideas and values, and building things that last.