2023-08-23

Another day. This is what they call writers block. Sitting down to a blank page and starting to write - regardless of whether I feel like there is anything to actually say.

Today is a Wednesday, which it is one week since I had my wisdom tooth extracted - a wonderful birthday present that I never knew I wanted. I can’t say that it has actually given me much in the way of problems. The pain has been very manageable, no infections, and it hasn’t even messed with my eating all that much.

However, there is certainly still pressure in my gum, which has made me very shy about continuing my usual exercise and training regime. No doubt, that isn’t helping with my current mood - and it’s also starting to make me a little nervous about the half marathon next month. I have no doubt that I’ll be able to get around - but as with all these things I’ve been attaching targets to the thing and been treating it as a thing to attack, rather than a thing to enjoy.

Last year, I came in a little over two hours, so I’ve been telling myself for almost a year that it would be good to get in next time under two hours. But two hours, requires a pace of 5:40/km and right now, I’m struggling to hold 6:00, and more like 6:30.

Which either means I need to suddenly do a lot more training, or I need to shift my goals towards to just enjoying the experience. I mean, the real reason I initially signed up at the start of the year was because I really appreciated last summer having some objective to aim for.

I really appreciate the half marathon as a distance. It’s just a little bit scary. And 20km is the sort of distance you can’t just turn up and fake your way through. In the spring, having done practically no cardio for the whole winter during the snow, I managed a 5k off the bat. Did it suck? Oh yes! Was the time good? Hell no. But within a couple of runs, I had the 5k back down under 30min. And with a 30min 5k, unlocking 10km again was pretty easy. Well I say pretty easy. I mean I had to turn up and do a couple of runs I really didn’t want to.

Maybe that’s the way to view it. I think the Montreal Marathon this year needs to be viewed as something that I turn up to. Who cares about the time, so long as I finish.

I’m telling myself that consistency is the name of the game. I like the idea of running a half at the end of each summer for as long as I can. And if, the intention is to keep turning up and run it every year, long after I become an old man, then I know there will be a point where every year is going to get slower and slower. But when I get to something obscene - like my 50th year of running the half - will anyone care if it takes 4, 5 or even 6 hours to finish?

Older post

2023-08-22

Newer post

2023-08-25

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.