Every disruptive technology in human history has followed the same arc. The skeptics mock it, the wealthy adopt it first, a killer app unlocks the masses, and then -- one day -- you cannot imagine life without it. We have been here before.

By Gorgan | March 22, 2026 | Technology & Society

In August of 2002, on a late-summer episode of The Screen Savers on TechTV, hosts Patrick Norton and Martin Sargent sat across from a guest making an argument that most people watching probably shrugged off. The internet, the guest suggested, was not some unprecedented rupture in human civilization. It had happened before. Not the internet specifically -- but this. All of this. The confusion, the skepticism, the slow dawning realization that something was quietly rewiring the world.

"Within a couple of years since the inception of the internet, who would have imagined that every company would need to include a Web Address in every advertisement going forward?"

Then someone made a fan. Then a washing machine. Then a refrigerator. Then a radio. Then a television. The infrastructure had arrived first, and the ecosystem of purpose grew around it, slowly and then all at once. Within a generation, a home without electricity was not a home -- it was a ruin. The electric company became as essential as the water company, as unremarkable as the road outside your door.

The Screen Savers guest was not making a particularly original observation in academic circles. But hearing it said plainly, on a cable television program in 2002, with banner ads still a novelty and broadband still a luxury -- it had the quiet force of a prophecy. Because sitting here now looking back, it is difficult to argue with a single word of it.

The Pattern That Will Not Change

Disruptive technology does not follow a thousand different stories. It follows one story, retold with different costumes. The arc is consistent enough to be almost mechanical: a new capability emerges, it is expensive and inconvenient, only the wealthy or the obsessively curious engage with it, a critical mass of utility is eventually reached, infrastructure expands, a killer application unlocks mass adoption, a generation grows up never knowing life without it, and then a new disruption begins the cycle again.

What changes is not the shape of the story. What changes is the speed. And the speed is accelerating.

A Brief History of the Same Disruption

1440s -- The Printing Press

Johannes Gutenberg's movable type press was, at first, a machine for the Church and the wealthy. Books were luxury objects. Literacy was a privilege. Within a century, the press had shattered the Church's monopoly on information, ignited the Protestant Reformation, enabled the Scientific Revolution, and fundamentally destabilized every power structure that depended on controlling the written word. Those in power called it dangerous -- and they were right, just not in the way they meant.

"Why does a peasant need to read?"

1760s -- The Steam Engine

James Watt's improved steam engine was, in its earliest form, a solution to a mining problem -- pumping water out of coal mines. The idea of powering looms, locomotives, and ships was theoretical and distant. The wealthy industrialists who invested early were considered gamblers. Within 80 years, steam had remade geography itself: travel times that once took weeks collapsed to hours, trade networks once constrained by animal power expanded across continents, and entire cities rose from nothing around the railway lines.

"You want to replace the horse with a boiler?"

1880s -- Electricity

The Screen Savers guest was drawing on this example for a reason. Electricity arrived with a shrug. A light bulb that cost more to install than a year's worth of candles did not immediately read as civilization-altering. The infrastructure -- the wiring, the generators, the substations -- had to come first. The utility followed. Within two generations, the electrical grid was not a feature of modern life. It was the skeleton of it. Every subsequent technology of the 20th century was, in some sense, electricity's child.

"I already have gas lamps. They work fine."

1876 -- The Telephone

Western Union, when offered the patent for Alexander Graham Bell's telephone, famously declined. President William Orton dismissed the invention as an "electrical toy" and told investors it was practically worthless. Why would anyone need a machine to speak to someone across a wire when letters and telegrams served perfectly well? The telephone's killer app was not business communication -- it was the human need to hear a voice. By the mid-20th century, a business without a telephone number was not a real business.

"What would a man say on the telephone that he cannot put in a letter?"

1900s -- The Automobile

Early automobiles were toys for the wealthy. The roads were not built for them. The fuel infrastructure did not exist. They required mechanical skill to operate and broke down constantly. Cities were designed around horses. Critics pointed out -- correctly, for the moment -- that the horse was more reliable, cheaper to maintain, and did not require a separate fuel supply chain. Henry Ford's assembly line did not just make cars affordable. It revealed that the demand had always existed; it was only access that was missing.

"The horse has served us for ten thousand years. This is a fad."

1990s -- The Internet

This is the one the 2002 Screen Savers episode was grappling with in real time. The internet had existed in one form or another since the 1960s. But the World Wide Web, the browser, the email address -- these arrived in public consciousness in the early 1990s as novelties. By 1996, news anchors were explaining what the "@" symbol meant. By 2000, every television advertisement ended with a web address -- a thing that would have been gibberish five years earlier. By 2010, a business without a website was operating with one hand tied behind its back. By 2020, a business without a digital presence was functionally invisible.

"The internet is a fad. No one wants to shop without touching the product."

2007 -- The Smartphone

When Steve Jobs unveiled the iPhone, he called it a revolutionary product. He was understating it. The smartphone did not just replace the phone and the camera and the map and the music player. It relocated human attention. The smartphone became the first screen most people look at in the morning and the last screen they look at before sleep. Within fifteen years, entire economies had reorganized around mobile-first behavior. Entire generations had grown up with a supercomputer in their pocket as a baseline assumption of existence.

"Why would I want the internet on my phone? I have a computer at home."

2022 -- Artificial Intelligence

ChatGPT reached one million users in five days. It reached one hundred million in two months -- at the time, the fastest adoption of any consumer technology ever recorded. The comparison that most observers reached for was the internet. But the more honest comparison, given everything above, is simply: this is the pattern. The wealthy and the curious are in first. The infrastructure is building. The killer applications are still being discovered. We are currently in the "what do you even do with it" phase -- the light bulb phase, the horse-and-boiler phase. The ecosystem of purpose has not yet grown to match the infrastructure of possibility.

"It just makes things up. I don't trust it. My job is safe."

The Question Nobody Thinks to Ask

In August of 2002, who would have predicted that within five years a device would exist that put the entire internet, a camera, a music library, and a telephone in a single glass rectangle that fits in a shirt pocket? Who in 1920 would have predicted that within thirty years, moving pictures with sound would be transmitted wirelessly into a box in every American living room? Who in 1880 would have predicted that electricity would one day carry human voices, and then human images, and then eventually all of human knowledge, across any distance at effectively the speed of light?

The Screen Savers guest made the electricity comparison because it was the most recent prior example of infrastructure that arrived before its purpose was understood. But the honest answer is that every major disruptive technology in history was the electricity comparison for the people living through it. The printing press was the electricity of the 15th century. The steam engine was the electricity of the 18th. The telephone was the electricity of the 19th. The internet was the electricity of the 20th.

Artificial intelligence is the electricity of right now. Not because the comparison is poetic. Because the comparison is structural. The infrastructure exists. The killer app is being assembled in real time by millions of developers and companies simultaneously. The adoption curve is steeper than anything that came before it. And the people who are most confident that their particular corner of the professional world is immune to its effects are, historically speaking, the people who are most likely to be wrong.

"The people who are most confident their corner of the world is immune are, historically speaking, the people most likely to be wrong."

This is not a counsel of panic. The printing press did not eliminate writers -- it created an explosion of writing. The automobile did not eliminate travel -- it created an explosion of distance covered. The internet did not eliminate commerce -- it created an explosion of commerce. Disruptive technologies do not typically destroy human activity. They relocate it, reshape it, and massively expand the scale at which it operates.

But the shape of the activity changes. And the people who thrive in the new shape are rarely the ones who spent the transition arguing that the new shape was impossible.

The Web Address at the End of Every Ad

That observation from the 2002 episode is worth sitting with a little longer: the idea that within a few years of the internet's public emergence, every company on earth would feel compelled to include a web address in every advertisement they ran -- a thing that would have seemed absurd, then optional, then obvious, then mandatory.

Look at job listings today. Look at how many of them list AI fluency as a preferred skill. Look at how many companies have dedicated AI strategy roles. Look at how many products have an AI layer built in or bolted on. We are watching, in approximately real time, the transition from absurd to optional. The transition to obvious is coming. The transition to mandatory will follow.

There will be a version of the web-address observation for AI, and someone twenty years from now will make it, the same way Patrick Norton and Martin Sargent sat in a television studio in August of 2002 and marveled at an arc that, in retrospect, was always going exactly one direction.

They never see it coming. They never do. And then one day, they cannot imagine it having gone any other way.

The Real Gorgan -- therealgorgan.hashnode.dev

Preface

I recently stumbled across someone using the handle "RealGorgan" online.

The irony wasn't lost on me. Someone claiming to be the "real" version of a name I've used for over 26 years. At first, I didn't think much of it. Names get reused. People have similar ideas. The internet is a big place.

But it kept nagging at me. Not out of anger, but curiosity. In a world where anyone can claim anything, where digital identities can be fabricated with a few keystrokes, how do you actually prove you were there first?

TL;DR

• Someone started using "RealGorgan" about two years ago

• I've been using "Gorgan" since November 11, 1999 in Ultima Online

• I still have the original 3.5" floppy disk with screenshots from 1999

• I created a forensic disk image that preserves the original FAT12 filesystem timestamps

• The evidence is cryptographically verifiable

• Download the forensic disk image and verify it yourself

The Challenge

When you tell someone you've been using a name since 1999, what evidence can you provide?

Screenshots? Anyone can edit a JPEG.

File timestamps? Those change every time you copy a file.

Old forum posts? Most forums from 1999 don't exist anymore, and those that do have been migrated through multiple database systems, losing metadata along the way.

Web archives? The Wayback Machine is great, but it didn't archive everything, and a personal gaming handle wouldn't have been on public websites anyway.

In the age of deepfakes, AI-generated content, and digital manipulation, proving digital provenance is surprisingly difficult. You need something that can't be faked. Something with cryptographic integrity. Something physical.

But here's the thing: I had something better than any of that.

I remembered I had a floppy disk with something on it that could help!

The Evidence

The year was 1999. Dial-up internet. The satisfying screech of a 56k modem connecting. And Ultima Online, one of the first massively multiplayer online RPGs to exist.

That year I created a character named Gorgan and spent countless hours in that pixelated fantasy world. I was so proud of my character that I took screenshots and saved them to a 3.5" floppy disk. Because that's what you did in 1999. Cloud storage wasn't a thing. Social media didn't exist. You saved your digital memories to physical media and hoped the disk didn't get corrupted.

My character Gorgan in Ultima Online, November 11, 1999

You might notice the first screenshot has some distortion at the bottom. That's not damage from age or a corrupted file. It was like that in the original screenshot for some reason. Maybe a glitch in the game's screenshot function, maybe something with my ancient video card. Either way, it's been there since 1999, preserved exactly as it was captured.

Another shot from the same day

That floppy disk sat in a drawer for over two decades. I forgot about it. Life moved on. The internet evolved. But the name stuck with me. Gorgan became my handle everywhere, from chatrooms and forums to GitHub and professional profiles.

Years later, while playing on UO Gamers: Hybrid (a free Ultima Online shard), someone impersonated my character. In response, I started adding "The Real" prefix to all my character names. It was a defensive move, a way to distinguish myself from the impostor. Eventually, "The Real Gorgan" became another variation I used interchangeably with just "Gorgan."

The irony isn't lost on me that now, decades later, someone else has adopted "RealGorgan" as their handle. History repeating itself, but this time with the roles reversed.

And when I saw it, I knew exactly where to find my proof.

The Investigation

I dug through old storage boxes and found it. A dusty 3.5" floppy disk with "UO Screenshots" scrawled on the label in permanent marker. My handwriting from 1999.

Using a USB floppy drive (yes, they still make those), I didn't just copy the files off the disk. I created a complete forensic disk image of the entire floppy, capturing every single byte including the filesystem metadata that contains the original timestamps from when the files were created.

The result: a 1.44 MB disk image file that's a perfect snapshot of that floppy disk as it existed 26 years ago.

Download the forensic disk image (1.44 MB)

What the Disk Reveals

The floppy uses an old filesystem called FAT12, which stores the exact date and time each file was created. This metadata is embedded in the raw disk structure itself and can't be faked without changing the entire disk image, which would completely alter its cryptographic fingerprint.

When you examine the disk image, you'll find two JPEG files:

• UO0002.JPG: Created November 11, 1999 at 5:04:08 PM

• UO0006.JPG: Created November 11, 1999 at 5:07:40 PM

These aren't "modified" dates that could be changed by copying files around. These are the original creation timestamps as written by Windows 98 or Windows ME in 1999, stored in the FAT12 directory structure.

The Digital Fingerprints

To prove nothing has been tampered with, here are the SHA-256 hashes (digital fingerprints) of everything:

Disk Image:

gorgan_floppy_1999.img
SHA-256: a49f14c99d947a902da7ddd1536d11fe53d010e3cbb84c81c0e356a9dda64331

Screenshots:

UO0002.JPG
SHA-256: fdf4174a9f0cf9bfc0be5c5660644e8bab6ecbe50983d1caf7ebae00a08cea7f

UO0006.JPG
SHA-256: 11ab252c3217ede84e7d48a8b75ac2c3a9cf726ecf4ffd129a30013971855ad5

If even a single bit were different, these fingerprints would be completely different. The integrity is verifiable.

The Verdict

Looking at these screenshots now, I'm hit with a wave of nostalgia. The chunky pixel art. The isometric view. The simple joy of exploring a virtual world when the concept of "virtual worlds" was still new and exciting.

Ultima Online was more than just a game. It was where a generation of us learned about online communities, digital identities, and the strange new frontier of living part of your life on the internet. We were pioneers in a way, figuring out who we wanted to be in digital spaces before those spaces became as real and important as physical ones.

And somewhere in that journey, I became Gorgan. Not because I was trying to build a brand or claim a namespace. Just because I needed a name, and that one felt right.

In a world where digital identity matters more than ever, where your online presence can be as important as your offline one, this floppy disk is more than just nostalgia. It's a time capsule from the early internet, preserved in magnetic oxide on a plastic disk, containing cryptographic evidence that anyone with basic technical knowledge can verify.

The Record

I'm not writing this to start a fight with whoever is using "RealGorgan" now. Maybe they didn't know. Maybe they thought the name was available. Maybe they have their own reasons.

But the record should be clear:

The name Gorgan has been mine since November 11, 1999.

Before MySpace. Before Facebook. Before Twitter. Before GitHub. Before "RealGorgan."

Twenty-six years later, it still is.

For the Technically Curious

If you want to verify the timestamps yourself, you can mount the disk image on Linux, Mac, or Windows. The modification dates are stored at offset 0x2600 in the disk image, in the root directory entries.

Mounting on Linux/Mac

# Download the image
wget https://gorgan.dev/user/themes/gorgan/images/gorgan_floppy_1999.img

# Mount it (Linux)
sudo mkdir /mnt/floppy
sudo mount -o loop,ro gorgan_floppy_1999.img /mnt/floppy
ls -la /mnt/floppy

# Mac
hdiutil attach -readonly gorgan_floppy_1999.img

You should see the two JPEG files with November 11, 1999 timestamps.

Mounting on Windows

Windows doesn't natively support mounting raw floppy disk images, but you can use the free ImDisk Toolkit:

1. Download and install ImDisk Toolkit

2. Right-click the gorgan_floppy_1999.img file

3. Select "Mount as ImDisk Virtual Disk"

4. Choose a drive letter and click OK

5. Open the mounted drive in File Explorer

6. Right-click on the JPEG files and select Properties to view the creation dates

The timestamps will show as November 11, 1999.

About the FAT12 Format

The disk uses the standard FAT12 format used by 1.44MB floppy disks in the 1990s. The date encoding uses a 16-bit format where bits 0-4 are the day, bits 5-8 are the month, and bits 9-15 are the year offset from 1980.

For UO0002.JPG, the raw date word is 0x2796, which decodes to November 11, 1999.

Download the disk image and verify it yourself. The evidence is all there.

Every modern innovation, from the servers that power the web to the AI models reshaping our future, stands on the shoulders of the open-source community. Before I dive into my own work, I want to take a moment to thank the thousands of developers who contribute their time and expertise to the public good.

Building for the public isn't just about writing code; it's about creating a digital public good that ensures technology remains accessible, transparent, and collaborative.

My Open Source Journey

In my own work at Gorgan's Lab, I've made it a priority to keep the majority of my projects open source. I believe that tools are most powerful when they are shared and refined by the community. From VS Code extensions that enhance developer productivity, to community gaming servers, to communication tools that preserve digital history, these projects embody the philosophy that knowledge and tools should be freely accessible to all.

The Legal Truth: Code is Speech

The connection between open source and freedom of speech isn't just a metaphor; it is a legal reality. In the landmark case Bernstein v. United States, the courts recognized that source code is a form of protected expression under the First Amendment.

Just as a poet uses words to convey an idea or a mathematician uses equations to describe the universe, a developer uses code to communicate logic and intent. When we open-source our work, we are exercising our right to "speak" in the language of the 21st century.

Why We Must Protect This Freedom

The four essential freedoms of free software (the freedom to run, study, change, and redistribute) are increasingly under threat from restrictive licensing, over-regulation, and centralized control.

Protecting open source is about more than just software; it is about protecting the freedom of speech itself. If we lose the right to share our code openly, we lose the right to innovate without a gatekeeper. We must remain vigilant against policies that seek to treat code as a dangerous "munition" rather than the expressive, creative work that it is.

A Call to Action: Learning from History

As we approach Martin Luther King Jr. Day,

We are reminded that progress has never come from passivity. Dr. King's legacy teaches us that remaining idle in the face of injustice is itself a choice, and history has not been kind to those who stood by while freedoms eroded.

Dr. King wrote from Birmingham Jail: "Injustice anywhere is a threat to justice everywhere." Today, that injustice extends into the digital realm. When code is restricted, when knowledge is gatekept, when technology is controlled by a concentrated few, we face a new form of tyranny. The oligarchic consolidation of technological power threatens the very principles of open innovation and democratic access to knowledge.

History shows us that transformation requires mobilization. The Civil Rights Movement succeeded not because people waited for change, but because they organized, spoke out, and refused to accept the status quo. Similarly, the open-source movement must be more than a technical preference; it must be a conscious stand against the centralization of power and knowledge.

This MLK Day, we should ask ourselves: Are we idle observers, or are we active participants in protecting digital freedom? The tools we build, the code we share, and the communities we foster are acts of resistance against a future where innovation is locked behind proprietary walls and controlled by the powerful few.

Conclusion

Open source is a technical expression of democracy. It is a world where the best idea wins, and where everyone has a seat at the table. But democracy requires vigilance, courage, and action.

Let's honor Dr. King's legacy by refusing to be idle. Let's keep building, keep sharing, and above all, keep protecting our right to speak in code. The fight for digital freedom is the civil rights movement of our time, and history will judge us by whether we stood up or stood by.

Over the past couple of years, I’ve developed several software projects by leveraging the power of AI. My workflow has evolved significantly:

• The Early Days: Heavy reliance on copying and pasting between platforms like ChatGPT.

• The Shift: The introduction of Claude made the experience more efficient and rapid.

• The Modern Stack: Using MCP Servers and detailed prompt instructions to build complex systems.

This evolution has made my development process more dynamic and innovative. I’m eagerly anticipating future advancements as I prepare to build even more ambitious projects.

Join the Conversation: How do you incorporate AI into your daily life? Do you use it professionally? Has it enabled you to achieve tasks that were previously impossible? I’d love to hear your thoughts in the comments!

Tips for Harnessing AI in Your Projects

If you're looking to integrate AI into your own workflow, here are a few best practices to keep in mind:

• Start Small: Begin with minor projects to understand the capabilities and limitations of your tools.

• Stay Updated: AI technology is rapidly evolving; keep an eye on new features to maximize your efficiency.

• Experiment with Tools: Explore different platforms to find the specific features that suit your unique workflow.

• Leverage Community: Join forums and social groups to gain insights and support from other builders.

• Focus on Data Quality: Ensure your input data is clean and relevant for more accurate outcomes.

• Iterate and Improve: Be prepared to refine your models and processes based on feedback and results.

• Consider Ethics: Be mindful of privacy, bias, and transparency in your AI solutions.

• Document Your Process: Keep records of challenges and solutions for future collaboration.

By incorporating these tips, you can effectively utilize AI to transform your ideas into reality.

Do you ever feel like you wish you could clone yourself to get more work done in a day? Why does there never seem to be enough time in the days to get what we want done?

I often wish I could come up with a strict schedule—you know, the kind where you work on Project A for two hours, then switch to Project B at exactly 11:00 AM. I try to micro-manage my time, but I find it impossible the second I get "lost in the code." Once I'm deep into a problem, that schedule becomes a cage.

Then, when the timer finally goes off, I don't want to stop. I'm in the zone. I've finally built up the mental map of the entire system, and walking away feels like I'm about to let a sandcastle wash away. Do you ever feel that way?

The Hidden Cost of Switching

The reason that "strict schedule" feels so wrong is actually scientific. Research shows that it takes a developer about 23 minutes to fully get back into a state of deep focus after a single interruption.

When we try to juggle four projects in one day, we aren't just splitting our time; we are paying a massive "cognitive tax" every time we switch. We spend half our energy just "reloading" the context of the next project into our brains. No wonder we feel like we need a clone—we're losing hours of our day just to the act of switching gears.

A Different Way: "Day Theming"

Instead of fighting your brain with hourly schedules, have you ever tried Day Theming?

Rather than micro-managing your hours, you manage your days. You dedicate all of Monday to Project A and all of Tuesday to Project B.

Why it works: It respects your "flow state". You don't have to stop just as you're getting started because you have the whole day ahead of you. It eliminates that "start-up cost" and reduces the decision fatigue of wondering what you should be doing next.

The Art of the "Context Dump"

But what about those nights when you're deep in the zone and know you should stop, but you're terrified you'll lose your train of thought?

I've started using a "Context Dump" throughout and at the end of the day. Before I stop working on any task or close my IDE, I write a quick, messy note to my future self:

"I was halfway through the auth refactor. The next step is fixing the JWT expiration logic. Look at the console log on line 42 for the current error."

It's like leaving a "Save Point" in a video game. It gives me the "permission" to stop working because I know I won't have to spend an hour tomorrow morning figuring out where I left off.

Protecting the "Lab"

At the end of the day, we have to remember that we aren't machines. Working non-stop because we're "in the zone" is a great feeling, but doing it every night is the fastest route to burnout.

The goal isn't just to do more work—it's to do better work without losing ourselves in the process. We need to find ways to honor that "lost in the code" feeling while still making sure we actually have a life outside of the screen.

So, next time you feel like you're drowning in projects... maybe don't reach for a stricter schedule. Try giving yourself more space to stay lost in one thing at a time.

Tools to Support Your Flow: VSCode Extensions

To make Day Theming and Context Dumps even easier, I've found two amazing VSCode extensions that keep everything you need right in your editor.

🗂️ Better Sidebar Markdown Notes

Enhanced markdown notes directly in your sidebar

Instead of switching to another app to jot down your context dumps, Better Sidebar Markdown Notes lets you keep your notes right there in VSCode. Create multiple pages, auto-save as you type, and even sync with the cloud for access across devices.

Key Features:

• Multiple pages with easy navigation

• GitHub Flavored Markdown support

• Auto-save functionality with configurable intervals

• Cloud sync support for seamless access anywhere

• Advanced backup and restore capabilities

• Custom storage locations (workspace or custom path)

This is perfect for those context dumps—quick, messy notes that keep your thoughts from scattering when you need to step away from the keyboard.

Install Better Sidebar Markdown Notes →

✅ Google Tasks for VSCode (with Calendar)

Manage your Google Tasks directly from VSCode without leaving your editor

Day Theming requires planning, and Google Tasks for VSCode brings your task management seamlessly into your development environment. No context switching, no alt-tabbing to another app—just your tasks and your code side by side.

Key Features:

• View your entire Google Tasks list in the sidebar tree view

• Create, edit, and delete tasks without leaving VSCode

• Calendar integration to see due dates and events

• Real-time sync with your Google Tasks account

• Secure OAuth 2.0 authentication

• Full CRUD operations for task management

Whether you're organizing your Day Theming schedule or tracking what needs to happen when, this extension keeps your tasks visible and accessible. You can even see which tasks have deadlines coming up—essential when you're dedicating entire days to specific projects.

Install Google Tasks for VSCode →

The Complete Flow

Here's how they work together:

1. Plan your week with Google Tasks — Use the extension to organize which project gets which day

2. Dive deep into your day — Let yourself get lost in the code, knowing interruptions are minimized

3. Document your progress — Use Markdown Notes for quick context dumps before you leave

4. Pick up seamlessly tomorrow — Your notes are waiting, your tasks are organized, and you're ready to dive back in

The beauty of these tools is that they live right in your editor—no tab switching, no mental friction. Just you, your code, and the tools that help you stay focused.

What do you think? Does the idea of Day Theming feel like it would give you more freedom, or does it sound just as scary as a strict schedule? And have you found tools that help you protect your flow state?