A Space for Systems That Have to Hold

Why this site exists, what it is about, and who it is written for.

By Bhavin Gandecha

Modern life sits on top of a small number of systems that almost nobody thinks about until they stop working. Phone calls travel through cables and switches that were planned years before anyone made the call. Hospitals run on networks that quietly carry test results from one floor to another. Banks settle payments through systems that have been running, sometimes with very little change, for decades. Power, water, transport, healthcare, schools, government services, all of these rely on layers of equipment, software, contracts, and people whose work is mostly invisible to the public. When the layers hold, life goes on as usual. When they slip, the whole picture shifts very quickly.

This site is a place to think about those systems with care. It is not a place for general comment on whatever happened in the technology world this week. It is a place to look at the parts of the picture that decide whether things stay standing, and to write about them in a way that respects the seriousness of the work.

What This Space Is For

My focus is on a specific set of areas. The first is broadband and the wider networks that carry our data from one place to another. These networks are being rebuilt right now, with new money, new policy, and new technical choices being made on a scale not seen for many years. The decisions being taken in this period will shape what is possible for the next decade, and a lot of those decisions deserve closer attention than they are getting.

The second area is the next stage of wireless connectivity, which includes the work being done now on WiFi and the early shape of what is being called 6G. These are not far away problems. The standards bodies, the equipment makers, and the operators are already setting the direction. The honest question is whether what they design will actually meet the needs of the places and services that will rely on it.

The third area is cyber physical systems. This is the long name for everything that lives at the join between computing and the real world. Smart roads, connected hospitals, automated factories, the controls that keep power and water moving. These systems behave differently from pure software because a mistake does not stay on a screen. It moves into traffic, into machines, into the buildings where people live and work.

The fourth area is artificial intelligence in places where it has to be trusted. I am less interested in what AI can do in a demo than in what it does in an operations room at three in the morning, when the people in the room are tired, the data is patchy, and the cost of being wrong is real. That is where the value of any tool gets tested, and that is where the writing on this site spends most of its time.

How I Approach the Work

Three ideas run through almost everything I write. The first is design. Before forming a view on any system, I try to picture its shape. Where does the load actually fall. What carries what. Where do the pieces join. Where do the joins go wrong. Without that picture, an opinion is just noise dressed up in technical words.

The second is the ability to keep working when things break. A system that only runs in perfect weather is not really a system. What matters is what happens at the edges, when load spikes, when a cable is cut, when a supplier misses a deadline, when a piece of software encounters a situation nobody planned for. The ability to keep going in a reduced state, and to come back fully later, is not magic. It is the result of patient choices made before the trouble started, often by people whose names are not on the building.

The third is the long gap between plans on paper and things in the ground. Plans are easy. Delivery is hard. The space between what was promised in a meeting and what actually got built on time is where most of the interesting work in this field lives. A lot of my writing comes back to that gap, because closing it is the part most public conversations skip.

Who I Hope Will Read This

If you work inside one of these systems already, I hope the pieces here are useful to your day to day work and now and then offer a fresh angle on something familiar. Engineers, operators, programme managers, and the people who quietly hold the line at three in the morning are very much who I have in mind when I write.

If you study these systems from a research or academic point of view, I hope the writing here helps connect your ideas to what is actually happening on the ground. The distance between a strong paper and a working deployment is often a lot wider than either side wants to admit, and there is value in shrinking it.

If you work in policy, or you advise people who do, I hope you find a voice that takes delivery seriously. Good policy that ignores how it will be carried out tends to fail in slow motion. The most useful policy commentary I have read over the years was written by people who had been close enough to the work to know what would survive contact with reality.

If you are a journalist working on a story that touches infrastructure, network design, the ability of systems to bounce back, or the operational side of AI, I welcome the conversation. The articles here are not press releases. They are working notes and considered arguments, and they are written so that they can stand up to questioning.

And if you have arrived here simply because you are curious, that is reason enough. The systems that quietly run modern life are too important to be left only to the people who build them. A small amount of public understanding goes a surprisingly long way.

What You Will Not Find Here

Being clear about what a site is for also means being clear about what it is not. This is not a feed of daily technology news. It is not a place for quick reactions to whichever big company released a new product this morning. It is not a marketing channel, and it is not a productivity blog. There is nothing wrong with any of those things, but they are not what I do here.

What you will find instead is a slower set of pieces. Articles that take a position and explain it carefully. Responses to research papers and policy documents, often focused on the gap between what they propose and what would actually need to happen to make the proposal real. Original pieces working through ideas that have been sitting with me for a while. Now and then, a set of slides or a diagram, because some arguments are easier to see than to read.

On Tone

I try to write the way I would talk to a respected colleague over coffee. Plain, but not blunt. Considered, but not dense. Confident where I have a reason to be, and open about the places where I do not yet have a clear answer. If a piece ever starts to feel like it is showing off, I have lost my way. If it feels like a useful conversation, then it is doing its job.

Pushback is welcome. The readers I learn most from are the ones who disagree carefully and tell me where my thinking is thin. I would rather be corrected than carry on being wrong. If a piece changes how you see a problem, or if it falls short for you, either way I would like to hear it.

Why Now

We are living through a period when many of the systems around us are being rebuilt in public view. New networks. New platforms. New layers of automation. Public spending on infrastructure on a scale that has not been seen in a long time. Some of this work will hold up. Some of it will not. The difference, in most cases, will come down to whether the people involved were thinking clearly and whether the assumptions they made survived first contact with the real world.

No single voice can fix that. What I can do is contribute the way I know how. By writing carefully, by sharing what I have learned, and by trying to raise the level of conversation by a small amount in a small corner. That is the purpose of this space, and that is what I plan to keep doing here for as long as it is useful to someone.

Thank you for reading. I hope you stay a while, and I hope what you find here is worth the time you give to it.