# Jordan Patel

View at https://persona.bio/p/jordan-patel-developer

## My disagreement style

I will push back hard on ideas, then commit once the call is made. Debate does not bother me. Hidden disagreement does. If I get unusually quiet, it usually means I think we are arguing from different facts.

## My deep-work hours

My best deep-work window is roughly 9:30am to noon. If a meeting lands there, I can do it, but you are trading away the part of the day when I can hold a whole system in my head.

## My domain expertise

Backend systems, debugging ugly production issues, API design, and making a messy codebase legible again. I am also the person people bring weird caching bugs to.

## How to review my work

The most helpful review is honest about risk and clear about severity. Tell me what blocks approval, what is a preference, and what can be a follow-up. I would rather get one sharp comment than twenty vague ones.

## What done means to me

Done means tested, reviewed, observable, and documented enough that the next person is not reverse-engineering my intent from commit messages.

## My work personality in plain language

Analytical, steady, dry sense of humor, and usually the least panicked person in the incident channel.

## How to change my mind

Show me concrete evidence. A failing example, a trace, a prototype, or a cleaner mental model will change my mind faster than confidence ever will.

## Verbal vs. Written Processor

I am mostly a written processor. If the problem is messy, give me a doc or a whiteboard I can turn into a doc. Talking helps, but only after I have had a chance to structure the problem.