Day 5 of Israel

If you’ll allow me the luxury of another cathartic rambling, I’ve been surprised today by the response of so many of you getting in touch by one means or another.

I think it has helped that last night gave a solid 11 hours of sleep that probably helped immeasurably. As this morning upon actually awakening I didn’t stare at the ceiling and wonder to myself as to why the hell I was here. Maybe that’s just a latter stage of grief, acceptance.

Maybe it was the thought of the baguette shaped and sized cinnamon danish pastry I knew I’d saved for this moment. I even splashed out and had bought the most expensive (instant) coffee in the shop to try out. Today was going to be a good morning. Made better when turning on the TV, it awoke displaying the Hobbit about 20 minutes in. Hopes were quickly dashed when I saw the state of the kettle. C’est la vie. Still with expert use of microwave I had both warm pastry and coffee.

The power cut as the Hobbit was getting good was most unappreciated. I took that as a sign to get off my keister and actually do some thesis corrections, even if that meant it had to be done on the laptop and required a walk to work for use of electricity. But then, as I picked up my keys to leave the AC decided to have the acoustic equivalent of an epileptic fit signifying the return of civilization. So obviously, I watched the end of the Hobbit before going to procrastinate with facebook and emails.

I was genuinely surprised by the number of people that had got in touch. I don’t know if that is significant to just how unproductive the whole world was feeling on Friday morning. But I had several lovely messages, from lovely people. And in my battered emotional state, most had me choking up. I suppose we always sort of know at the back of our mind’s that people are there for us, after all we surround ourselves with people. I also know that, I perhaps know more than most and that I try desperately hard to keep as many as close as is possible. Perhaps that’s one of my reasons for so frankly speaking here, though I’m always shocked when someone acknowledges that my humble ramblings are worth their time to read.

A man, wiser than myself, a man I respect with my whole being sent me a message, proposing an alternative way of thinking. One in which where despite everything in our lives we ultimately concentrate on three things; relationships, friendships and work. Within this “holy trinity”, your typical person and deal with an upheaval in one of these three things and typically by throwing ourselves at the remaining two. How often have we all seen after a disastrous end to a relationship someone throw themselves at friends (typically with immediate alcohol) and throw themselves at work for the remaining time? Two of the trinity starts to strain things. Whilst what I’ve in the last month is disturb all three. No wonder then, times are tough when the normal coping mechanisms are diminished.

This then has been a day of throwing myself at work. Whilst the hours are long, the work is tough, and the motivation is low. There are diamonds shining in the rough. Every hour spent on these corrections is an hour closer to me officially holding me PhD certificate. That and even in this dive of an apartment with the windows wide open, glorious sunshine, 30 degrees with a gentle sea breeze makes me think that this is exactly what British autumns are missing. All that is missing is an easy chair out on a veranda, a bottle of red with some quality company.

This post was written to The Parlor Mob, give ‘em a listen…

Older post

Day 4 of Israel

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.