Technical Team Management
Technicians are a special breed. We speak in code, dream in architecture, and communicate in a language that sounds like alien to outsiders. I know because I'm one of them. I've led teams of brilliant weirdos—people who see patterns others miss, who debug at 3am because the problem is beautiful, who speak in memes and think in abstractions. My job isn't to change you. It's to give you the space, the trust, and the coffee to do your best work.
Grow Developers. Build Tech Teams. Create Legacy.
I don't just manage people. I grow them. One-on-ones that matter, code reviews that teach, and opportunities that challenge. I create environments where questions are welcomed, where 'I don't know' is the beginning of discovery, and where everyone understands not just the what but the why. Former team members still reach out years later to bounce ideas off me. That's the legacy I care about.
We Speak Alien. That's Our Superpower.
Let's be honest: technical teams are different. We communicate in pull requests, not meetings. We solve problems while staring at terminals. We laugh at jokes that make normal people uncomfortable. I don't try to make you normal. I create environments where your weirdness is an asset, not something to hide. Because the best code comes from minds that think differently.
How I Manage (Without Killing the Vibe)
- Context, Not Commands — I tell you why we're building it, not just what to build. Your brain is better than mine when it knows the goal.
- Trust — I don't watch your screen. I trust you to deliver. Most of you will exceed expectations. The few who don't? We talk. Privately. Honestly.
- Protect the Weird — Jira tickets? I shield you. Scope creep? I fight it. Meetings that could be emails? I cancel them. You focus on code. I handle the noise.
- Celebrate — That bug you killed at 2am? I know. That elegant solution nobody noticed? I saw it. I celebrate the quiet victories that only technicians appreciate.
The Alien Language (And Why It's Beautiful)
Technical teams have their own dialect. I speak it fluently:
- Pull Request Poetry — Not just code reviews. Teaching moments. Celebration of craft. I read every PR. I learn from them. So does the team.
- Dark Humor & Memes — Debugging is trauma bonding. We laugh at the chaos. We meme our failures. It's how we cope. It's how we connect. I'm here for all of it.
- Technical Debates — Architecture wars. I encourage healthy debate. The best solutions survive the fire of passionate disagreement.
- Shared Obsession — We don't just work. We obsess. We dream in code. We wake up with solutions. I don't manage that obsession. I nurture it.
What My Teams Say (Or How I Know It Works)
- "First boss who actually reads my code, not just my status updates." — Mariano, Technical Leader
- "He gets us. The weirdness, the late-night debugging, the memes. He's one of us." — Aitor, Fraud Expert
- "I've never had a manager who trusted me this much. It made me want to do my best work." — Thomas, Project Manager
- "He shields us from the noise. I can actually focus on code." — Albert, Junior Developer
Context, Not Commands
I tell you why. You figure out how. Your brain is better when it knows the goal.
Protect the Weird
Jira? I handle it. Meetings? I cancel them. You focus on code. I handle the noise.
Trust, Not Micromanage
I don't watch your screen. I trust you to deliver. Most of you exceed expectations.
Celebrate the Quiet Wins
That bug you killed at 2am? I know. I celebrate the victories only technicians understand.
