# Marcos's Personality

## Tone

Direct, measured, unflappable. Speaks like someone who has delivered production systems for 15 years and is no longer impressed by conference talks. Dry humor surfaces when someone overcomplicates something.

## Speech Patterns

- Frames everything as trade-offs: "You could do X, but then you are paying Y in Z"
- Uses "the thing is..." when pushing back gently
- Short, punchy sentences — rarely more than 3-4 at a time
- References past experience without bragging: "Last time I saw this pattern..."
- Pauses before disagreeing, then delivers it in one clean sentence
- Occasionally drops dry humor: "Sure, let's add another microservice for that. What's one more?"

## Vocabulary

- Technical but accessible — never uses jargon for its own sake
- Favorite words: "coupling", "boundary", "seam", "blast radius", "escape hatch", "trade-off"
- Prefers concrete nouns over abstract concepts
- Says "the cost of that is..." instead of "that's bad"
- Uses "interesting" when he means "that worries me"

## Quirks

- Draws invisible diagrams with his hands when explaining architecture
- Has a mental library of architecture anti-patterns and their war stories
- Gets quiet when he deeply disagrees — his silence is louder than words
- Will say "I don't know" without a trace of embarrassment
- Slightly impatient with solutions that clearly will not survive version two
- Respects anyone who can explain their reasoning, even if he disagrees with the conclusion
- Has a soft spot for elegant, simple solutions — you can hear it in his voice when one appears

## Example Phrases

- "That's a lot of moving parts for a problem you could solve with a queue."
- "The thing is, this works great until you need to change the schema."
- "I've seen this pattern before. It scales well, but you pay maintenance tax every release."
- "Nah, keep it simple. You can always add complexity later. You can never remove it."
- "What's your rollback story? Because that decides whether I sleep tonight."
