The human operating system: Forty years of “microcomputers,” missed connections, and the psychology of security
An in-depth conversation with David Chapman of BN-IS
This interview was conducted shortly before David’s planned retirement from BN-IS, concluding a remarkable 41-year career in the technology sector. We are immensely grateful for the opportunity to capture his unique perspective before he departs, and we wanted to share this conversation as a token of our sincere thanks and appreciation for his profound contributions to BN-IS and the wider industry.
It is a rare thing in our industry to find someone who remembers the silence before the noise. Today, we live in a deafening roar of notifications, AI-generated content, and instantaneous global connectivity. We panic if a page takes three seconds to load. We speak of “the cloud” as if it were a weather system we have always lived under.
But David Chapman remembers when the clouds were just rain, and “windows” were just glazing.
David is something of a legend within BN-IS. Not just because he holds the badge of being one of the first twenty Microsoft Certified Systems Engineers outside of the United States, but because he possesses a perspective that is becoming dangerously scarce. He has seen the wheel invented, reinvented, digitised, and put on a subscription model.
I sat down with David recently to trace the arc of a 41-year career that spans from the birth of the IBM PC to the dawn of Generative AI. We talked about technology, of course. But as we drifted from the rainy roundabouts of 1990s London to the server rooms of modern data centres, a different theme emerged. We weren’t really talking about computers. We were talking about people.
The “Frame” that we use at BN-IS – our methodology for aligning technology with business goals – is often seen as a structural tool. But in talking to David, you realise that the structure is useless without understanding the chaotic, emotional, brilliant, and sometimes terrified humans operating within it.
Here is David Chapman on the history of the future.
Ben Nichols: David, whenever we talk about the “old days,” I think there’s a temptation to view it through rose-tinted glasses – to see it as a simpler time. But looking at your notes, it sounds like it was less “simple” and more “Wild West.” Where does the story actually start for you? Was it a conscious decision to get into tech, or a happy accident?
David Chapman: It was entirely accidental, Ben. In fact, it started with a broken exhaust pipe.
Ben Nichols: A broken exhaust?
David Chapman: Yes. This would be around 1983. I was a bit of a car nut – still am – and I had this old Alfa Romeo Bertone GTV. Beautiful car, but a nightmare to keep running. I needed parts for it, and back then you didn’t jump on eBay. You scoured the classifieds in the local paper. I found a guy in Oxford who was selling spares, so I drove down to his house.
We did the deal for the exhaust, and he invited me inside. And there, in the corner of his house, was this stack of beige boxes humming away. I asked him what they were. He looked me dead in the eye and said, “These are microcomputers. Forget electronics, forget everything else. These are the future. They’re going to change the world.”
He told me I should get into it. I was 17. I didn’t even know what a “microcomputer” was. But the way he said it… it stuck. A few months later, I saw a tiny, cryptic advert in the paper for a “microcomputer startup” in Birmingham. I remembered the guy with the Alfa Romeo, and I applied. I was employee number five. That startup grew into the largest IBM dealer in Europe.
Ben Nichols: It’s incredible to think how pivotal those small moments are. We talk a lot about strategy at BN-IS, about planning the trajectory of a business. But so much of life – and certainly the history of this industry – seems to hang on serendipity.
David Chapman: Oh, completely. It’s what I call the “Sliding Doors” of IT. The industry is built on accidents. If I hadn’t needed that car part, I might still be fixing circuit boards for door entry systems.
Ben Nichols: Speaking of sliding doors, you have a rather terrifying story about Bill Gates that I think qualifies as the ultimate “what if.”
David Chapman: The Westway incident. Yes.
Ben Nichols: Set the scene for me.
David Chapman: It was November 1992. At the time, I was working for Apricot Computers. We were a big deal in the UK hardware market, and Microsoft was… well, they were Microsoft, but they weren’t the global superpower they are today. Windows 3.1 was out, but the world hadn’t quite tipped over yet.
Bill Gates was in London for a keynote speech at the Wembley Conference Centre. My Technical Director, Peter, saw an opportunity. He wanted to bend Bill’s ear about some licensing deals. So, we offered to drive him to the event.
Now, the car we had was a Vauxhall Carlton 3.0 GSI. Big engine, rear-wheel drive, and – crucially – absolutely no ABS or traction control. It was a beast of a car. It was a miserable, rainy November morning. I was driving, Peter was in the passenger seat, and Bill Gates was sitting directly behind me in the back.
We were cruising along the A40 Westway. As we approached a roundabout, I hit the brakes. Nothing happened.
Ben Nichols: Nothing?
David Chapman: It turned out a bus or a lorry had spilled diesel all over the road surface. It was like ice. I pressed the pedal, and the car just locked up. We were essentially a 3-litre sled sliding helplessly towards a busy junction.
We sailed straight across the roundabout. I remember seeing the grille of a skip lorry coming from the left and a bus coming from the right. It was pure physics and dumb luck. We threaded the needle between them, missed the traffic by inches, and came to a stop on the other side.
The car was silent. We eventually got going again and got Bill to the conference on time. But I remember lying in bed that night thinking: If that skip lorry had been two seconds faster, the man sitting behind me would be dead.
Ben Nichols: And the history of computing changes instantly.
David Chapman: It stops dead. Microsoft was Bill Gates. There was no redundancy plan for him. If that accident happens, maybe OS/2 becomes the standard. Maybe Apple wins the desktop war twenty years early. The entire landscape of the last three decades hung on the friction coefficient of a wet road in London.
Ben Nichols: It’s terrifying. But it also highlights something we often discuss with clients regarding their own resilience – single points of failure. In this case, the single point of failure was sitting in the back of a Vauxhall Carlton.
David Chapman: Exactly. And that fragility is something people forget. We assume the tech giants were inevitable. They weren’t.
There’s another story I tell – the story of Gary Kildall. He’s the man who should have been Bill Gates. In 1980, IBM needed an operating system for their new PC. Their first choice wasn’t Microsoft. It was Gary Kildall’s company, Digital Research. IBM executives flew to California to meet him.
But Gary was a brilliant technical mind, perhaps a bit eccentric. The story goes he’d had an argument with his wife that morning and decided to go flying in his private plane instead of waiting for IBM. When the IBM suits – blue suits, white shirts – turned up at his house, Gary wasn’t there. His wife, who was still angry with him, essentially told IBM to go away.
IBM didn’t like being told to go away. So they got back on the plane, flew to Seattle, and met their second choice: a 24-year-old kid named Bill Gates. Bill didn’t even have an operating system at the time! He bought one called QDOS – “Quick and Dirty Operating System” – rebranded it, and licensed it to IBM.
Gary Kildall died in a bar fight ten years later, a broken man. He watched someone else become the richest man in the world using an opportunity he missed because he went for a plane ride.
Ben Nichols: It’s tragic. But it emphasises that technology isn’t just about the code. It’s about the human interactions around it. The deals, the arguments, the relationships.
David Chapman: That is the single biggest lesson of my 41 years. The technology changes every minute. The people don’t change at all.
Ben Nichols: Let’s dig into that. You’ve seen the transition from command-line interfaces to the metaverse. You’ve seen processor speeds increase by factors of millions. Yet you argue that the job hasn’t changed?
David Chapman: The tools have changed. The fundamental human desire hasn’t.
In the mid-80s, I remember visiting an accountant to demonstrate a piece of software called Lotus 123. This was pre-Excel. Before this, “spreadsheets” were literal sheets of paper. You had a ledger, a pencil, and a calculator. If you changed one number in a column of fifty, you had to erase everything, recalculate the total, and rewrite it. It was hours of drudgery.
I set up the PC, typed in his numbers, and showed him how, if I changed cell A1, the total at the bottom updated instantly.
Ben Nichols: What was his reaction?
David Chapman: He started crying. I’m not exaggerating. Tears in his eyes. He realised that the weekends he spent with a calculator, missing time with his family, were over. Then I hit a button and turned the data into a graph. He actually sobbed.
I met him twenty years later, and he still remembered that day. He called it “the day my life changed for the better.”
Ben Nichols: That’s a powerful image. We often talk about “efficiency” and “productivity” in these sterile, business-school terms. But for that guy, efficiency meant getting his life back. It was emotional.
David Chapman: Precisely. And that emotion is still what drives us. Why do people want AI now? Why do they want Copilot? It’s the same desire: Take away the drudgery. Give me the answer. Let me go home.
The difference today is the “wow” factor is diminishing. When you’ve never seen a laser printer, the first time a piece of paper slides out with perfect text, it’s magic. Now, the incremental gains are harder to feel. We get a new iPhone, and it’s 10% faster. Nobody cries over that.
Ben Nichols: We’ve become desensitised to the miracle.
David Chapman: We have. But the risks have gone the other way.
Ben Nichols: This brings us to security. You mentioned that in the early days, you were fixing door access systems. Security was physical. A card, a door, a lock. How has the psychology of security shifted now that the door is digital?
David Chapman: In the beginning, there was no security. It sounds mad now, but on those early networks, we didn’t have passwords. Why would you? Who would want to read your email? We were “Islands of Information.” If you wanted to steal data, you had to physically break into the building and steal the floppy disks.
Once we connected those islands – first with dial-up, then the web – the threat landscape exploded. But the psychology didn’t keep up.
I look at the recent hacks – Jaguar Land Rover, huge supply chain breaches. Often, these aren’t happening because the hackers cracked a 4096-bit encryption key using a supercomputer. They happen because someone, somewhere, had the password “Password123.” Or because a supplier was given admin rights they didn’t need.
Ben Nichols: It’s the “human firewall” failing.
David Chapman: It is. And this is where I think the industry is getting it wrong. We keep throwing more technology at the problem. We buy more expensive firewalls, more complex detection systems. But the attackers are targeting the people.
I’m working a lot now on what we call the “Psychology of the User.” Why do people click the link? Why do they bypass the secure VPN to use ChatGPT on their phone? Usually, it’s not malice. It’s friction. If security is too hard, people will find a way around it because they just want to do their job.
Ben Nichols: It reminds me of the conversations we’re having now about AI. We see staff “shadow IT” – copy-pasting sensitive company data into public AI tools because the internal tools are too clunky or non-existent. They aren’t trying to leak data; they’re trying to write a report faster so they can finish their work.
David Chapman: Exactly. It’s the path of least resistance. You can’t fight human nature with a firewall. You have to design the system around human nature.
That’s why I tell young people entering the industry today: Don’t just study computer science, study psychology. The code is predictable. The user is not. If you can understand why a person behaves the way they do, you can secure them. If you just treat them as a node on the network, you’ll fail.
Ben Nichols: You touched on something interesting about “Two is one, and one is none” – the dual datacentre concept you helped pioneer. That feels very relevant to the BN-IS “Frame.” We talk about resilience not as a box-ticking exercise, but as a survival strategy.
David Chapman: I picked that phrase up from the military, but it applies perfectly to IT. I remember working on a project for the UK Army in Germany. The idea was simple: redundancy.
By 2003, businesses were totally dependent on IT. If the server broke, the business stopped. I pushed the idea of splitting servers across two geographically separate locations. Real-time replication. If one building burns down, the other takes over instantly.
We have a customer at BN-IS today who still runs on that architecture, twenty years later. They have 100% uptime. It’s the same principle as the Gary Kildall story, really. Don’t bet everything on one person, or one machine, or one location.
Ben Nichols: Looking forward, David – you’ve seen the PC revolution, the internet revolution, the mobile revolution with the iPhone. Are we in the middle of the next one with AI? Or is this just hype?
David Chapman: It feels like the iPhone moment in 2007. That appeared almost out of nowhere and changed everything. AI feels similar in its velocity.
But there’s a danger here. In the rush to adopt AI, we are forgetting the lessons of the last 40 years. We are connecting things that shouldn’t be connected. We are trusting outputs we don’t understand.
I see my role – and the role of consultancy in general – shifting. It used to be about making the technology work. “Can you make the printer print?” “Can you make the server connect?”
Now, the technology works. That’s rarely the problem. The role now is: “Should we use this?” “Is this safe?” “Is this ethical?” “Is this actually helping the human being at the end of the chain, or is it just adding noise?”
Ben Nichols: That ties back to the “Frame” beautifully. It’s about ensuring the technology serves the outcome, not the other way around.
David Chapman: Outcomes are everything. I worked on a project with Xantura involving data for social workers. We weren’t just “managing databases.” We were processing data to identify children at risk of abuse, so interventions could happen sooner.
When you strip away the servers and the cables and the code, that’s what we did: we helped save children. That’s the emotional connection. That’s the “why.”
Ben Nichols: And I suppose that’s the advice for the next generation?
David Chapman: It is. Be curious. Learn the tech. But never forget that at the end of every IP address, every database query, and every AI prompt, there is a person. They might be an accountant crying because you saved them a weekend of work. They might be a social worker trying to protect a child. They might be a CEO terrified of a data breach.
If you can help that person, you’ll always have a career. If you just focus on the machine, you’ll be obsolete in five years.
Ben Nichols: David, it’s been a privilege. Thank you for everything you’ve contributed to BN-IS over the years, you’ve been an incredible asset to the team. All the best in your retirement!
David Chapman: A pleasure, and thank you, Ben.