“Face the sunshine, and forge a path in the uncharted wilderness.”

This manual is designed to reduce communication friction and help us collaborate effectively. After the crucible of leading 250+ person enterprise engineering teams, I am embracing an open-minded approach toward my next career chapter, seeking a team with aligned values and a shared desire to drive real-world impact through emerging technologies. Even as my context may evolve, my underlying engineer’s soul remains unchanged. This is a living document based on my 20+ years of experience, reflecting my current operational state and expectations.

🌟 Core Philosophy & Vision

  • Embracing Ambiguity & Action Speaks: When exploring the frontiers of emerging tech (like AI, Robotics, and Cyber-Physical Systems), the map is rarely drawn out. I deeply value resilience and tangible execution when facing the unknown. Tell me what we can do, rather than just pointing out what’s broken.
  • Fairness Cares: I deeply value fairness. I will intervene if team members are treated unfairly or if actions negatively impact the collective good.
  • Empowerment & Psychological Safety: I detest micromanagement. I provide context and expect you to take the steering wheel. We are navigating the unknown together; honest mistakes are an acceptable part of exploring the frontier. Watching you take ownership and grow is my greatest satisfaction.

⚙️ Technical Philosophy & Dev Culture

  • Architectural Thinking (DDD): I have a strong bias toward Domain-Driven Design (DDD). I appreciate systems that are structured, loosely coupled, and accurately reflect real-world business realities.
  • Exploring Technical Frontiers: Shipping the feature is only the baseline; pushing boundaries is the goal. I encourage deep curiosity and practical exploration of edge tech (e.g., Zig, Zenoh, DePIN, IoT).
  • AI-Driven Workflows: I actively embrace AI. Don’t cling to traditional, tedious processes; I expect teams to leverage AI tools to multiply their productivity, reserving human brainpower for problem prevention and the hardest architectural judgments.

💬 Communication & Working Preferences

  • Async & Efficiency First: Much like my preference for self-hosted infrastructure, I prefer crisp documentation over lengthy, inefficient meetings. However, for urgent matters, a direct Slack Huddle or Face-to-Face conversation is always preferred over lengthy emails.
  • Be Straight & Open Minded: I prefer difficult, honest conversations over unspoken issues. I view all feedback as a learning opportunity; please be direct and offer specific suggestions.
  • Deep Processing & Quiet Concentration: As an introvert, I work best in quiet environments for solving complex problems. If I am silent in a meeting, it rarely means I disagree—it means my brain is compiling in the background to find the optimal solution. My calendar is open; book time whenever you need to collaborate.

⚠️ My Struggles

  • Elegant Architecture vs. Speed to Market: My engineer’s instinct constantly craves the “most elegant architecture,” but driving meaningful real-world impact often demands rapid iteration and speed to market. I battle this trade-off frequently. If you notice me over-engineering when we just need a quick MVP, please call me out directly.
  • Impatience with Inefficiency: I have a very short fuse for illogical discussions or administrative friction. If I come across as cold or rushed, please bear with me—or better yet, propose a much more efficient resolution right on the spot.
  • The Poker Face: I don’t wear my emotions visibly, which can sometimes be misread as negative. Rule of thumb: if I’m unhappy, I will say so directly; otherwise, assume the system is running smoothly!

🗂 Collaboration Deep Dive

(Detailed content for the following sections will be progressively updated)

Input & Output

How I receive information, how long I need to react, and how I give feedback.

Meeting Manifesto

What an efficient and effective meeting looks like to me.

Asynchronous First

Why I value documentation over verbal instructions.

Human Sensor

Acknowledging my blind spots in emotional perception and inviting partners to complement me.

Technical Standards

My bottom line for Code Quality and DDD (Domain-Driven Design) practices.