Marvel's Kryptonian Slacker
Chapter 343

Stark Studios' Work

1,297 words4 min read0 views1mo agoSource
Next

Despite Henry's indifference, the Skrulls did not abandon their attention to the Kryptonian.

One of them asked, "So how do we deal with this Krypton cockroach? This isn't a star system with a green star. And right now, we don't have the means to terraform a star."

"Hmm, does anyone remember the characteristics of Kryptonian? I only remember that they become very weak under red stars and become so weak as to die under green stars."

Who would remember the defeated foe from nine thousand years ago? I only remember their exploits under red and green stars. Red stars are the Krypton types of Krypton, while the Barrington Galaxy, with its green stars, was the battlefield where the Skrull Empire annihilated the Krypton fleet.

What would happen to Kryptonian under a yellow star?

All the Skrulls looked up directly at the sunlight. Unfortunately, human pupils and optic nerves cannot withstand the brightness of sunlight; their eyes could not take the stimulation, and they all teared up and were plunged into a brief period of blindness.

Okay, they're soldiers, which means they're all academic underachievers. Who remembers the detailed history of the Skrull Empire? Their teachers should be proud if they even know anything about Kryptonian.

It seems the only option is to contact General Ross and ask him what his plans are. Hopefully, this Krypton cockroach won't hinder our operations.

These Skrulls came from the same warship. Unfortunately, their warship was destroyed by prisoners of the Starforce, so the Skrulls had to use escape pods to make an emergency landing on the planet codenamed C-53.

General Ross was the leader of this Skrulls. So when they were in a dilemma, they naturally thought of their leader.

However, after landing on Earth, most of them lost contact with each other.

According to their code of conduct, they all immediately transformed into the appearance of the planet's natives to avoid being detected by the native government. Especially since the two sides' ordinary forms are very different, disguise has always been the Skrulls ' primary action.

Now, they need to find a way to reconnect with each other.

However, the suggestion from the leadership was not accepted by everyone.

As the most ambitious Skrulls, Evrin said: There must be a reason why Krypton is rejected by the entire universe, and even its home planet is sealed off by the Phantom Zone, preventing people from getting out and people from getting in.

General Ross has his own goals to achieve, shouldn't we share his burden and take care of this Kryptonian? We don't know how this Kryptonian broke through the blockade to reach planet C-53, nor do we know his purpose.

What If...? he's colluding with the Kree? What if he's hindering General Ross's operations? Even if we can't eliminate him, we should at least prevent him from causing us trouble."

The Skrulls present exchanged glances, and one of them asked, "Evrin, what do you plan to do? Try to assassinate him?"

No, let's do what we do best: infiltrate the planet's native government and get them to help us deal with that Kryptonian. We just need to find a way to sow discord between the two sides. The key to this operation is still to remain covert.

All the Skrulls nodded in agreement with Evrin's suggestion. Espionage and infiltration were skills almost every adult Skrulls possessed. They were also adept at sowing discord.

Although it was their first time on this backward planet, they quickly figured out the best way to frame someone in this indigenous society by stealing their appearance and short-term memory.

Everyone has found a suitable role and entry point for themselves. What If...? their current identity doesn't work, they simply steal another one—this is commonplace for the Skrulls. Everyone is adept at carrying out this process.

The man being targeted couldn't possibly know he was being schemed against before even meeting the other party. Henry went to work as usual.

The first task, of course, was to keep an eye on the maintenance and upgrade progress of a series of video post-production software programs. Then came the research progress on the UHD codec.

Because many of the software programs were developed collaboratively, Henry introduced Git, a distributed version control software developed and version controlled collaboratively on a server within the local area network.

This way, he doesn't need to visit each department personally. Instead, he can check the update progress on Git to get a general idea of the software's status. There's a Gantt chart showing everyone's ideal progress, and if someone isn't meeting the target, he can simply check on them.

Although CVS, a system already available for collaboration and part of the GNU General Public License, has its limitations and shortcomings, Henry opted for the more user-friendly Git instead.

Because it was a network function built on the back of the supercomputer "Hollywood Kid" and its servers, this Git software naturally caught the eye of Tony Stark and was used internally by Stark Industries.

Henry's conditions were simple: install GNU, and he would provide the personnel for subsequent maintenance, then it would be fine to use.

Tony Stark, of course, wouldn't object; after all, only the public version would be released. Upgrades used internally were a private matter, including encryption and enhanced cybersecurity measures.

This is true for many GNU licensed software programs; anyone with the ability to modify them will make changes according to their own needs. As long as they are not used for commercial sale, they are within the scope of the license.

Whether the revised version will be made public depends on the situation. Stark Industries ' use of the technology involves its company secrets and programs under development, so they certainly wouldn't be foolish enough to expose it and give malicious individuals a weakness to attack.

Besides these official matters, Henry inevitably used the supercomputer's resources to do some personal work, mainly developing his own EDA and simulation software.

Once chip manufacturing reaches the nanometer level, Henry will have a high chance of making mistakes if he relies solely on the old methods—that is, using Super Brain to think and coordinate all his senses to manually shape chips with tools.

With such a small manufacturing process, a single mistake can render the entire chip unusable, requiring everything to start from scratch.

To reduce the likelihood of such situations, we design and simulate the operation beforehand to see what might happen. This would result in less frustration than trying to figure it out by hand and then failing.

On the other hand, Henry also began to experiment with topological core architectures, moving towards the field of Quantum Computer. This would also avoid the approach of simply improving traditional manufacturing processes, just to speed up the computer's instruction cycle.

Without the supercomputers generously sponsored by Tony Stark, relying solely on their own makeshift home computers, it's hard to say how long it would have taken to develop them.

For Henry, who possesses advanced privileges and can secretly obtain administrator privileges when necessary, doing his own thing without being discovered is incredibly easy.

Only when Tony came to the West Coast did Henry restrain himself a little when using the supercomputer.

As for whether the young master had discovered his secret, Henry didn't care much. It was like Henry would try to hack into Tony Stark's virtual machine to see what kind of advanced technology was inside.

Another, less important task was for the production department to put shortlisted projects or scripts on Henry's desk for selection, along with the production department's evaluation results, distribution methods, and expected profits.

End of Chapter
Prev
NovelSummaries
Next

Explore the wiki

Comments