Writing

Writing

Notes on building enterprise software.

Essays and recorded commentary on why enterprise software succeeds or fails, and what that means for the products I build. Published on LinkedIn and YouTube.

YouTube — Recorded Commentary

Selected videos exploring technology, data, governance, and enterprise systems through real-world observations and practical analogies.

Channel on YouTube

Video

King's Cross, Storytelling, and the Art of Knowing When to Stop

Using the history and transformation of London's King's Cross Station as a starting point, this video explores how narratives evolve over time and why timing, structure, and decision-making matter. The discussion connects storytelling principles with data analysis, demonstrating how effective analytical work depends not only on collecting and processing information, but also on recognising when sufficient insight has been reached and how results should be communicated.

Video

Technology Adoption, Innovation Cycles, and Lessons from London's Infrastructure

Through the evolution of gas lighting, electricity, and urban infrastructure in London, this video examines how technologies emerge, scale, mature, and eventually become obsolete or evolve into new forms. The discussion draws parallels with database technologies and SQL Server architecture, highlighting broader lessons about innovation, performance, scalability, and long-term technology strategy.

Video

Governance by Design: What London's Skyline Teaches About Data Architecture

This video explores how London's urban planning framework protects strategic views and historical assets through carefully designed constraints and governance rules. The same principles are then connected to SQL Server concepts such as constraints, triggers, and controlled data structures, illustrating how effective governance enables both flexibility and long-term integrity within complex systems.

Professional Insights

Three things I keep coming back to. Most problems in enterprise software are decisions that were never made, not missing technology. The part that many organisations share should be built once and configured, not rewritten for each customer. And a model is only useful if it fits the data and the person who has to act on it. These ideas shape how I build Procura and HOP and the research I will start at the University of East London.