The 90s were a chaotic, brilliant, unrepeatable moment in technology. No instructions, no YouTube, no Stack Overflow. Just hardware, curiosity, and time. Here is what that era gave me that nothing since has replicated.
If you grew up in the 90s around technology, you already know what I am talking about. There was something about that era that has not been replicated since, and I do not think it can be.
The internet existed but was not domesticated. Software worked inconsistently and you had to figure out why. Hardware was hands-on in a way it simply is not today — you could open a case, see the components, understand roughly what each piece did and how it connected to the others. There was no single place to look up answers. You worked things out.
That era produced a generation of people who think about technology differently from the generations on either side of it. And I think about my own career — everything I have built and continue to build — as a direct product of what the 90s taught me.
The Technology That Was Just Arriving
When I was growing up, technology was not ambient. It was arriving. It was new and it was exciting in a way that is genuinely difficult to communicate to someone who grew up with a smartphone in their hand from age seven.
The internet came to Australian households as something strange and a little miraculous. You connected via a modem that made a sound like two fax machines having an argument, and then — if you were lucky and the phone line was clear and your ISP was not overloaded — you were online. On the actual internet. The one the whole world shared.
Pages loaded slowly. Images loaded line by line. Downloading a song took the better part of an hour on a good connection. It did not matter. It was extraordinary that it was happening at all.
The software landscape was different too. Programs came on CDs, or floppies if you were buying something older. They installed — or they did not, and you had to work out why. Driver conflicts, IRQ settings, memory allocation errors. Troubleshooting a Windows 95 installation was a proper exercise in patience and systematic thinking.
There were no tutorials for most of this. The documentation was dense and assumed technical knowledge. You either developed that knowledge or you stayed stuck.
Most people stayed stuck. Some people — the ones who are now running IT businesses, or working as engineers, or building software — got very interested in the problem of becoming unstuck.
What the Hardware Taught Me
The physical relationship with 90s technology was formative in ways I only fully appreciated later.
When my dad upgraded computers, the old machine came to me. And the old machine became a project. I had a screwdriver and curiosity and no particular concern about breaking something that was already considered obsolete.
I learned what RAM was by physically handling it — the way it seated into the slot, the click when it was fully pressed home, the way a machine would fail to POST when it was not quite right. I learned what a power supply did by watching what happened when one failed. I learned cable management by dealing with the consequences of not doing it — a loose IDE cable was a machine that would not boot, and finding the problem required methodical elimination of possibilities.
This kind of tactile, physical engagement with technology built an intuition that I cannot adequately describe but rely on constantly. When I am diagnosing a complex system failure today, I am drawing on a mental model of how systems interconnect that was built by pulling apart machines in a bedroom in the late 90s.
You cannot get that from documentation. You cannot get it from a course. You get it from handling real systems, watching them fail, and working out why.
Dial-Up Internet and the Frontier Feeling
The early internet had a quality that I have heard described in different ways by people of my generation — a sense of being on the edge of something, of participating in something that was being built in real time.
Every website was made by someone. The barrier to creating was low and the standards were nonexistent, which meant the web was wildly uneven — brilliant things next to terrible things, amateur enthusiasm next to early professional work, everything in the same undifferentiated space.
I was part of that. Building simple things, exploring strange corners, participating in early online communities that operated on trust and curiosity. The culture of the early internet rewarded people who shared knowledge freely and engaged with genuine interest. The idea that information should be accessible, that problems should be worked through together, that someone who figured something out should post about it so others could benefit — that culture shaped how I think about knowledge.
It is also, in a direct line, why I write about IT the way I do now. The impulse to explain what I understand, to share what I have learned, to write clearly about things that are often communicated badly — that comes from a web culture that valued it long before “content marketing” was a phrase anyone used.
The Things 90s Tech Didn’t Have
What the 90s did not have is as instructive as what it did.
There was no instant answer. If something did not work, you could not type the error message into a search engine and get a forum post with the solution. You had to diagnose it yourself. You developed a process — eliminate variables, isolate the failure, test the hypothesis, try again. That process is still the core of good IT troubleshooting.
There was no always-on connectivity. Computing was an activity you did deliberately, not a constant ambient state. You sat down at a machine, did a thing, and then moved away from it. That relationship with technology — engaged and purposeful rather than constant and passive — feels healthier to me than what came after, even if I am not immune to the pull of always-on connectivity myself.
There was no authority. The internet was not curated or officially explained. You found things, evaluated them, decided whether they were credible, and formed your own view. That habit of evaluating sources critically rather than accepting whatever arrived first is something I still apply — to technology claims, to vendor pitches, to every piece of security advice that tells businesses what they must do without explaining why.
Why It Still Matters
I am a technology professional in 2026, and the technology I work with every day would be unrecognisable to my 1990s self. Cloud infrastructure, AI tooling, enterprise security platforms, software-defined networking — none of this existed in any recognisable form when I was learning to pull apart computers.
But the thinking that the 90s built — systematic, curious, hands-on, comfortable with ambiguity, oriented toward understanding rather than just operating — applies to all of it. The technology changes constantly. The thinking is the constant.
The best engineers I have worked with, of any generation, share this quality: they are genuinely interested in how things work at a level below the surface. They are not just users of tools — they are students of systems. When something fails, they want to understand the mechanism of the failure, not just apply the fix.
That orientation, in my experience, is usually built early. For my generation, it was built in the 90s, in the gap between what the technology did and what we wanted it to do, in the space where curiosity had to substitute for instruction.
I am glad I grew up when I did. The technology was worse. The learning was better.
The Thread That Runs Through Everything
When I think about why I started CX IT Services, why I built CX365, why I invest in continuous learning and push my team to do the same — it all traces back to that kid with a screwdriver and an obsolete Pentium III.
The passion was not manufactured. It was not a career strategy. It was genuine, deep interest in technology as a thing to be understood and worked with, not just consumed. That interest has not diminished in thirty years. If anything, the pace of technological change has kept it alive in a way that a more static field never could.
The 90s gave me the foundation. Everything since has been building on it.
