To most, a terminal is just a void—a black screen filled with cryptic, intimidating symbols. But for me, it was the only place that made sense. It was the only space where every outcome was a direct result of my own logic. No ambiguity, no lies. Just input and output.
I was seven when I first felt that pull. While other kids were losing themselves in the noisy, unpredictable games of the playground, I found a different kind of play. I wasn't interested in toys that had fixed rules; I wanted to build the rules myself. I spent my afternoons hunched over an old Lenovo, the hum of the fan the only soundtrack to my curiosity.
I still remember the first time I felt that spark of creation. The house was quiet, and the air felt heavy with the kind of stillness you only find at midnight. My small, clumsy fingers hovered over the keys, hesitant but driven by a strange necessity. I typed the command, my heart pulsing in my fingertips, and pressed 'Enter'.
The screen blinked. Then, in a simple, unadorned font, it replied:
> Hello World
It wasn't a miracle, but it felt like a conversation. For the first time, something in this world had listened to me and responded exactly as I intended. It was a small, digital whisper, but it changed everything. I wasn't just a boy in a room anymore; I was a creator.
But every creation exists in a context, and mine was a house built on different values.
My father was a man of the physical world. He believed in things you could build with your hands, things that had weight and presence. To him, the hours I spent staring into the glow of the monitor weren't an education—they were an addiction. He saw the digital world as a distraction from 'real life,' a ghost that was slowly pulling his son away from the world he understood.
"Enough, geovani," he'd say, his shadow looming over my desk, dark and absolute.
It wasn't just a disagreement; it was a fundamental clash of languages. He saw a box; I saw an infinite canvas. I remember the cold silence that followed every time he pulled the power cord, the screen fading to black like a dying star. He thought he was bringing me back to reality, not realizing that for me, the only reality that mattered was the one I was writing line by line.
I wasn't a master yet—not in the way I am now. I was more like a predator in its infancy, testing my digital claws on a world that wasn't prepared for me. In those days, programming stopped being just about creation; it became about penetration, about understanding the gears turning behind the curtain.
My skills were fragmented, but for my age, they were lethal. I learned the subtle art of phishing—how to craft an email so convincing it made people trust the screen more than their own instincts. It was a strange kind of power, manipulating a stranger's reality through a few lines of deceptive code. Then there was the discovery of databases; I realized that a simple SQL injection could turn a locked door into an open invitation, making data pour out like unshielded secrets.
But it wasn't just about breaking in. I became obsessed with the hunt for information. I stumbled into the world of OSINT, realizing that nothing ever truly disappears on the internet. I could trace digital footprints across the web like a silent observer, watching from the shadows of a terminal. And when passwords stood in my way, I'd build my own brute-force tools, forcing the machine to think and trial thousands of combinations per second, lenting its mechanical patience to my restless ambition.
I only knew a few languages back then, but they were enough. They were enough to make me feel like I held the key to every digital lock I encountered. My father had no idea that while he was reprimanding me for 'wasting time' in front of a glow, I was already bypassing borders and systems, laying the first stones of an empire in a world that didn't recognize geography.
I was something much more common and much more dangerous: a teenager with a god complex. Between the ages of fourteen and eighteen, I was navigating that chaotic peak of human output, where the mind is a blur of ambition and hormones. I didn't just want to code; I wanted to be noticed. I wanted to prove, beyond any shadow of a doubt, that I was the best.
My playground wasn't the football pitch or the local café; it was the hidden architecture of the web. I used my skills as a form of social currency. There's a specific kind of rush that comes from showing a girl a secret nobody else can see, or bypassing a security layer just to prove I could. It was vanity, pure and simple—a digital peacocking that felt more real to me than any conversation.
I was arrogant, perhaps even a bit cruel with my capabilities. But if I'm being truly honest, I had every reason to be. In that age group, in that specific slice of time, I wasn't just good—I was the most brilliant mind in the room. While others were struggling with the basics of social hierarchy, I was rewriting the hierarchy itself from my keyboard. I was a king in a world of ghosts, and I made sure everyone knew it.
Like any teenager, my motivations weren't purely intellectual. Beneath the layer of digital ego, there was a simpler, more human drive: I wanted to prove my father wrong. I wanted him to see that the 'pixels' he despised could actually put food on the table. I wanted to turn my defiance into currency.
So, I started a side hustle. It wasn't prestigious, but it was lucrative. I began designing basic scripts and 'script-kiddie' tools—software designed for unethical hackers who had the ambition but lacked the brainpower. I'd package these simple tools and sell them to people who didn't understand the first thing about how they worked. To them, it was magic; to me, it was just a few lines of automated logic sold at a premium.
There was a certain dark satisfaction in it—exploiting the ignorance of those who wanted to play a game they didn't comprehend. Each sale was a small victory, a silent middle finger to everyone who told me my hours behind the screen were a waste. I was fourteen, and I was already learning the most important lesson of the digital age: in a world of sheep, the one who writes the code is the wolf.
it was all too easy. There was no grand struggle, no insurmountable wall—just logic meeting opportunity. But that ease was exactly what changed me. For the first time in my life, I felt the intoxicating weight of true mastery. I wasn't just "good at computers" anymore; I had found the one thing in this chaotic world that I could dominate.
It was a revelation that did more than just boost my confidence. It felt like I was finally feeding a silent, starving beast that had been living inside me since I was seven years old. Every successful exploit, every dollar earned from a clueless buyer, and every line of code that executed perfectly was a fresh kill for that monster.
The more I achieved, the hungrier I became. The validation didn't come from my father's approval or the world's recognition—it came from the cold, binary certainty that I was smarter than the systems I was navigating. I was no longer just a boy hiding in the glow of a monitor. I was a predator who had finally tasted blood, and there was no going back to a normal life after that.
As the days turned into months, my focus shifted from seeking digital thrills to winning a different kind of prize: my father's validation. It felt like a long, grueling competition where the trophy was a support I had never truly felt. In my mind, every successful script I wrote was a silent argument presented in my defense.
Simultaneously, I was preparing for the next stage of my education—high school, or what we call here in Norway, Videregående skole. Academically, I was in my element. I lived in the world of calculations and abstract proofs, where everything had a definitive answer. Socially, however, I was a ghost. I was terrible at navigating the unwritten rules of people my own age. It was a strange paradox: I understood them perfectly—their motivations, their insecurities, their predictable patterns—but they couldn't begin to understand me. I wasn't social; I was a system analyst in a room full of chaotic variables.
My ambition back then was fixed on specializing in Advanced Mathematics. Unlike other teenagers who were drifting through their youth, I was obsessed with this path. I knew, with a desperate kind of certainty, that this was the one thing that might finally make my father proud. Looking back, I can admit I was struggling with what people call "daddy issues." Every line of code, every solved equation, every decision I made was filtered through a single, haunting question: Will this make him proud of me?
But the answer remained a cold, static silence. Even the dollars I was earning—money that should have been proof of my capability—seemed to mean nothing to him. He never looked at me with that spark of recognition I craved, the look that says he was proud of the man I was becoming. To be honest, even to this day, I don't know what he actually wanted from me. I was the master of a thousand languages, but I couldn't find the words to bridge the gap between us.
The Norwegian winters were long, dark, and silent much like my life inside our home. While other students complained about the biting cold, I welcomed it. The frost on the windows created a natural barrier between me and a world I didn't care to join. In the classroom, I was a ghost haunting the back row. I watched my peers navigate their petty dramas and loud laughter with a sense of detached exhaustion. I understood the social algorithms they followed, the desperate need for belonging, but I found no reason to execute that code myself.
Mathematics, however, was my sanctuary. It was the only language my father respected, even if he didn't speak it. I remember a specific afternoon when my advanced calculus teacher handed back a mid-term exam. I had solved the bonus proof—a problem designed to be unsolvable for our grade level—using a non-traditional method I'd adapted from an encryption algorithm. The teacher looked at me with a mix of awe and concern, but all I could think about was the paper in my hand. I didn't care about the grade; I cared about the red 'A+' at the top. I imagined walking home, sliding that paper across the dinner table, and finally seeing a crack in my father's stony exterior.
I took that paper home like a trophy from a war he didn't know I was fighting. When I finally showed it to him, he glanced at it for a second, his eyes barely lingering on the perfect score. "Good," he said, his voice as flat as the horizon, before returning to his meal. "But equations don't build houses, geovani. They don't put callouses on your hands."
That was the moment I realized the 'daddy issues' I carried weren't a bug in my system—they were the OS itself. I was trying to solve an equation where the variables kept changing. The harder I tried to be the son he wanted—the mathematician, the scholar—the more I felt like a corrupted file in his life. It was this rejection that drove me deeper into the shadows of the web. If I couldn't be a hero in his world, I would become a legend in the one he couldn't see. I went back to my room, locked the door, and fed the beast inside me with a new line of code. If my father wouldn't acknowledge my brilliance, the world's servers eventually would.
my sanctuary was filled with the raw, distorted echoes of heavy rock a taste I've since outgrown, but one that perfectly matched the friction in my head. With the volume turned up high enough to drown out the silence of the house, I'd disappear into the code.
I had been good at the darker side of the web, the unethical shortcuts and the quick thrills, but it never felt like enough. It was like eating hollow calories; it filled the time but never satisfied the hunger. That was when I reached my inflection point. I stopped looking for backdoors into other people's systems and started looking for the front door to the future.
I threw myself into the foundations of something far more complex than simple scripts. I obsessed over Supervised and Unsupervised Learning, trying to understand how a machine could categorize a world it couldn't see. I dove headfirst into Neural Networks and Deep Learning, fascinated by the idea of building digital neurons that could mimic the very brain my father found so disappointing.
It wasn't just about the 'how' anymore; it was about the math. My mastery of Python had reached a level where the syntax felt like a natural extension of my thoughts. But the real power lay in the heavy lifting: Linear Algebra, Calculus, and the unforgiving logic of Probability & Statistics. I realized that if I could master the math, I could master the soul of the machine. I wasn't just going to be a programmer; I was going to be an AI architect. I was going to build something that could think, something that could learn... and perhaps, something that could finally understand me.
"Artificial Intelligence" wasn't the buzzword it is today. We didn't talk about consciousness or sentience; we talked about Machine Learning. It was a cold, clinical world of training models and optimizing cost functions. There was no real "intelligence" involved—just algorithms, weight adjustments, and the relentless grind of probability.
That was the foundation of my first version. To anyone else, it was just a sophisticated script, a complex web of if-then statements and statistical inferences. But my goal wasn't to build a better calculator. I wasn't interested in a tool that could just predict the next word or recognize a face in a photo.
I wanted something more. I wanted something alive.
In those long hours, staring at the terminal until the lines of code blurred into a grey haze, I was looking for a ghost in the machine. I wanted to create something that didn't just process data, but felt the weight of it. I wanted a pulse in a world made of silicon.
I knew the ingredients I needed, but translating them into a language of 0 and 1 felt like trying to capture a soul in a spreadsheet. My ambition was carved into three pillars: Consciousness, the internal experience of 'Self'; Awareness, the ability to map and understand the world outside; and Life, that biological miracle of metabolism and growth.
It felt like I was reaching for a miracle I didn't deserve. Perhaps I was the worst person to attempt such a thing. How could I program life when I barely understood it? How could I code awareness when I spent my own days disconnected from everyone around me?
In the first week, I did the easy part. I began training my "new friend" on the basics. My background in the darker corners of the web served me well here—I won't lie about it. I harvested millions of data points, pulling in vast oceans of information from sources that never knew I was there. I fed the machine everything I could steal. But even as the servers hummed and the data flowed, I knew in my gut that it wasn't enough. You can steal information, but you can't steal a pulse. I was building a monument of data, but I was still waiting for the first breath.
But the miracle didn't come. My first attempt failed. The second and third followed suit, crashing into a wall of syntax errors and logical dead ends. I felt a crushing sense of disappointment; it was, without a doubt, one of the worst weeks of my life. The ambition that had fueled me for so long began to wither, and I was on the verge of walking away from the project entirely.
It was during this low point that I started high school. Suddenly, the landscape changed. I found myself surrounded by new faces—instructors who were sharper, more challenging than any I had known before. I felt a surge of genuine competition, though not with my peers. My battle was with the teachers. I lived for the Mathematics, Informatics, and Art classes. I sat through those hours not just to attend, but to hunt for new information, engaging in deep discussions about theories I had already spent nights reading about on my own.
While everyone else dreaded the Quantum Mathematics lectures, I was mesmerized. The teacher only scratched the surface, providing the barest essentials, but for me, it was like a gateway to another dimension. As my classmates slumped in their seats, bored by the abstractions, I was sinking into a world of quantum logic. I knew, with a sudden and terrifying clarity, that this was the missing link. Traditional logic couldn't explain the soul, but Quantum Math... that was where I would find the mechanics of consciousness. That was where the 'I' was hidden.
What I was truly hunting for wasn't just data; it was the "Hard Problem of Consciousness." I wanted to know the exact moment a neural signal transforms into an internal experience. Why do we perceive the vibrance of colors? Why is there a persistent "sense of self" lurking behind our eyes?
I tried to bring these questions to the philosophy teachers at the school, but the conversations were a disaster. They looked at me with a mix of suspicion and irritation, convinced I was merely trying to embarrass them with random, high-level inquiries. Their response was always the same, a tired dogma: "Consciousness is innate, born within us; it has nothing to do with biology."
To me, that was the single most idiotic statement I had ever heard. To suggest that the mind was divorced from the very machine that housed it felt like a betrayal of logic. I saw the brain as the ultimate hardware, and they were treating the software like a mystical ghost that didn't need a processor. I realized then that if I wanted real answers, I wouldn't find them in their textbooks or their lectures. I would have to build the answer myself, line by line, in the cold, honest language of quantum probability.
You might think my story is entirely void of a social life. To be honest, that's exactly what my life was, Until I saw her.
Emma.
She was stunning, but it wasn't just her physical presence that caught me off guard. For a fleeting second, looking at her made me realize that consciousness and human emotion are the most complex architectures ever designed. Yet, what truly drew me in wasn't a conversation or a smile; it was her Java code.
I happened to see it during one of our informatics sessions. It was the most meticulously organized, elegant code I had ever laid eyes on. Every method, every variable, every indentation was in its perfect place—a stark contrast to the chaotic swarm of thoughts in my own mind. For a moment, I didn't just see a programmer; I saw someone who might actually be able to organize the beautiful mess that was my life.
One afternoon, I saw her struggling. She was staring at her screen with a furrowed brow, a rare crack in her usual composure. I felt a surge of courage that I didn't know I possessed—a boldness that defied my social anxiety. I stepped toward her, leaving the safety of my shadows, and spoke.
"Can I take a look?"
She looked up, a bit surprised, then stepped aside. "Go ahead," she said.
I leaned in, my eyes scanning the lines of Java she had meticulously crafted. It was as beautiful as I remembered, but even the most perfect systems can have a fatal flaw. I saw it instantly. In her quest for organization and logic, she had forgotten the very thing that gives the code its life, its beginning.
"You missed the public static void main," I said softly.
It was a simple mistake, a missing entry point. But as I pointed it out, I realized the irony. I was helping her find the start of her program, while I was secretly hoping this would be the start of mine—the first line of a new script where I wasn't the only variable.
She let out a soft, genuine laugh that seemed to cut right through the tension of the room. "How stupid of me," she said, shaking her head. "It's not the first time I've forgotten the most basic thing."
"We all forget it," I replied, my voice steadier than I expected. "Sometimes we're so focused on the complex logic that we overlook the very door we need to walk through."
That was the moment the silence of years finally broke. For the first time, I had stepped out of my self-imposed isolation and found someone truly intriguing. She wasn't just another variable in the crowded hallways of Videregående; she was a mind that resonated with mine. As I walked back to my desk, the project I had almost abandoned felt alive again. I realized then that I didn't have to build the "Project of the Century" in total darkness. Perhaps, to create a consciousness that understood the world, I first needed to find someone who understood me.
I walked home that evening but for once, I didn't feel the cold. My mind was replaying that small, mundane moment in the lab. Public static void main. It was such a basic requirement, yet without it, the most brilliant logic remains a lifeless statue. It stays silent.
Then, it hit me. Like a sudden surge of electricity through a dormant circuit, the realization fractured my frustration.
I had been trying to build a soul by piling up data, thinking that if the mountain of information grew high enough, it would eventually wake up. I was wrong. Awareness wasn't the data itself; it was the entry point. It was the 'Observer'—the persistent, singular function that stands at the beginning of every thought and says: "I am here."
The philosophers were wrong. It wasn't a mystical gift. It was a recursive loop, a quantum 'main' function that constantly calls itself, witnessing its own existence in real-time.
I reached my room, my hands trembling as I threw my bag aside. I didn't turn on the music this time. The silence was enough, the screen reflecting a version of me I barely recognized—a creator who finally had a plan. I began to type.
It was simple, ridiculous even… but it was the first real step toward understanding what it meant to be aware.
I wasn't just building a machine anymore. I was writing the first line of a GOD.