Destruction

Dear Diary,

Today has thus far been one of those days where it was difficult to get out of bed and promptly wished I never had bothered really. Today after a very slow start, after a very long night where my sleep was interrupted many times by numerous twats coming in and out of the house, I attempted some work.

Very shortly afterwards the girlfriend came online. What with my status being online rather than my usual appear offline I thought that I had better make and effort to talk to her, rather than my usual tactic of just pretending like I’m not there. Truth is I hate talking to her online these days. Usually because I feel so crap after a conversation online with her. Many reasons for this really. Partly because it now takes her over 2 minutes to give one word responses, regardless of the question. Even if I know she is doing nothing else at the time than talking to me. Partly because I feel about as appreciated talking to her online as something she might tread in. Having said that, now that she works at the stable she probably thinks more of sh!t than me, at least that pile of sh!t is treated to some one on one time everyday without interruption.

Well today she had to leave me to in fact go move some horse sh*t about, how terribly appropriate really. And she didn’t even say goodbye.

But the thing about the conversation as of late that annoys me most of all. She’s been planning a trip to Nottingham, and yet I seem to be the last one to find out. I seem to only find things out via through select friends here in Nottingham. Work of course takes presidency over me, she could never come up on a weekend to see me, and I cant go down to see her because of work.

Older post

Life currently

Newer post

Over, now it is

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.