2023-08-25

The Bye family (possibly annual) retreat, that I decided to call it as of about 5 seconds ago is going astoundingly well. The search criteria was to have it within about an hour of the city and to have as little fuss as possible.

Therefore to find an almost inclusive hotel across the road from a supermarket, small water park and a small amusement park seemed like just the ticket.

But true to Murphy’s Law, the gods have smiled upon me trying to make a plan and a small amount of rain resulted in a tiny notice on the website of amusement and water parks not being open today. Hilarious! A water park that won’t open due to a light drizzle.

That’s the sort of confused logic that I could expect “everything is not that bad” England. But I thought the Canadians would be made of sturdier stuff.

Challenging to go walkabout with one child that would eternally prefer to be on my shoulders and another that despises the idea of being physically unattached from iPad with another less than a broadband connection. And that was before the rain, and the sub 14 degree weather.

I mean it’s ridiculous really. Where the hell has the summer been? It’s the last week of August and - like an idiot - I packed T-shirts and little else. Not monsoon gear, wind breakers nor down jackets.

Thank goodness I’m made of sturdier stuff and can accommodate a slight chill with some light jogging with a toddler on my shoulders.

But I do mean light. My formerly-wisdom-toothed gum still gives me a surprising amount of “you’re about to do something” every time I bend over to tie some shoe laces.

And if a slight pressure change from orientation is flaring the thing up, then I’m very hesitant to do any hardcore aerobic exercise.

But looking at the bright side, being unable to open my jaw very wide and then having it feel quickly exhausted is doing wonders for the weight lose journey.

Older post

2023-08-23

Newer post

2023-08-27

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.