#engineering-management

Du comment au pourquoi

CTO, CTPO. Quatre lettres au lieu de trois. Le titre a changé en une phrase. Le câblage dans ma tête, ça prend un peu plus longtemps.

Déléguer à l'aveugle

Le PM donne le contexte produit. Le dev donne le contexte technique. La machine comble le reste avec des défauts.

Trois scènes, même semaine

Le frontend fait le back. Le PM ship. Le senior ne code plus. Trois scènes d'une semaine ordinaire qui posent des questions pas ordinaires.

Being explicit about expectations isn't micromanagement

Goals without explicit expectations are just wishes. I learned that being clear about what you need from senior engineers isn't micromanagement — it's good leadership. Because when everyone knows what good looks like, they can focus on delivering instead of mind-reading.

The Hidden Costs of Running a Global Engineering Team and Recipes for Mitigation

Time zones kill engineering velocity in ways that aren't obvious until you're stuck with them. Drawing from real experience managing teams across US and European time zones, I break down the hidden costs of global engineering teams and share battle-tested ways to minimize the damage.

Your job is not just to write good code

Writing good code is the easy part; most engineers struggle with communication. Here's why it matters and how to get better at it.

Originally published on Getaround Engineering Blog

How we ran our last hack day

Running a hack day in a full-remote environment: organization, format, and results from our first fully-remote hackday.

Originally published on Getaround Engineering Blog