2023-10-10

A little bit of an extended hiatus. It just goes to show how fragile some of these do-good habits are. Like meditation, language learning or healthy eating. The only way I have stuck with any of them is through a sheer grit and determination. Not truly because I actually ever incorporated these things into my like. They never became autonomous.

I bit like flossing. I’ve had the dentist lecture me incessantly for a decade or more and only in the last two times I’ve been to the dentist they didn’t mention it. Either because the flossing was finally self evident or perhaps the other horrors of my mouth didn’t allow for enough air time to get through the flossing lecture as well.

My point is, that was after a fairly concerted effort to floss my teeth every other night - I was being realistic. I knew that there was no way that I was ever going to achieve nightly flossing so I tried to just not go two consecutive nights without it.

And yet, and yet, a week in Mexico and it’s all shot to pieces. I managed to even get a quickie floss or two during Mexico but the habit was broken.

And really at this point I don’t know why I’m persisting with the flossing metaphor when I’m really talking about journaling. The week in Mexico was easy to justify. I completely unplugged for a week. No WiFi. No cell reception. I did take the phone for the sake of emergency check ins for the flight and I took a few pictures, but I was very proud to never unlock my phone in Mexico.

The objective was to completely unplug, and I knew there was no “dipping the toe in” option. An internet connection for the weather, enables the pop ups and notifications. The family WhatsApp group and pictures of parents in Spain quickly turns into checking email. And then I’m replying to work email on the beach. No thanks.

But the downside to going offline entirely was not my journaling options were limited. I mean I could have used a pen and paper. Maybe even transcribed it later if I wanted to. But I didn’t.

And then when I got back, I was sick, had Covid and I was at a research conference with odd hours. Much to do, and few hours to do it.

It was all too easy to justify not journaling for one more week until life went back to normal. But then it was a long weekend. was still sick. The in laws sick too. So now I’m solo parenting two boys, a dog, whilst still feeling pretty sick.

Now there’s no denying it. Back in the office today. Back to reality. So here I am. Making the effort. Doing the hard thing. The hardest part is always starting.

And maybe that’s the learning in all of this. Maybe the secret to being successful in all of this is acknowledging that habits will break. You will fall. But it’s the picking yourself up and starting again. Looking yourself in the mirror, knowing that you might have lost some progress and starting again anyway.

Older post

2023-09-21

Newer post

2023-10-11

How do you define successful engineering leadership?

The Philosophy

Many view technical leadership as being the “smartest architect in the room.” I see it as the opposite. My job is to build a room where I don’t have to be the smartest person because the systems, culture, and communication are so robust that the team can out-innovate me.

The Strategy

  • Alignment: Does every engineer understand how their sprint task impacts the company’s bottom line?
  • Velocity vs. Stability: We aren’t just “shipping fast”; we are building a predictable, repeatable engine that doesn’t collapse under its own weight at the next order of magnitude.
  • The Human Growth Curve: Success is when the engineering team’s capability evolves faster than the product’s complexity. If the team feels stagnant, the tech stack will soon follow.

What is your approach to scaling technical organizations?

The Philosophy

Scaling isn’t just “hiring more people” - that’s often how you slow down. Scaling is about moving from Individual Heroics to Organizational Systems.

The Strategy

  • The 3-Continent Perspective: Having managed global teams, I focus on “High-Signal Communication.” As you grow, the cost of a meeting triples. I implement “Asynchronous-First” cultures that protect deep-work time while ensuring no one is blocked by a timezone.

  • Modular Autonomy: I advocate for breaking down monolithic teams into autonomous units with clear ownership. This reduces the “communication tax” and allows us to scale the headcount without scaling the bureaucracy.

  • Automation as Infrastructure: At petabyte scale, manual intervention is a failure. I treat the developer experience (CI/CD, observability, self-service infra) as a first-class product to keep the “path to production” frictionless.

How do you balance high-growth velocity with technical stability?

The Philosophy

Technical debt isn’t a “bad thing” to be avoided; it’s a set of historical decisions that no longer serve you. Like any loan, leverage can accelerate growth when investments payoff. But if velocity and returns are slowing you need a payment plan before the interest kills you.

The Strategy

  • The ROI Filter: I don’t refactor for the sake of “clean code.” I don’t refactor a micro-service with no users. I refactor when the pain on that debt - measured in bugs, downtime, or developer frustration - starts to exceed the cost of the fix.

  • Zero-Downtime Culture: Especially at scale, stability is a feature. I implement “Guardrail Engineering” where the system is designed to fail gracefully, ensuring that a Series B growth spike becomes a success story rather than a post-mortem.

  • The 70/20/10 Rule: I typically aim to dedicate 70% of resources to new features, 20% to infrastructure/debt, and 10% to R&D. This ensures we never stop innovating, but we never stop fortifying either.