Skip to main content
  • Home
  • Library
  • Read
    • Popular
    • Charts
    • Browse
    • Categories
    • Wikis
    • Glossary
  • Request
  • Activity
  • Leaderboard
  • Help
Our Apps
  • DaoSearch
  • Narratorr
Social
  • Discord
  • Patreon

Chapter summaries

The AI Wave Tycoon's Rise
VolumesArcsSummaries

Ch. 1You've Been Optimized

After being laid off, Han Luyi gained the ability to see reality’s code, including people’s tasks and emotions, and used it to uncover errors in his severance calculation. He left Prosperity Group with an extra 47,832 yuan and questions about his dwindling Energy and his former supervisor’s three critical Bugs.

  • Han Luyi signed a layoff agreement, then experienced a painful vision that activated his reality code vision and showed his Energy dropping.
  • Han Luyi saw Zhang Wei’s task and emotions, identified errors in his years of service and overtime calculations, and persuaded her to raise his severance by 47,832 yuan.
  • Han Luyi saw that Chen Bowen felt contempt and hidden fear, while his three critical Bugs were beyond Han Luyi’s current level.
  • Han Luyi warned Chen Bowen that the recommendation system’s conversion rate was falling, returned his employee badge, and left the company.
  • Outside the building, Han Luyi wondered what would happen when his Energy reached zero and what Chen Bowen’s Bugs were.
Read chapter

Ch. 2This World Has a Bug

Han Luyi tested Sight at home and discovered it could reveal real-world business losses caused by software bugs, including a major anomaly at Flash Tech. After helping his neighbor Lin Wanqing carry groceries, he saw that she had a family dispute marked as a bug he could investigate once he reached Lv. 2.

  • Han Luyi measured Sight's energy use and learned it could inspect code but not financial data on his phone.
  • He scanned his open-source recommendation system and saw that one bug caused an estimated 62,000 yuan in daily losses.
  • Han Luyi spotted a warning that Flash Tech had severely abnormal core operational data and noted that a deep scan could grant substantial experience.
  • On the stairs, Han Luyi helped Lin Wanqing carry her groceries and learned she lived in apartment 501 with her daughter, Duoduo.
  • Sight showed Han Luyi that Lin Wanqing had an unresolved family dispute, with its details locked until Lv. 2.
Read chapter

Ch. 3The 415% lie

Han Luyi used Sight to uncover Flash Tech’s inflated user numbers, mass-produced fake accounts, and theft and overseas transfer of private data. After collecting evidence and noticing Flash’s CTO Zhou Mingzhe’s connection to Dingsheng, he decided to involve his Dorm 404 friends and invited them to dinner.

  • Han Luyi used Sight to select reliable freelance jobs and earned 8,200 yuan by completing three coding tasks in one morning.
  • Han Luyi scanned Flash Tech and discovered its reported user figures were drastically inflated and that the company was stealing users’ private data to create fake active accounts and deceive investors.
  • Han Luyi recorded the findings and gathered evidence through APK reverse engineering, packet capture, and analysis of account behavior.
  • Han Luyi recognized Flash CTO Zhou Mingzhe as someone who had attended Dingsheng’s annual party with Wang Zhiyuan and Chen Bowen.
  • Han Luyi weighed whether to expose Flash despite the risks, then messaged the Dorm 404 group to invite his friends to dinner and discuss something serious.
Read chapter

Ch. 4Don Quixote's Charge

After losing his job, Han Luyi met his friends and learned that Ma Xiaofei had suffered losses from Flash’s allegedly misleading advertising data. Han Luyi arranged a legal consultation as he considered how to handle technical evidence against the company.

  • Han Luyi met Ma Xiaofei and Zhang Haoran at One More Skewer, where they discussed Han Luyi’s dismissal from Dingsheng and Ma Xiaofei’s unpaid advertising work for Flash.
  • Ma Xiaofei said his research suggested Flash’s public metrics were inflated, while Zhang Haoran described suspicious investment structures and Flash CTO Zhou Mingzhe’s ties to Dingsheng.
  • Han Luyi asked how someone could safely report hard evidence of data falsification or privacy violations, and Zhang Haoran recommended contacting lawyer Gu Siyue.
  • Han Luyi saved Gu Siyue’s business card and scheduled an appointment with Haicheng Boheng Law Firm for the next morning.
Read chapter

Ch. 5One in Twenty-Three Million

Han Luyi consulted Gu Siyue about reporting Flash for secretly collecting users’ private data and inflating its user numbers. After Gu warned him about the risks of challenging a powerful company, Han explained why he felt personally affected, leaving Gu to consider his resolve.

  • Han Luyi met Gu Siyue at Boheng Law Firm and described technical evidence of Flash’s privacy violations and fake user statistics.
  • Gu Siyue questioned Han’s evidence and warned that Flash’s legal team could make a real-name report dangerous for him.
  • Gu asked why Han wanted to report Flash despite having no obvious business or employment connection to it.
  • Han said Flash had stolen his own private data and that inflated figures had cost his self-media friend money.
  • Han connected his decision to being laid off and said he would act for the millions of users who could not see what Flash had done.
  • Gu noted that Han was the only one among twenty-three million people to seek a lawyer, and Han said one person was enough.
Read chapter

Ch. 6Seventy-Two Hours

Gu Siyue helped Han Luyi prepare a protected legal and media strategy to expose Flash’s illegal transfer of user data before its Series B investor meeting. After Flash began shutting down data channels, the report and supporting evidence were accelerated, and Han Luyi waited for 36 Degrees to publish.

  • Gu Siyue warned Han Luyi that Flash’s overseas transfer of twenty-three million users’ data could bring criminal charges, then offered to file reports and route contacts through her while setting a seventy-two-hour deadline.
  • On Day 1, Han Luyi prepared and notarized an anonymized report, asked Ma Xiaofei to contact an editor at 36 Degrees, and asked Zhang Haoran to analyze Flash’s financing using public information.
  • Old Zhao told Ma Xiaofei that 36 Degrees was cross-checking the report and that Flash was preparing a public-relations response; Han Luyi then used Sight to discover Flash had begun disabling and obfuscating privacy-data channels.
  • Gu Siyue moved publication up twelve hours, while Zhang Haoran completed an analysis showing Flash’s Series B valuation depended on inflated data.
  • On Day 3, Han Luyi submitted screenshots of Flash’s emergency update as supplemental evidence, and Old Zhao told Ma Xiaofei that the editorial review had passed.
  • After the Dorm 404 Group received the message “Eight tonight,” Han Luyi confirmed he was ready and set his alarm for the planned publication time.
Read chapter

Ch. 7Ignition

Han Luyi watched his investigation into Flash Tech trigger a public and financial crisis, then gained a major Sight upgrade after the system credited him for helping expose and remediate the vulnerability. As he kept his involvement secret, Su Niannian contacted him about leaving Dingsheng, and he waited to see what she would say next.

  • Han Luyi watched the report on Flash Tech spread across social media, prompting Flash Tech and Starlight Capital to issue statements and suspend investor plans.
  • Gu Siyue assured Han Luyi that the report could not be traced back to him and praised his work.
  • Sight credited Han Luyi with helping expose a vulnerability affecting 23 million users, awarded him experience, and upgraded him to Lv.2.
  • Han Luyi discovered that Lv.2 Sight could scan a much wider area and provide detailed repair paths for code bugs.
  • Han Luyi decided not to message Ma Xiaofei or Zhang Haoran, then received a message from Su Niannian asking whether he had left Dingsheng.
  • Han Luyi confirmed that he had left, and Su Niannian began typing a reply.
Read chapter

Ch. 8Long Time No See

Han Luyi met his former college classmate Su Niannian at Bug Café after two years without contact, and they caught up over coffee. After Su described setbacks on her AI code review project, Han asked who its core target users were.

  • Han Luyi agreed to meet Su Niannian at Bug Café after she contacted him on WeChat.
  • Han arrived early, spoke with café owner Old Zhou, and waited by the window.
  • Su arrived, and she and Han joked about their college memories and discussed their work.
  • Su told Han that a director had replaced her as lead on an AI code review project and that users found its results unimpressive.
  • Han asked Su who the AI code review tool's core target users were.
Read chapter

Ch. 9What Code Could Not See

Han Luyi and Su Niannian discussed the gaps in AI code review, and Han began shaping an idea for a tool that connected code with real-world behavior. After Flash Tech CEO Ding Ren publicly threatened the anonymous whistleblower, Gu Siyue warned Han to stay silent about Flash, leaving him focused on both his new project and the danger surrounding the investigation.

  • Su Niannian explained that small development teams needed help catching bugs before launch, and Han Luyi identified real-world business mismatches as a weakness of existing AI code review tools.
  • Han Luyi imagined a code review product that connected code to real-world scenarios and wrote down “BugKiller” and “Step one: find a product manager,” thinking of Su Niannian.
  • Su Niannian left to attend a meeting after asking Han to keep in touch, and Han returned to Bug Café to refine his product idea.
  • Han Luyi read Ding Ren’s statement accusing the anonymous informant of defamation and saw that online commenters had begun guessing the informant’s identity.
  • Han forwarded Ding Ren’s statement to Gu Siyue, who warned him to be careful and told him not to discuss Flash anywhere.
  • Han left the café with notes titled “BugKiller” and “Don’t Mention Flash.”
Read chapter

Ch. 10Making Money Like Breathing

After reaching Lv.2, Han Luyi used Sight to complete freelance software fixes quickly and earned 65,000 in a week, while rediscovering the free time he had lost at Dingsheng. He realized paid work gave him no experience, and began considering how to help people for free so he could level up.

  • Han Luyi used Sight to fix three clients’ software problems in under two hours, earning 26,000 and receiving surprised praise.
  • Han Luyi enjoyed an unhurried afternoon for the first time in years, bought groceries, and cooked lunch.
  • Lin Duoduo brought Han Luyi her frozen tablet, and he repaired it in less than two minutes while Lin Wanqing watched.
  • Han Luyi spent the week taking freelance jobs in the mornings and running, reading, and enjoying time at home in the afternoons.
  • Han Luyi earned 65,000 for the week but saw that his experience remained at 15, while fixing Lin Duoduo’s tablet had earned him three points.
  • Han Luyi concluded that paid work did not count toward experience and opened his computer to try an idea for helping people without charging them.
Read chapter

Ch. 11Alias

Han Luyi built a reputation as forum user NullPointer by solving difficult technical problems, while the Flash Tech investigation continued and the search for its whistleblower drew closer to him. He found a job request from Dingsheng Digital Technology about the recommendation system he had built, saw how Chen Bowen’s changes had ruined it, and ended the chapter furious over what had happened.

  • Han Luyi used Sight and Bug Detection to solve difficult forum problems as NullPointer, earning likes and raising his experience from 15 to 25.
  • The Flash Tech case escalated as authorities intervened, Ding Ren was barred from leaving the country, Zhou Mingzhe disappeared, and the company’s app and funding collapsed.
  • Han Luyi saw that the Reverse Engineering Old Wang profile thread had narrowed its search to someone with recommendation-system expertise, bringing it closer to identifying him.
  • Dingsheng Digital Technology posted an urgent outsourcing request about severe performance problems in its recommendation system, accompanied by a technical summary written by Xiao Ming.
  • Han Luyi recognized that Chen Bowen’s team had replaced the dynamic scheduling module he had built with a static rule engine, and he grew furious after confirming the system was in extremely poor condition.
Read chapter

Ch. 12Dingsheng's Outsourcing

Han Luyi rejected an outsourcing request to repair Dingsheng’s failing recommendation engine, which his former team had damaged after replacing his system. He began developing BugKiller, an AI code-review tool, and arranged to discuss the idea with Su Niannian.

  • Han Luyi used Sight to inspect Dingsheng’s recommendation engine and saw 140 Bugs, including three critical problems that could cause the system to collapse within 72 hours of launch.
  • Han Luyi ignored the outsourcing request and posted a technical warning about common pitfalls in recommendation-system refactoring under the name NullPointer.
  • Han Luyi realized he could organize the Bug patterns he had encountered into training data for an AI code-review tool called BugKiller.
  • Han Luyi created a BugKiller folder and began compiling a database of Bug patterns, symptoms, trigger conditions, and repair paths.
  • Han Luyi invited Su Niannian to dinner to discuss the AI code-review idea, and she agreed to meet him at seven.
Read chapter

Ch. 13Too Spicy to Handle

Han Luyi and Su Niannian discussed turning his bug-pattern database into an AI code-review tool called BugKiller, and Su Niannian agreed to help with its requirements and testing. They parted after dinner, with Han Luyi heading home to continue developing the prototype.

  • Han Luyi met Su Niannian at a Hunan restaurant and ordered dinner for them.
  • Su Niannian showed Han Luyi her analysis of seventeen competitor products and identified the gap between code and real-world impact as their core problem to solve.
  • Han Luyi proposed BugKiller, an AI tool trained on a structured bug-pattern database, and said he could build an MVP prototype in one week.
  • Su Niannian agreed to write the user research and requirements document, completing the MVP requirements during dinner and offering to test the prototype.
  • Su Niannian left by taxi after reminding Han Luyi to sleep and eat properly, and Han Luyi walked home and briefly activated Sight.
Read chapter

Ch. 14Twenty-Three Bugs

Han Luyi completed BugKiller, whose first scan found twenty-three Bugs in its own code, and sent the prototype to Su Niannian for testing. He consulted Gu Siyue about protecting the software, but she warned that his former employer’s non-compete agreement might put the project at risk.

  • Han Luyi spent a week building and training BugKiller, then compared its results with Sight and fixed every Bug in its own code.
  • Han Luyi sent the prototype to Su Niannian, who reported that it found five previously unknown problems in her team’s code and praised its impact assessments.
  • Han Luyi contacted Gu Siyue to arrange software copyright and trademark advice.
  • Gu Siyue began the registration process and asked Han Luyi to send her documentation for the software.
  • Gu Siyue learned Han Luyi had signed a non-compete agreement and warned that its terms might cover BugKiller, so Han Luyi planned to photograph and send it to her.
Read chapter

Ch. 15Late-Night Knocking

Han Luyi drove Lin Wanqing’s drunken ex-husband, Xu Jiaming, away when he came to see Lin Duoduo late at night. Sight revealed that Xu Jiaming was preparing a custody lawsuit, leaving Han Luyi considering whether to help Lin Wanqing find legal support.

  • Han Luyi used Sight to see that Lin Wanqing was afraid and Lin Duoduo was scared as Xu Jiaming pounded on their door.
  • Han Luyi confronted Xu Jiaming and offered to call a cab or the police, prompting him to leave.
  • Lin Duoduo told Han Luyi she was scared of her father, and Lin Wanqing thanked Han Luyi for helping them.
  • Han Luyi’s Sight revealed that Xu Jiaming was preparing a custody lawsuit and Lin Wanqing had no legal support.
  • Han Luyi thought of Gu Siyue and changed her contact note to “Legal Consultant—Lawyer Gu,” but went to bed without contacting her.
Read chapter

Ch. 16Lawyer's Letter

Han Luyi received a non-compete warning from Dingsheng Digital Technology Group just as BugKiller was nearing completion. After a recruiter offered him a lucrative job, he chose to consult Gu Siyue about the agreement, leaving the startup’s future uncertain.

  • Han Luyi received a reminder letter from Dingsheng Digital Technology Group demanding that he stop work covered by his non-compete agreement.
  • Han Luyi used Sight to learn that Chen Bowen had recommended the letter and Wang Zhiyuan had approved it.
  • A recruiter offered Han Luyi an algorithm director role paying over 1.2 million a year, and he reviewed the job description.
  • Han Luyi read Su Niannian’s BugKiller feedback and contacted Gu Siyue for legal advice.
  • Gu Siyue told Han Luyi to bring his separation agreement over, and Han Luyi gathered the documents to meet her.
Read chapter

Ch. 17She Was on the Fifth Floor

Han Luyi learned that Gu Siyue had secured written evidence that Dingsheng refused to pay his non-compete compensation, allowing him to terminate the agreement. Gu Siyue then revealed that someone had singled him out for a compliance review, while Chen Bowen still seemed unaware that his threat had been neutralized.

  • Han Luyi brought Dingsheng's legal notice to Gu Siyue, who showed him the demand letter, Zhang Wei's refusal to pay, and the notice terminating the non-compete agreement.
  • Gu Siyue explained that Zhang Wei's email established Dingsheng's express refusal to fulfill its payment obligation, giving Han Luyi grounds to terminate the agreement immediately.
  • Han Luyi and Gu Siyue discussed how Dingsheng's broad restricted-field clause could be challenged if the company had paid compensation.
  • Gu Siyue showed Han Luyi an internal compliance review listing more than a dozen former employees, with only Han Luyi marked in red.
  • Han Luyi left Gu Siyue's office thinking that Chen Bowen still did not know the non-compete threat had already been neutralized.
Read chapter

Ch. 18Competitor

Han Luyi completed BugKiller v0.2 and prepared to launch a closed beta while learning that a well-funded competitor was nearing its public release. He also predicted Dingsheng Digital’s company-wide recommendation system rollout would fail within 72 hours.

  • Lin Wanqing brought Han Luyi cakes to thank him, and he contacted Gu Siyue about legal help for a friend facing a custody case.
  • Han Luyi improved BugKiller’s one-click patching pass rate to 95.2%, packaged v0.2, and sent it to Su Niannian, who began planning a twenty-user closed beta.
  • Han Luyi learned that CodeSafe had secured angel funding and planned to launch its AI code review product in about three weeks, and he noted Wang Zhiyuan’s connection to its investment chain.
  • Han Luyi read a former Dingsheng colleague’s request for advice on his forum post but did not reveal that he was NullPointer.
  • Ma Xiaofei shared news that Dingsheng Digital would roll out its upgraded recommendation system across all its apps, and Han Luyi predicted it would fail within 72 hours.
Read chapter

Ch. 19I Am the Prophet

Dingsheng’s recommendation system failed catastrophically after its full rollout, vindicating Han Luyi’s earlier warnings and making his blog post go viral. As Dingsheng’s former team blamed him for the crash, Han kept working on his new project and received support from Gu Siyue.

  • Dingsheng’s faulty recommendation system produced increasingly inappropriate and duplicated suggestions before a cascading failure crashed three core apps.
  • Han Luyi used Sight to confirm that incompatible profile formats and the lack of a circuit breaker had caused the outage, and Dingsheng disabled recommendations to restore its apps.
  • People found Han Luyi’s earlier article about recommendation-system pitfalls and praised NullPointer as a prophet; Han told Ma Xiaofei and Zhang Haoran that he had written it.
  • Han Luyi continued refining his project after Su Niannian reported false-positive complaints from internal testers.
  • Zhao Qiming told Han Luyi that Chen Bowen had blamed the crash on Han’s old architecture and documentation during a review meeting.
  • Gu Siyue warned Han Luyi not to get dragged into the Dingsheng controversy and offered help if he needed it.
Read chapter

Ch. 20Loading the Magazine

Han Luyi consulted Gu Siyue after Dingsheng publicly implied he had caused its recommendation system collapse, and learned the company could still claim BugKiller as work-made-for-hire. He archived evidence to defend the product while its beta attracted a potential enterprise client, leaving his own announcement unpublished.

  • Han Luyi read Zhao Qiming's photos of Chen Bowen's review presentation and learned that Dingsheng was blaming former employees while a paid article linked him to NullPointer.
  • Han Luyi refused Ma Xiaofei's offer to respond publicly and met Gu Siyue, who advised him to gather evidence before acting because the non-compete had ended.
  • Gu Siyue warned Han Luyi that Dingsheng could claim BugKiller as work-made-for-hire and told him to preserve records proving the product's development was independent of Dingsheng.
  • Gu Siyue gave Han Luyi a referral for the custody dispute he had asked about, recommending Shen Yuwei for family litigation.
  • Han Luyi archived BugKiller's development records, while Su Niannian reported strong beta usage and a CTO's interest in integrating the product into a CI workflow through an API.
  • Han Luyi opened his drafted BugKiller announcement and hovered over Publish without posting it.
Read chapter
Page 1 of 26
AboutStatsAPIChangelogStatusContactPrivacyTermsDMCA
© 2026 RandomTranslator·v3.26·RSS