Chapter 17: The Judges Are Convinced
After submitting his results, Su Xin looked left and right; seeing some people pointing at him with disdainful expressions, he didn't pay much mind to it.
Since he wanted to generate buzz to accelerate the promotion of the software, he had to endure the strange looks of the crowd before they knew his true strength.
Su Xin had long been prepared for this.
Not far from one side of the podium was the judges' table.
Seeing that Su Xin had submitted his results so early, the five judges could not help but look at each other.
Although they did not believe Su Xin could have truly found and optimized so many bugs in such a short time, out of professional ethics, the five of them opened Su Xin's document to take a look.
The first thing that caught their eyes was the number written in the box at the very top of the document—18.
One of the judges couldn't help but sneer:
"18 bugs? It seems this kid really is just a show-off. So many of us only found 15 bugs; he can find three more than us?"
The other judges also shook their heads.
Then they continued to read on.
The description of the first bug and the corresponding solution appeared before them, which made them immediately straighten up.
"The bug description is fine, and the solution is also excellent."
"Could this kid actually have some real talent?"
Then they continued to look down.
The second bug, the third bug...
By the time they reached the ninth bug, all five judges had to admit in their hearts that Su Xin was definitely not just someone with a little talent, but could be called a true master in the software programming industry.
Finding and solving so many bugs was one thing; they could do that too.
However, among the five of them, and everyone they knew, it was impossible for anyone to achieve the exaggerated efficiency that Su Xin had.
What's more, Su Xin's solutions for some of the bugs made their eyes light up, and they were genuinely impressed.
They continued to look further down.
"Huh? This tenth bug, is it for real? When the algorithm setting is Lanczos, opening a video with a resolution above 2K causes the software to crash directly?"
The five judges couldn't help but look at each other, then immediately opened the original version of the software to test it, configuring it according to the instructions in Su Xin's bug document, and then opened a 2K video.
Sure enough, when the video opened, the entire screen froze, and the mouse cursor turned into a spinning circle; it was clearly lagging.
A few seconds later, the program crashed and closed.
"Sure enough, this bug really exists, yet none of us had discovered it before."
"It seems that the three extra bugs Su Xin found compared to us are all real."
"What a shame! The five of us spent most of the day, and the bugs we found don't even add up to as many as a teenager."
At this moment, the five judges were completely convinced of Su Xin's strength; even without seeing the rest, they could basically confirm that the remaining bugs were accurate.
Sure enough, as they continued to read down and verify them one by one, they found that the content in the document was accurate and error-free.
Next.
The five of them looked at the optimized new software code together, focusing on the places where the bugs existed to see how Su Xin had perfected them.
They were no longer just holding the mindset of auditing; they wanted more to understand Su Xin's code optimization ability.
After all, no matter how many bugs were found, how accurate they were, or how ingenious the proposed solutions were, it only represented a good eye and rich theoretical knowledge.
To modify and perfect the software required extremely strong practical ability; otherwise, the other party would just be a Zhao Kuo talking on paper.
Soon, one of them exclaimed.
"Holy crap! Awesome!"
"Is this guy really a high school student?!"
Although this judge couldn't help but swear, the other four had no intention of reminding him; they were completely immersed in the world of code, like architects seeing a building that could stun the world.
They had been won over by Su Xin.
They no longer placed themselves in the position of judges, but instead subconsciously adopted the posture of juniors, admiring the brand-new code architecture Su Xin had built.
That's right, it was a brand-new code architecture.
Although the main body of the software and every function remained unchanged, the internal operating logic had been greatly optimized, just like a square rural mud house that, after being decorated and renovated by a top designer, had turned into a luxurious small villa.
It was almost equivalent to tearing it down and rebuilding it.
The profound skill contained within left the five of them shocked to the point of scalp numbness, wishing they could cast aside their identity as judges right now to ask Su Xin for advice.
However, considering the occasion, they suppressed this impulse and continued to check the code.
In the final step, they opened the new software Su Xin submitted, tried running it, and verified one by one whether all eighteen bugs had been optimized.
The result was perfect.
At this time, one of the judges suddenly and curiously opened the software properties bar and couldn't help but whisper in surprise:
"Hiss! The memory is actually down to only 36MB. I remember it was a full 51MB before; he actually optimized away about thirty percent!"
You have to know, this represents more than just a difference of a dozen megabytes of memory; the most critical thing is that the more complex the code, the easier it is for problems to occur during operation, and the greater the operational loss.
It's like a car; the more complex the parts, the higher the failure rate, the greater the energy loss during operation, and the greater the risk of accidents.
Just imagine, if you could reduce the car's parts by thirty percent while guaranteeing all its functions, what kind of concept would that be?
This kind of optimization ability would absolutely shock the world!
The same is true in the world of code.
Under the premise of not affecting the program's functions and fluency, optimizing the memory size by thirty percent, and doing it in such a short time—this ability left the five of them terrified.
From the initial bug registration document to the source code just now, and then to the current trial run of the software, after this series of audits, they were completely won over by Su Xin's strength.
At this time.
More than thirty media outlets were filming the scene, and several of them had started live web broadcasts.
When they saw Su Xin submit his results first, some people who were unaware of the situation initially cheered and applauded, but after hearing the reporter's commentary and the explanations in the comment section, the netizens realized that the average time for previous competitions was around fifty minutes.
Yet Su Xin had only used ten minutes.
This speed was too outrageous; anyone who understood a bit of the inside story would not believe that Su Xin was participating in the competition seriously, but rather that he seemed to be deliberately using outlandish behavior to grab attention.
This kind of attitude was a sign of disrespect toward the competition.
On the barrage, there was a chorus of mockery and scolding.
At this moment, several netizens who happened to have watched Su Xin's interview on the Wanyue Entertainment livestream hurriedly spoke of the various arrogant remarks Su Xin had made before the competition.
After all, Wanyue Entertainment was only a relatively small online media outlet, and the attention on pre-competition interviews was not high to begin with, so those remarks by Su Xin had not spread previously.
But at this time, during the official competition stage, the number of netizens watching the livestream reached over a million, and even when spread across various streaming platforms, the popularity of each livestream room was much higher than that of Wanyue Entertainment before.
Very quickly, more than half of the netizens watching the livestream knew about Su Xin's arrogant remarks.
End of Chapter
