Post results

So, after the weekend in Manchester and having watched lady E run the race for life we have returned to Nottingham. So we only have a day or two now until I go off on Doug’s stag weekend and after that its a week in Sherringham on the Norfolk coast with JC and company. Which should be a nice relaxing break from the running around that has been accustomed in previous months. As soon as we get back from that lady E has some work experience to see if she wants to teach and then its practically graduation, which means leaving Nottingham.

Something that I hadn’t really thought about much that. I mean, I’d always kinda been looking forward to it because I couldn’t wait to get away from this place and the bureaucracy and other crap that has come with this place over the years. But now it’s becoming a little more real I guess. That and I think lady E is getting more upset by the day about the thought of me buggering off, her perhaps moving back with the parentals. And I guess that hasn’t bothered me until recently because I haven’t been thinking about it, and possibly because I think I’m starting to realise that I might actually miss her. Shock horror, I know, me, showing some emotion. Tough I know.

But, in other, slightly more positive news. I’ve had some good news come through, the news boss to be has contacted me saying that he has found some funds that will allow me to start work 6 weeks early. Meaning that I can be paid for the summer and I’ll have something to do through late August and September. Which is great cos it means that I’ll have some money coming in and I wont have to trawl the streets looking for a summer job. Granted that will perhaps mean that my summer plans will be a bit more restricted but it also means that I wont be going out of my mind with boredom.

And then that leaves us with the one last bit of news, aside from my gran sending me £50 for passing university (which she really shouldn’t all things considered). My exam transcripts and thus mark breakdown for all my modules were released yesterday. My research project was a very strong 2:1, but upsettingly my two cancer modules scraped past with only just 50% each which considering the time I spent revising, the days in the library, the purchasing of 2 specialist textbooks (at £60 a pop) doesn’t quite seem worth it. Which means that overall my average for the year was 60.1%, taking my complete degree average to 60.5%. Which I’ve gotta say is less than I hoped for but at the end of the day, I was not borderline, and the history books will only show me getting a 2:1, even if it was only by half a percent. And let’s face it I worked pretty damn hard for it. So all at once, I’m greatly relieved and disappointed at the same time. Relieved for the 2:1 and no viva, but disappointed that that 60.5 wasn’t a 65. But ca la vie. It’s all I needed and it’s all I need to carry on.

Older post

Nearly there

Newer post

Alton Towers

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.