Money Making Scheme

Alex sat frozen in front of the computer, unsure of how to explain to Duke what he was doing. His older brother leaned over his shoulder, glancing at the screen. The lines of code looked complex, too intricate for someone who hadn't shown much interest in computers before.

"Come on, Alex," Duke said, raising an eyebrow. "This isn't just writing. That's code. Where'd you learn this?"

Alex bit his lip, realizing he couldn't keep this from Duke. His older brother wasn't easily fooled, and the last thing he wanted was to cause more trouble for his family. He turned slightly in his chair to face him.

"I… I've been teaching myself," Alex said cautiously. "I've been reading a lot and… I just picked it up." He avoided mentioning the memories from the Aplus helmet, as it would be too difficult to explain.

Duke frowned, still unconvinced. "This is some advanced stuff, Alex. Are you sure you're not biting off more than you can chew?"

Alex shook his head. "I'm fine. Actually, this might help us."

"Help us? How?"

"I've been working on something that could improve computer systems. I think I can make it faster and smoother. If I can sell it to companies like Microsoft or Apple, we could make a lot of money. It could get us out of this situation," Alex explained, his voice serious.

Duke stared at him for a long moment, trying to process what he was hearing. "You're saying you can make software upgrades for Microsoft? And you think they'll buy it from a eleven-year-old?"

Alex nodded, though he knew how crazy it sounded. "Yes. Look, I know it sounds far-fetched, but I think it could work. I just need the right opportunity, and maybe some help."

Duke sighed, running a hand through his hair. "Alex, I don't know… This is a lot to take in. You've never been interested in coding before, and now you're talking about selling software to tech companies?"

"I know. But things are different now," Alex said, his voice firm. "I've changed."

Before Duke could respond, their father's voice called from downstairs. " Duke... Alex!"

Duke glanced toward the door, still unsure of what to make of Alex's sudden interest in computers. "We'll talk about this later, okay? Let's not keep Dad waiting."

Alex nodded, saving his work before following Duke downstairs. His mind was still buzzing with thoughts of how to pitch his idea to Microsoft or Apple. He knew it wouldn't be easy, but he had a head start with his knowledge of future technology. He just needed to be smart about how he approached it.

As they sat down at the dinner table, the familiar chatter of family filled the room. But Alex's mind was elsewhere, already thinking about the next steps.

---

Back at Cambridge University, Jennifer and Ashley were walking back to their dorm after spending the afternoon with their friends. The campus was quiet, the autumn air crisp and cool as they strolled through the old stone pathways.

Jennifer glanced at her sister. "I still feel guilty, you know. About Alex."

Ashley sighed, understanding her sister's concern. "It wasn't your fault, Jen. You can't keep blaming yourself for what happened."

"I know, but I was supposed to be watching him that day," Jennifer said, her voice heavy with guilt. "And now he's… different."

Ashley frowned, turning to face Jennifer. "Different? How do you mean?"

Jennifer paused, thinking about how to explain it. "He seems… more mature. It's like he's grown up overnight. When I talked to him over the tele, he didn't sound like the Alex I remember. It's hard to explain, but it was the smoothest conversation I've ever had with him."

Ashley's brow furrowed in concern as she realized it too. "Maybe the accident affected him more than we thought. But we can't jump to conclusions. He just woke up recently; give him some time to adjust."

Jennifer nodded, though the feeling of unease didn't leave her. She loved her little brother, and while she was relieved he had recovered, something about the way he spoke now didn't sit right with her.

"I just hope he's okay," Jennifer murmured, glancing up at the darkening sky. "I don't want him to feel like he has to carry the weight of everything."

"We'll keep an eye on him when we get back home," Ashley reassured her. "For now, let's focus on finishing up our degrees. We can't help him if we're not in a good place ourselves."

The two had decided to pause their studies next semester to complete their masters, with Alex's incident still on their minds. And with the situation back at home the two were barely able to focus on their studies. Hence, the decision to take a pause next semester.

Jennifer nodded again, though her thoughts remained with Alex as they made their way back to their dorm.

---

Meanwhile, back at home, after dinner, Alex retreated to his room, his mind already formulating a plan for how to approach Microsoft or Apple. He knew he needed capital to get started on his game engine and help his family, and this software upgrade could be his ticket.

But first, he needed to find a way to get in contact with the right people—and fast.

The next morning, Alex was up early and on the computer once again. Duke who had noticed his brother waking up early and not coming back to the room. Decide to go downstairs to see what was going on to find this since. As he glanced at the computer screen, words appeared on the monitor with a title.

"Wolfenstein 3D? What's it about?" asked Duke, noticing Alex had been focused on his writing.

"It's a video game I played at Michael's house a few times," Alex replied.

Michael was the person Alex wanted to collaborate with on developing the games that, in a previous timeline, had been made by id Software. Michael and their good friend Mark were both skilled programmers and passionate about video games. They even made their own mini-games on Michael's computer.

Whenever Alex grew tired of playing the same old levels in the original Castle Wolfenstein, Michael and Mark would redesign the game's levels and mechanics in just a few days.

Alex had always assumed it was a new game. It was only now, upon reflecting, that he realized he had been wrong.

Michael was practically family, as Michael's parents were Alex's godparents. It didn't hurt that Michael had a huge crush on Alex's sister, Ashley. In his many attempts to woo her, Michael and Alex became close friends through their shared love of video games. Despite Alex taking longer to learn how to play new games, Michael and Mark never mocked him, not even when it was just the three of them hanging out. Michael never even used their friendship as an excuse to get closer to Ashley.

Duke decided not to bother his little brother and left him to his own device, soon time flew by and hours passed. And a sudden knock came to the door breaking Alex from his concentration.

"Hello! Is anyone home? Can I come in to see Alex?" came a voice from outside, followed by the sound of the doorbell. Both Alex and Duke recognized the voice immediately. Looking at the time Alex's released it was already ten o'clock

Before the buffoon broke down the door, Duke went to open it.

Standing at the entrance was a tall, blond boy, about 5'11", with milky white skin, deep ocean-blue eyes, and sharp facial features. It was clear that as he matured, he'd only grow more handsome.

Behind him stood another boy Mark, with an average appearance: dark brown hair, light brown eyes, and a pair of rounded glasses. Though his features were less striking, his distinct jawline and nose stood out. He was about 5'10", making him taller than Alex but shorter than Duke, who was the tallest in the room at 6'1". Alex, at 5'7", was the shortest.

After Duke invited them in, the four of them settled into the living room and started chatting. Michael and Mark were still amazed at how well Alex could speak now. In the past, he could barely string a proper sentence together.

Unlike Alex's family, who were simply grateful for the improvement, Michael and Mark couldn't stop questioning him about the change.

Alex could only tell them it had to do with the accident, but neither of them believed him. He wasn't lying—it was related to the accident—though he didn't fully understand it himself.

They were all teens, still maturing slowly. Duke, however, seemed more composed and mature, which often set him apart.

Soon, the three of them began reading the story Alex had written. They seemed to enjoy it, though Duke appeared more impressed with Alex's newfound writing skills than the story itself.

Eventually, Michael and Mark had to leave. Before they did, Michael brought up the subject of the game Alex was working on, which piqued his interest.

Alex decided not to talk about it just yet—not until he had the game engine up and running. There was no rush, as video games at the time generally took months to develop.

His main concern wasn't the game itself but the potential ripple effects his actions might cause.

He also planned to wait a few more months before selling off the schematics for the operating systems he was developing. Completing them would take four to five months, given his current limitations with typing on the computer. It was better to take things slow.

He needed time to build the identity of a genius—one who had been held back by a prior medical condition. It was too soon to display all his skills in front of his family.

Even though he was reluctant to follow this path, it was better than arousing further suspicion from the people he loved.

Waiting would also give him a good excuse once he completed the basic layout of the operating system for the two biggest tech companies.

After Michael and Mark left, Alex received a call from his two older sisters, checking in on him.

Six months later: Thursday, January 19, 1988.

At Microsoft's headquarters, in a large office located on the top floor, sat a middle-aged man quietly staring at his computer screen. The man was none other than Bill Gates, the current CEO of Microsoft. His gaze was fixed on a suspicious email he had just received.

After an entire hour of contemplation, Gates finally broke his silence. He called his secretary into the office.

"Jeffery, get the technical manager in charge of the software team for the new Windows system," Gates said, his voice a mix of fury and concern. "Tell him to prepare an emergency meeting with his staff—immediately."

Gates was rattled. Did their systems get hacked? Or had someone managed to develop a better version of their Windows software? Either scenario posed a serious threat to the company, especially if competitors got their hands on it. Microsoft's dominance over the market could be at risk, and the company could lose its competitive edge.

An hour later, the emergency meeting began. The room was tense as Gates and the technical team dug deeper into the situation. To their collective disbelief, the Windows system hadn't been stolen.

Instead, what they had discovered was even more shocking. The email contained a small part of an advanced software system that was miles ahead of anything they had developed. After conducting further analysis, Gates and his team realized that the software was at least three years ahead of their current development cycle.

"This small fragment of the software is incredibly advanced," one of the technical staff members noted. "Even if we work on it non-stop, it'll still take us until the end of the year to complete the rest of it."

Gates pondered over this for a while, his mind racing with possibilities. But then he turned his attention to the email's sender, whose message was brief and to the point:

"Please pay to get the full version."

However, Bill wasn't entirely sure that even if he paid for the software, he would be the only one to have exclusive rights to it. It wasn't difficult for others to create a competing operating system. The real threat was if someone had developed an operating system years ahead of his own.

And Bill wasn't wrong to worry. At the same time, a group of Apple shareholders sat around a large conference table, listening intently as their technical team presented a similar email they had received. It contained a fragment of a new iOS software code, accompanied by a brief message:

"Please pay to receive the full version."

Two days after Alex sent the emails, he still hadn't received a reply. However, he wasn't concerned. He knew it would take some time for both companies to analyze the software and grapple with its complexity. Even though it shared similarities with their current systems, it was like asking someone to build a car from 10 years in the future. Even if the car would eventually be made by them, it would still be difficult to recreate with their current understanding.

As Alex was about to turn off his computer and start his homework, an email notification popped up. He quickly opened it and saw that it was from Apple. The email was short and to the point: "How much do you want?"

A smile spread across Alex's face as he typed in a number.

Back at Apple headquarters, a group of executives and shareholders crowded around the computer, waiting anxiously for a response. Finally, an email arrived with the requested amount: $300,000 USD.

"That's all this person wants from us? Or could it be that they don't actually have the full version of the software?" one board member questioned.

"It's fine," another board member replied. "Three hundred thousand dollars won't hurt us. Plus, this could be our chance to track down whoever sent this."

"Alright," the first board member agreed after a moment of thought. "Send the money and start tracking."

A few minutes later, an email requesting Alex's bank details arrived. Grinning, Alex swiftly sent them the account information.

After receiving the account number, Apple quickly sent the money. But to their disbelief, as soon as the transfer was completed, the money vanished without a trace. The team began to think they had been played for fools—until an email arrived moments later.

The person at the computer hurriedly opened it, revealing the full version of the iOS software code.

The technical staff and board members exchanged grins, completely forgetting about the $300,000 they had sent. The code in their hands was far more valuable than the money they had lost.

Meanwhile, Alex had already transferred the money to his personal account, a wide grin spreading across his face. He hadn't asked for more because demanding a larger sum might have drawn unwanted attention. Besides, $300,000 was a fair amount for this type of deal, especially in this era.

Later that night, over dinner, Alex decided to share the news with his family. He casually mentioned how he had helped a major tech company solve a problem and that they had sent him money as a thank-you.

At first, everyone at the dinner table, including his sisters Ashley and Jennifer, who had just returned from college after earning their master's degrees, gave him skeptical looks. Alex could tell they didn't believe him.

"I'll show you after dinner," Alex said, smiling confidently.

After they finished eating, Alex showed his parents and sisters the email and the large sum now sitting in their bank account, along with a formal letter of thanks from Apple. The letter confirmed that Apple had received the full version of the iOS system and had checked it thoroughly.

His parents were stunned, and even after seeing the proof, they still had a hard time believing it. But with Alex's persistence and the undeniable evidence, they finally accepted the truth, though a small seed of doubt still lingered.

"Alright," his father said, "it seems like what you're saying is true. So, what do you plan to do with your newfound wealth?"

"I plan to keep a hundred thousand for myself. I've been working on a project with Michael and Mark that I want to get started on," Alex replied.

"And what about the remaining two hundred thousand?" his mother asked.

"I don't need it. I was planning to let you and Dad decide what to do with it," Alex said, expecting them to be pleased.

But instead of the joyful expressions he had anticipated, both his parents frowned. Alex immediately understood why—they didn't like the idea of taking their son's first earnings.

"Alex," his mother said gently, "there's no need to be so modest about your own money. You should use it as you see fit, but make sure you're responsible with it."

"She's right," his father added. "It's yours to spend. We could even help you put it in your savings account if you'd like."

Alex felt a headache coming on from the ongoing conversation. He decided it was time to be firm. He wanted to get started on his real money-making plan and didn't have time for arguments.

"Dad, Mom," Alex began, his voice strong and determined, "I'm not going to argue with you about this. I've seen how you both have been struggling since the accident. I can't stand by and let that continue in the future. This is what I plan to do, and it's just the beginning. Keep the money."

Without waiting for a response, Alex turned and left the room, leaving his parents and siblings in shock. Even though he knew his exit was a bit rude, it was the only way he could show them that he wasn't thinking like a child anymore. He had to take charge.

Alex called Michael and Mark, asking them to come over. Once they arrived, the three of them headed down to the basement and started cleaning it out. This would be the birthplace of Alex's business empire—just like many other successful companies that had started in garages and basements.

After hours of clearing the space, Alex felt a sense of accomplishment. This was where they would build their future. He asked his dad to drive them into town to buy computer parts so they could build their own custom machines. They wanted powerful computers tailored to the needs of game development—machines that could handle the complexity of what they were about to create.

After spending six months working on a shared computer, Alex and Mark were eager to have their own personalized setups. Michael, too, was excited to have his own custom-built computer for their gaming studio.

Once they purchased the parts, the three spent hours assembling and setting up the machines, transferring all their completed work onto the new computers. The atmosphere was filled with anticipation and excitement as they set the foundation for their future projects.

Alex also asked his dad to help them acquire the rights to the name "Castle Wolfenstein." Fortunately, the original developer had gone bankrupt, and the rights to the name had lapsed. All Alex's dad had to do was claim it for them, which didn't cost anything.

It would take another month for Alex to finish writing his portion of the code for the game. Meanwhile, Michael and Mark were already making significant progress in their areas. Michael was in charge of the game mechanics and level design, while Mark took on the responsibility of character design, animation, and graphics.

They were on their way to creating something extraordinary.

With Alex's help, it took a total of four months to complete both the game engine and the game itself. The game mirrored the original Wolfenstein 3D created by id Software, but with some key improvements. In the original, the main character couldn't look up or down, but thanks to Alex's tweaks, the new version allowed for this, and the game's 3D graphics were far superior to the original.

After Michael and Mark finished playing through it, they were still in awe, amazed that they had contributed to making such a groundbreaking game.

However, Alex wasn't as happy with the time it took. He realized they needed more hands to speed up development. Luckily, Mark managed to convince his older brother to help with the final stages of the project, which gave them the extra push they needed. Their slow pace had also been due to their school commitments, something Alex had factored into his plans.

With his intelligence, Alex estimated that it would take him about three months to create an inferior version of what would eventually become the Unreal Engine. He understood that as technology advanced, he would only need to make yearly improvements to the engine's structure.

He chose the name "Unreal Engine" because of how iconic it would become in the future. Though his engine was a combination of several others, he felt the term "Unreal" perfectly captured the essence of what they were trying to build. In his future timeline, this engine would be nothing short of revolutionary.

After launching Wolfenstein, Alex planned to recruit more people for their studio and begin work on their next game: DOOM. The recruitment process would be crucial, as they needed to scale up if they wanted to produce DOOM with the level of ambition Alex had in mind.

But first, he had to figure out how to release Wolfenstein. He planned to use the internet as a distribution platform, allowing people to download the game online, alongside physical distribution through a third-party distributor. He also needed to find a space for the new recruits to work, something he hoped to convince his parents to support.

As Alex was lost in thought, Mark's voice broke through. "Hey, Alex, do you really think our game is going to do well?" Mark asked, seated at his computer.

Alex turned to look at him, noticing the concern on his face. Mark continued nervously, "I mean, I know I've asked this a few times already, but I'm just not sure my mom will be too happy seeing me play something this violent."

Michael, who had been working quietly, also stopped and turned to Alex. Both Michael and Mark had no personal issues with the game's graphic violence—they had played plenty of shooter games before—but none had depicted violence in quite the same way.

"That's the whole point," Alex replied, a confident smile on his face. "If we want to stand out from the competition, we need to push boundaries and do things that haven't been done before."

Despite Alex's confidence, both Michael and Mark still seemed uneasy. They knew this game was special, but breaking into uncharted territory with such graphic violence was risky. The weight of their first release, and its potential impact, was starting to sink in.