2023-11-20

Midweek journaling! Look at this! Truthfully, between meetings over the last day or two I’ve taken the time to investigate a new framework for my website. None of the bells and whistles. Just a minimal barrier between writing and getting something posted.

I think historically this has been my barrier. When my grandmother was still alive I made a conscious effort to use my correspondence with her as a way of keeping an account on my life. However, it always created a feeling of it being an event. If I’m going to go to the hassle of committing to words on paper, envelopes, international stamps and mailboxes then I’m not going to do it for anything less than something substantive.

I targeted a monthly frequency, but if I’m honest with myself finding a few spare hours to write and edit a few pages became something that I’d only commit to once the guilt had mounted to spill over levels. Surmounting the apathy of sitting on the couch and doing nothing. All told, I suspect the frequency was akin to quarterly than the monthly i desired.

Even then, the barrier to activation was too high. Committing to a few hours on a laptop, ideally without interruption versus a mere 10 minutes that I can type out on my phone really does reduce the hard work.

I think too the commitment to not really proof or edit any of these things. Just to use them as a stream of consciousness is useful to me. Both to reduce the overhead but as an unfiltered way to work through what’s going on in that head of mine.

As the quote goes “I apologize for the length, I would have written less if I had more time”. Editing is an important skill and it forces one to clarify their thinking, but it takes time and I’m not searching for refinement in this process.

Having worked a little on the website and optimized my workflow there was a moment today where I saw fifty posts from the last few months just listed out before me. And it was quite a thing to behold. A body of work. A record, that I, did something. No matter how small. I did something. And from humble beginnings sprouts the motivation to do more.

Older post

2023-11-19

Newer post

2023-11-26

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.