The Programmer Who Saw 2026 in 2008 | EddieSilva.com
A conversation from around 2008, the AI future I did not fully understand, and the professional advantage of staying curious.
I do not remember the exact year. Maybe I wrote about this before. Maybe somewhere in an old note, an email, a draft, or one of those digital corners where memories go to wait patiently, I was more precise. Maybe I even mentioned the date. But age has a way of sanding down the edges of memory. So does bourbon without ice. What I remember is not the calendar. I remember the conversation. It was probably around 2008. I was talking with a close friend of mine, a programmer working at a large company here in the United States. He was not speaking like someone repeating a trend. He was not trying to sound futuristic. He was not doing one of those dramatic speeches people give when they want to impress you with technology. He was simply fascinated. I could see it on his face. There was a light there — the kind of light people have when they are not just explaining something, but seeing something. He was talking about artificial intelligence with the kind of conviction that makes you listen, even when you do not fully understand what you are hearing. And I confess: at that moment, I did not give it the attention it deserved. What he was saying sounded fascinating, yes. But it also sounded a little foolish. Too far away. Too abstract. Too much like science fiction dressed in technical language. Artificial intelligence? For programmers? For research? For medicine? For work? For real life? At the time, it sounded like one of those ideas that may become important “someday,” which is usually another way of saying, “not now.” So I listened politely. I respected him. I knew he was intelligent. But I did not understand the size of what he was trying to tell me. Time passed. Years passed. The world changed quietly, then suddenly. And then ChatGPT arrived. I had the privilege of being among the early users who accessed and tested this new tool from OpenAI. I did not know exactly where I was stepping. I did not have a grand strategy. I did not fully understand the universe that was opening in front of me. But I entered. And that was one of the best decisions I made. At first, it felt like curiosity. Then it became habit. Then it became a door. Then it became a completely new way of thinking about work, writing, programming, research, strategy, systems, creativity, and execution. I remember receiving emails from OpenAI about APIs and developer access. I remember seeing things that, at the time, I did not treat with enough seriousness. I looked at some of it and thought, “Interesting.” Then I moved on. A few weeks later, I regretted it. Not because it was too late. It was not too late. But because I could already sense that something was moving faster than most people understood. The ecosystem was forming. The tools were getting stronger. The conversation was changing. And the people who were paying attention were not just learning a product. They were learning a new language. By 2023, I finally understood what my friend had been trying to show me back around 2008. It took me a long time. Fifteen years, more or less. That is a humbling thing to admit. But I am grateful. I am grateful because I woke up before the wave became impossible to ignore. I woke up before many people started treating AI as a normal part of their professional life. I woke up before the conversation became only noise, fear, hype, panic, and reaction videos. I had enough time to understand that this road had no return. And that brings me back to the point of that old conversation. The person who gave me the first real warning about artificial intelligence was not a marketing person. He was not a futurist selling a keynote. He was not someone trying to build a personal brand around fear. He was a programmer. And that matters. Because even then, he did not see AI as a villain. He did not speak about it as a threat waiting in the dark to destroy his profession. He did not present it as something that would replace the mind of the developer. He saw it as a tool. A powerful tool, yes. A disruptive tool, certainly. But still a tool. He saw it as something that could help programmers think better, test faster, build differently, and reach places that manual effort alone could not reach. He saw it as an extension of the craft, not the death of the craft. Today, as a programmer myself, I understand that in a much deeper way. AI does not remove the need for judgment. It increases the value of judgment. AI does not remove the need for taste. It exposes the lack of taste. AI does not remove the need for discipline. It punishes people who have none. AI can generate code, but it cannot know what kind of product you are really trying to build unless someone gives direction. It can suggest architecture, but it cannot carry responsibility. It can help you move faster, but it cannot decide whether you are going in the right direction. That is still our job. The developer who understands AI as a partner becomes more dangerous in the best sense of the word. More capable. More curious. More productive. More willing to experiment. Less trapped by the blank screen. The developer who treats AI only as a threat may lose valuable time fighting the weather instead of learning how to sail. I do not say this with arrogance. I say it because I almost missed the point once. In 2008, or whatever year that conversation really happened, my friend was describing a future I could not yet see. I heard the words, but not the music. I understood the topic, but not the direction of history. In 2023, I finally heard it. And by 2026, it became obvious to me that he had seen further than most of us. He saw a world where artificial intelligence would not belong only to laboratories or science fiction. He saw it entering the daily work of people who build things. He saw developers using it not as magic, not as a toy, but as a serious instrument. I tip my hat to him. Not because he predicted every detail. Nobody does. But because he had the correct posture toward the future. He was not afraid of it. He was curious. That may be the most important lesson in all of this. Technology changes. Tools change. Programming languages rise and fall. Platforms come and go. What looks impossible in one decade becomes ordinary in the next. But curiosity remains one of the greatest professional advantages a person can have. I wish I had understood him sooner. Still, I am glad I understood him eventually. Sometimes the future does not arrive as thunder. Sometimes it arrives as a conversation with a friend, years before you know what he is really telling you. And sometimes, many years later, you sit down, older, grateful, maybe with a bourbon without ice, and realize: He was not being foolish. He was early.
Thank you, Ismenio.
Thank you for seeing something before many of us had language for it. Thank you for talking about artificial intelligence when it still sounded distant, strange, almost unreasonable. Thank you for not speaking about it like a salesman, a prophet, or a frightened man guarding the past.
You spoke like a builder.
At the time, I listened with respect, but not with the right kind of attention. I understood that you were serious. I understood that you were intelligent. I understood that you were fascinated. But I did not yet understand that your fascination was a form of professional vision.
You were not trying to predict every detail.
You were recognizing a direction.
There is a difference.
A good friend does not always change your life with advice. Sometimes he changes it by paying attention to something before you do. Sometimes he plants a thought that waits for years. Sometimes he says something that sounds too early, and only later do you discover that too early was exactly the point.
You gave me one of those thoughts.
I almost missed it.
But I did not lose it.
So this article should not end only with the idea that AI arrived and I eventually learned to use it. It should also include the friend who saw the road earlier and spoke about it with excitement instead of fear.
That posture matters.
It mattered then.
It matters even more now.
So, thank you, Ismenio.
Thank you for being early.
Thank you for paying attention.
And thank you for leaving a signal that took me years to fully hear.