Why Infrastructure

Why I Write About Infrastructure

I grew up on a remote rural farm in Western Australia.

It might not seem directly connected to artificial intelligence, fibre networks, or electricity systems, but it shaped how I think about infrastructure more than anything else.

Farming teaches you very quickly that everything is a system.

Crop rotation, soil health, water management, stock movement, seasonal planning, each decision affects the next. One crop can strip nutrients from the soil, another can restore it. Livestock can either degrade or improve land depending on how they’re managed. Every action has a consequence, and every season builds on the last.

Planning is not optional.

You are constantly balancing short term needs with long term sustainability, while dealing with variables you cannot control; weather, pests, market conditions, and natural disasters. A strong year can quickly turn into a poor one without warning.

That environment develops a practical mindset:

Understand the system.
Plan ahead.
Maintain what matters.
Expect disruption.

Those principles have stayed with me throughout my career.

Learning Systems Through Work

Before telecommunications, I worked across a range of environments that all reinforced similar lessons.

In construction labouring and landscaping, I learned that good planning on paper does not always translate cleanly into execution. Landscaping in particular had a unique challenge, often you complete the final stage of work and its looking like a show peace. Only then to have utilities installed afterwards, requiring rework. It reinforced the importance of sequencing, coordination, and understanding how different systems interact.

Having worked as a subcontractor in construction and landscaping, I gained direct experience of how infrastructure projects are delivered at ground level, including the impacts of sequencing decisions, late stage changes, and the commercial pressures faced by contractors.

This perspective has shaped how I approach large scale infrastructure programs, particularly in understanding where plans meet reality.

In hospitality and promotions, I spent years working directly with people; managing operations, running events, and handling both customers and teams in fast paced environments. That experience built an understanding of how systems behave under pressure, and how important communication and coordination are when things don’t go to plan.

Across other roles, from warehouse work to banking and sales, I gained exposure to different operational environments, each with their own constraints, processes, and dependencies.

Looking back, the common thread was clear:

I’ve always worked in systems that must operate reliably under pressure.

Telecommunications and Infrastructure

My career in telecommunications brought all of those lessons together.

Starting in network drafting and moving into design and delivery across multiple network types,  including access networks, inter-exchange systems, transmission infrastructure, and IP networks, I worked across environments where reliability, scale, and coordination are critical.

Telecommunications infrastructure is fundamentally about connecting systems:

Having worked across multiple generations of telecommunications technology, from early circuit based transmission systems through to modern IP and packet-based networks. I have seen first hand how networks have evolved from rigid, voice centric infrastructure into flexible, high capacity systems capable of supporting today’s data driven economy.

This evolution reflects a broader shift in infrastructure: from fixed and hardware defined systems to scalable, software driven platforms designed to handle exponential growth in data movement.

A network evolution that started decades ago

Over time, I became involved in increasingly large and complex infrastructure programs, working across design, operations, and delivery environments.

What stood out consistently was this:

Infrastructure is never just one thing.

It is a collection of interconnected systems, each dependent on the others, each with its own constraints, and each requiring long-term planning to function effectively.

How That Connects to AI

Today, much of the conversation around artificial intelligence focuses on software, models, and computing capability.

But from an infrastructure perspective, AI is something else entirely.

It is a system.

It depends on:

Each of these layers must scale together.

If one fails or lags behind, the system is constrained.

This is not a new pattern, it is the same principle seen in farming, construction, and telecommunications.

The difference is scale.

A Practical Perspective

My perspective on AI infrastructure is shaped by working in environments where:

It is not just about what is technically possible.

It is about what can actually be built, maintained, and operated over time.

Why I Write

The current discussion around AI often overlooks the physical systems that enable it.

Electricity.
Fibre networks.
Datacentres.
Infrastructure.

These are not secondary considerations.

They are foundational.

This is why I write about the infrastructure behind the AI economy.

 Footnote

This article is part of a series exploring the physical infrastructure behind the AI economy.

Disclaimer

The views expressed in this article are my own and are intended for general information and discussion purposes only. They do not represent the views of any employer, organisation, or client.

© 2026 Rodney Terry – Digital Backbone. All rights reserved