← All articles

How to Work With Me

A personal guide to my working style, communication preferences, and collaboration approach.

This is a guide to working with me — what I value, how I communicate, and what to expect when we collaborate. I'm writing it because I've found that explicit working agreements save everyone a lot of unnecessary friction.

How I think about problems

I'm a systems thinker. My first instinct when I encounter a problem is to understand the full context before proposing a solution. I'll ask questions that might seem tangential — they're usually not. I'm trying to understand the root cause, not just the symptom.

If you give me a task and I push back with questions before starting, that's not resistance — it's due diligence. I'd rather spend 20 minutes understanding the problem correctly than 4 hours solving the wrong one.

Communication style

I prefer written communication for anything that requires a decision or has lasting implications. Not because I don't like talking — I do — but because writing forces clarity and creates a record.

I'm responsive during working hours and I try to set clear expectations when I'm blocked or need time to think something through. I'll tell you if I need more context. I won't silently stall.

On feedback

Give it to me directly. I don't need it softened. I'd rather know clearly what's not working than receive vague positive reinforcement followed by confusion later.

I'll do the same for you, calibrated to what I know you prefer. If you haven't told me how you like feedback, I'll default to direct and specific.

What slows me down

Ambiguous requirements with no room to ask questions. Last-minute changes to agreed-upon scope. Decisions made without the people who'll implement them. Context being withheld that would have changed my approach.

If you see me going quiet or slower than usual, check in. Something's probably off and a quick conversation fixes it faster than waiting.

What energizes me

Ownership. I do my best work when I understand why something matters and have real latitude to figure out the how. I'm not someone who needs to be managed closely — I need to be trusted and given good problems.

I also genuinely enjoy working with people who care about craft. The kind of teammates who notice when something could be done better, even when "good enough" would have shipped just fine.

Continue reading

Mar 15, 2025

Becoming an AWS Cloud Practitioner

My journey studying for and passing the AWS Cloud Practitioner certification.

Read more →

Mar 10, 2025

How to Work With Me

A personal guide to working style, communication preferences, and collaboration approach.

Read more →

Feb 20, 2025

Write Robust Code

Principles and practices for writing code that is reliable, maintainable, and resilient.

Read more →