Where have all the flowers gone?

As another week begins it seems appropriate to reflect back at the week gone by, and what a week it has been. It has both simultaneously been busy yet quite, crazy yet peaceful.

It has been in this week that for the first time in Israel I have eaten lunch alone.

For this week, it has been very quiet. The lose of my brother-in-arms still weighs heavy upon the office – with it still not being the same. Of my two remaining comrades, one was in Finland with his (what I’m sure will be) soon-to-be wife which he never should have left. The other, it was his first week in his new position without the security of being under the wing of his 40-year-experience predecessor and thus off his feet.

My last bastion of sanity, in this otherwise autism showcase then flew away for a long weekend in Cyprus to get married – because oh yes, unless you are both provably Jewish back to the grandparents then you arent Jewish enough to marry in the Jewish state.

And all of this in the same week that I said goodbye to my personal tour-guide of Israel, the person who showed me the bright lights of Tel Aviv and so many places. And now she’s living her life 10 time zones away on the other side of Canada.

This left me with a curious case of having absolutely nothing to do of interest upon the weekend.

So what does any work obsessed, career driven – yet career confused, person with nothing to do and no responsibility do. Well the obvious answer is make use of the copious free equipment at work and do back to back 12 hour days whilst simultaneously catching up on a load of paper work that should have been done months ago.

It seems a weird alignment in the planets that I find myself with nothing to do. But at the same time having time to catch up on all things work, to spend time alone, music blaring and just crack on and cross a few stubborn things off the list was very therapeutic.

Of course, there needs to be a work / life balance and I can hardly say that I’ve been unproductive on the work front. But for a little while there has been a nagging at the back of my mind that says that I’m here for work first and an amazing time second. I know that I’m only going to be here a short time and when I think that already 4 months has gone by without me even realising it’s terrifying how quickly time has moved. Whilst at the same time, some days seem to drag and drag.

I know that if I want to stay in this life, this academic life, then I need to get results from this place. This needs to be a positive mark on the CV with glowing recommendations and reports. Maybe that’s all just a moot point. But what I need most is to keep my options open at this point. Just like this time last year I had no idea where I would be in a years time, this year, like last, I’ve got no idea what I’ll be doing in another 12 months.

It’s a very strange feeling. I’ve avoided being alone for so long, I’ve kind of forgotten what it feels like. But it seems no matter where I go, I surround myself with people. Good people. Some amazing people. And I try to keep as many of these amazing people in my life as possible. I guess, ultimately, this is why I write here in such a public fashion. I often delude myself that I write for me, only me, and the fact that people read it is a happy coincidence. But now I think it isn’t that. I think this is my way of keeping as many of those people that I care about in my life as possible.

This weekend when I had no intention of seeing anyone. I didn’t feel alone. I didn’t feel lonely. I was comfortable in knowing that there’s people out there that care regardless. And whilst they weren’t physically there it didn’t matter.

Sometimes, it is good to step back and just…enjoy the silence.

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.