For advance/early chapters : p atreon.com/AutumnXd
"To be honest, my father and I share the same dream: to create a truly independent brand. To develop technology with our own patents, free from licensing dependencies. To prove that a smaller player can compete with the giants in the VR device space.
For this dream, my father has dedicated himself tirelessly over the years. And so have I.
But I hope that the dream my father hasn't yet realized can be achieved by me—and in the shortest possible time."
Alex's expression grew serious.
"Ever since I entered the game development industry, I've been diving deep into computer languages and programming. I'm genuinely interested. Over the past two years, I've self-studied extensively—researched technical documents from across the industry, even practiced writing programs myself.
I've made some progress. And I have some ideas that might seem impractical, which I hope to put into practice and verify here.
I also hope I can fulfill my promise to my father: to make Polaris Technologies profitable within the next year. To make the Polaris brand a global powerhouse like Nexus within three years. And to make Polaris the world's largest VR device supplier within five years."
Alex's words left the room silent.
Expressions grew complex. Hearts tightened once again.
On one hand, they were pleased that Alex intended to make serious strides in the VR device field. On the other hand, the ambitious vision he'd just painted seemed... naive. Even reckless.
Clearly, Alex was an idealist.
Developing programs and developing games weren't the same thing. Miracles couldn't be conjured through sheer enthusiasm.
Profitable within a year? A global brand within three? The technological gap between independent players and the Nexus monopoly couldn't be bridged in just a few years—especially since Nexus was also advancing. The brand influence they'd cultivated globally, their integrated product ecosystem, made it nearly impossible for any latecomer to shake their position quickly.
Of course, everyone present could tolerate Alex's impracticality. Outsiders didn't truly understand how difficult this was. That ignorance made it easy to utter passionate but ultimately naive words.
"Mr. Morrison speaks very well!"
Timothy Crawford was the first to break the silence, clapping his hands. "We need grand goals to motivate ourselves—to continuously break through and move forward!"
Only then did the others react, forcing smiles and joining in the applause.
Alex smiled but said nothing more.
He could read the room. They probably felt, like his father, that he was young. That his ideas were naive and impractical.
But he didn't care.
This was a normal reaction. What he'd said was genuinely astonishing. If he didn't have the advanced technical knowledge from the system in his mind, he'd probably find his own words ridiculous too.
After the all-hands meeting, Alex gathered the company's senior executives for a smaller session to understand current business operations and R&D progress.
During this meeting, Alex listened the entire time without expressing any opinions.
From everyone's reports, he developed a solid grasp of Polaris Technologies' current situation.
After the meeting, Alex returned home and began mapping out future plans—how to gradually implement his ideas without raising suspicion.
First principle: he couldn't unleash all the technology in his mind at once. That would be too shocking.
He needed to start with software. Develop the advanced VR system architecture from his memory.
However, writing a complete operating system required enormous amounts of work—far more than he could complete alone. He'd need support from the entire programming department.
As for hardware technology, over the next six months he could progressively file patents for several core innovations. Then the R&D department, guided by his direction and core technologies, could design corresponding chips and integrate them into Polaris's new products.
Two days later, Alex asked Timothy Crawford to give him a detailed overview of the R&D department's research achievements and current development projects.
Timothy was initially worried Alex wouldn't understand, so he tried to simplify highly technical details.
But Alex's counter-questions completely stumped him.
It was clear Alex had come prepared. Just as he'd claimed, he really had studied computer languages and technical documentation over the past two years. He'd acquired genuine professional knowledge.
But Timothy Crawford was a true expert in this field. Stanford graduate. PhD. One of the top software engineers in the industry.
How could he let some amateur newcomer look down on him?
So Timothy proceeded without regard for whether Alex could follow. He focused on difficult concepts, deliberately used extremely technical terminology, hoping to make Alex realize he shouldn't show off in front of an expert.
He expected his words to completely overwhelm Alex. Leave him speechless.
To his shock, Alex understood everything.
Not only that—Alex engaged seriously, discussing the technical details at a peer level.
And then Alex proposed several solutions that Timothy hadn't even considered.
Subsequently, Alex sat down at a computer and wrote a simple program, replacing one of their current architectural modules.
When the program ran, Timothy and the other programmers' eyes nearly popped out of their heads.
An outsider might not see the difference between Alex's code and theirs. But for insiders? It was immediately clear how incredible Alex's program was.
"So it can be done this way..."
The programmers were enlightened. Some who hadn't quite grasped it quietly asked their seniors for explanations.
Timothy, expression oscillating between excitement and shock, carefully studied the code Alex had written. He marveled at the elegance. Wondered why he hadn't thought of it himself.
Alex's performance completely stunned him.
He couldn't believe that Alex had truly only studied for two years and already possessed the skill level of a top-tier software engineer.
If that were true, his entire worldview would collapse.
Timothy considered himself a genius. He'd been a star student his whole life—full scholarship to Stanford, consistently at the top of every class, recommendations from industry legends.
Yet despite all that, the professional knowledge he possessed had taken over a decade to learn and accumulate. His current technical skills were built through years of grinding work experience.
And this guy just... casually studied for two years? Researched some documents? And now he understood this much? Could write programs that Timothy himself had to admire?
This was simply unfair.
However, in the following days, Timothy Crawford's mentality completely imploded.
After fully understanding their current development situation, Alex directly rejected all of their design ideas and directions.
He announced that he would personally handle the architecture.
...