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

Recaps

The AI Wave Tycoon's Rise
VolumesArcsSummaries

Arc 2BugKiller’s Cloud Expansion

Han Luyi and Su Niannian grew BugKiller from a small product into a funded, cloud-partnered company while resisting exclusivity and surviving CodeSafe’s pressure. The arc ended with Su identifying non-technical, AI-assisted creators as a promising new market, though Han had not yet decided whether to pursue it.

  • Han Luyi accepted Zhao Wenyuan’s livestream challenge, and BugKiller beat CodeSafe on the larger codebases with more confirmed bugs and fewer false positives.
  • Su Niannian helped set BugKiller Pro’s price, joined the company full-time for twenty percent equity, and overturned Beaver Technology’s non-compete with Gu Siyue’s help.
  • As CodeSafe partnered with Dingsheng Cloud and BugKiller’s growth slowed, Han and Su planned technical improvements, stronger security credentials, and a multicloud strategy rather than exclusive binding.
  • Han brought Lu Mingzhou into the company, rejected Qingyue Cloud’s exclusivity offer, and negotiated non-exclusive partnerships with Kunlun Cloud, Tianshu Cloud, and Azure Peak.
  • BugKiller moved into a new office and hired staff, while Han ended an investor meeting after Lin Zheng criticized the company’s prospects.
  • Jiang Yixin joined BugKiller after interviewing with Han, and she and Su discovered that many users were non-programmers submitting AI-generated code.
  • Su proposed positioning BugKiller as technical insurance for AI-assisted creators, while Han reviewed evidence of their growth and paid conversion but remained unsure about targeting them.
Chapters 26–50 Vol. 1 Read

Ch. 26Cutting into the Main Artery

Han Luyi’s blog and Ma Xiaofei’s video made his layoff-to-BugKiller story a viral sensation, driving a surge in users. Meanwhile, Wang Zhiyuan offered Zhao Wenyuan access to Dingsheng’s enterprise channels, and Zhao weighed the opportunity against the risk of becoming dependent on the company.

  • Su Niannian helped Han Luyi revise his blog post about being laid off and creating BugKiller, and he published it without naming his former employer or anyone involved.
  • The blog post went viral, and Ma Xiaofei filmed and posted an interview with Han Luyi that drew hundreds of thousands of views and helped BugKiller’s registered users more than double.
  • Ma Xiaofei celebrated reaching 100,000 followers, while Su Niannian told Han Luyi that people remembered his story more readily than BugKiller’s features.
  • Wang Zhiyuan told Zhao Wenyuan that he had personally backed Zhao’s angel round and revealed that Han Luyi had been laid off from Dingsheng after contributing heavily to its recommendation algorithms.
  • Wang Zhiyuan offered to connect CodeSafe to Dingsheng Cloud’s 150,000 enterprise customers, and Zhao Wenyuan said he would think about the offer despite recognizing the risk of dependency.
Read chapter

Ch. 27All or Nothing

Zhao Wenyuan challenged Han Luyi to a public, fair evaluation of CodeSafe and BugKiller using three sealed codebases. The livestream began with more than 20,000 viewers watching, and the first test was about to start.

  • Zhao Wenyuan proposed a livestreamed head-to-head test after CodeSafe's registrations and online reputation declined.
  • Han Luyi accepted Zhao Wenyuan's challenge, and 36-Degree Technology agreed to host the evaluation.
  • Han Luyi proposed three rounds using codebases of different sizes, and sponsors supplied sealed projects neither team had seen.
  • Su Niannian checked BugKiller's systems before the livestream while adjusting to her reassignment at Beaver Technology.
  • Zhao Wenyuan and Han Luyi shook hands before the broadcast, and the host began the first round on a 30,000-line Go microservice framework.
Read chapter

Ch. 28Let the Product Speak

CodeSafe narrowly won the first round, but BugKiller dominated the larger second-round codebase with a much lower false-positive rate. Han Luyi pushed to begin the final round as Zhao Wenyuan faced mounting scrutiny.

  • CodeSafe scanned the thirty-two-thousand-line project slightly faster and found two more confirmed bugs than BugKiller, while BugKiller provided impact assessments and fix paths.
  • Zhao Wenyuan emphasized detection rate and precision, while Han Luyi calmly accepted the first-round result.
  • Su Niannian watched the livestream and believed the larger codebases would favor BugKiller.
  • BugKiller finished scanning the one-hundred-twenty-thousand-line project nearly two minutes before CodeSafe and recorded 58 confirmed bugs with two false positives.
  • The expert panel found that CodeSafe had 41 confirmed bugs and seven false positives, while BugKiller had 58 confirmed bugs and two false positives.
  • Zhao Wenyuan said CodeSafe was being optimized, and Han Luyi urged him to begin the third round on a three-hundred-fifty-thousand-line Java system.
Read chapter

Ch. 29The Higher the Way, the Taller the Demon

BugKiller decisively beat CodeSafe in the final round, exposing CodeSafe’s 38.2% false-positive rate and sending its users and reputation into decline. Zhao Wenyuan turned to Wang Zhiyuan for a large contract and learned that the deal depended on budget and personal ties, while Han Luyi continued developing BugKiller v1.2 unaware.

  • CodeSafe flagged 123 issues in the 350,000-line test, but the expert panel confirmed only 76 as bugs, while BugKiller had 127 confirmed bugs and a 3.8% false-positive rate.
  • Zhao Wenyuan thanked the community, removed his microphone, and left the livestream after the results were announced.
  • Su Niannian tracked BugKiller’s registrations as they surged, while CodeSafe suspended marketing to focus on fixing its core engine.
  • Zhao Wenyuan found that CodeSafe’s architecture failed on large codebases and called Wang Zhiyuan to ask whether Dingsheng Cloud was still interested.
  • Wang Zhiyuan told Zhao Wenyuan that the procurement budget, not product quality, drove the deal and said he would send a proposal the next day.
  • Han Luyi worked on new features for BugKiller v1.2 in 502, unaware of Zhao Wenyuan’s call.
Read chapter

Ch. 30Two Thousand Nine Hundred Ninety-Nine

Su Niannian helped Han Luyi price BugKiller Pro at ¥2,999 by showing how its team-focused features could justify the cost, and the product quickly attracted paying customers. As BugKiller grew, Su Niannian saw how little Beaver Technology valued her contributions and received a request for an annual plan while remaining tied to her job there.

  • Su Niannian reviewed eleven competing products and persuaded Han Luyi to price BugKiller Pro at ¥2,999, with impact assessment, CI integration, and a team dashboard reserved for teams.
  • Su Niannian saw BugKiller's first successful ¥2,999 payment and told Han Luyi that someone had paid for a product they had built themselves.
  • Su Niannian tracked BugKiller's growth to 47 paying users and ¥140,953 in monthly revenue, with 82.4% retention.
  • At Beaver Technology, Su Niannian watched coworkers overlook her work and saw Fang Xu credited for materials and projects she had created.
  • A CTO asked Su Niannian whether BugKiller offered an annual plan, while her Beaver OKRs assigned her only operations support work.
Read chapter

Ch. 31A Losing Case

Su Niannian resigned from Beaver Technology to work on BugKiller, but the company imposed a two-year non-compete agreement with million-yuan damages. Lawyer Gu Siyue assessed the agreement and concluded that the dispute would be difficult to win because Su’s new work directly overlapped with her former role.

  • Su Niannian asked Han Luyi for twenty percent equity in BugKiller in exchange for taking it on full-time, and Han agreed.
  • Su Niannian resigned from Beaver Technology and completed her departure procedures on June fifteenth.
  • Beaver Technology imposed a two-year non-compete covering AI, code review, and software quality assurance, with damages exceeding a million yuan.
  • Su Niannian showed the agreement to Han Luyi, who arranged a consultation with labor lawyer Gu Siyue.
  • Gu Siyue reviewed Su Niannian’s documents and said the non-compete case was difficult because Beaver paid compensation properly and Su’s new work matched her former product direction.
Read chapter

Ch. 32He Helped You Win

Gu Siyue used Beaver Technology’s own records to challenge its non-compete restriction on Su Niannian, and the arbitration panel ruled the clause was not binding. Afterward, Su Niannian committed to building BugKiller full-time, while Han Luyi asked Gu Siyue to help establish the company.

  • Gu Siyue found that Beaver had transferred Su Niannian out of the product role, cut off her access, and selectively enforced the non-compete against her.
  • Gu Siyue filed for arbitration and presented Beaver’s access records and evidence that two departing colleagues received no non-compete notices.
  • Beaver’s lawyer struggled to explain the contradiction between Su Niannian’s isolation from core information and the company’s claim that she remained bound by the restriction.
  • The arbitration panel ruled the non-compete clause was not binding and ordered Beaver Technology to stop paying compensation and return withheld amounts.
  • Su Niannian told Han Luyi she would take charge of BugKiller full-time, and Han Luyi asked Gu Siyue to draft company agreements and serve as long-term counsel.
Read chapter

Ch. 33Ladybug

Han Luyi visited Lin Wanqing and Duoduo for dinner, thanked them for the meal, and brought home Lin Wanqing’s ladybug painting. As he returned to work on the new company, Su Niannian sent him news that CodeSafe had partnered with Dingsheng Cloud, signaling that major competitors were entering the field.

  • Han Luyi visited Lin Wanqing’s home, where Duoduo showed him her drawings and asked him to come back.
  • Lin Wanqing told Han Luyi that Shen Yuwei had secured approval for her protection order and gave him a painting of a ladybug on a door.
  • Han Luyi returned to 502 and placed Lin Wanqing’s painting beside Duoduo’s ladybug drawing.
  • Han Luyi thanked Gu Siyue for recommending Shen Yuwei, and Gu Siyue praised Shen Yuwei’s handling of the case.
  • Su Niannian sent Han Luyi news that CodeSafe had partnered with Dingsheng Cloud to provide its code review engine to 150,000 enterprise developers.
Read chapter

Ch. 34Encirclement

Su Niannian and Han Luyi assessed CodeSafe’s coordinated campaign against BugKiller and devised plans to build an open plugin ecosystem and curb inference costs. As BugKiller’s registrations kept rising but new paying teams fell to zero, Gu Siyue called Han Luyi to urgently discuss compliance.

  • Su Niannian showed Han Luyi BugKiller’s slowing paid conversions, rising inference costs, and evidence of a coordinated five-front campaign by CodeSafe.
  • Han Luyi used Sight to confirm CodeSafe’s technical weaknesses and BugKiller’s continuing advantage, but found no fix path for the broader competitive threat.
  • Su Niannian proposed open-sourcing BugKiller’s SDKs and interfaces, while Han Luyi suggested a personal Pro plan and tighter free-plan scan limits.
  • That night, Han Luyi declined Ma Xiaofei’s offer to respond publicly and reassured President Li as BugKiller’s dashboard showed zero new paying teams.
  • Gu Siyue called Han Luyi and asked to urgently review her compliance framework for data security, privacy, and liability.
Read chapter

Ch. 35Who to Turn to When Things Go Wrong

Han Luyi worked to strengthen BugKiller against Dingsheng by pursuing security certifications, speeding up the product, and building trust with enterprise clients. As he continued rewriting the impact-assessment module, Sight’s experience reached 200/200.

  • Gu Siyue showed Han Luyi procurement checklists that exposed BugKiller’s missing security qualifications and helped him arrange an audit and plan a data security white paper.
  • Su Niannian presented a response plan focused on open-sourcing the SDK, improving scan speed, and strengthening BugKiller’s impact-assessment features, setting a ten-day deadline for the speed improvements.
  • Old Zhou warned Han Luyi that a superior product could still lose to a free competitor if customers did not know whom to trust when problems arose.
  • Han Luyi negotiated a security audit with Zhou Yan for one hundred thousand and a penetration test, then saw declining registrations and two clients pause their subscriptions.
  • Han Luyi found an unsolicited forum comparison favoring BugKiller and continued rewriting its cache layer as Sight’s experience reached 200/200.
Read chapter

Ch. 36Blueprint

After reaching Lv.3, Han Luyi discovered that Sight could perceive data across roughly two hundred meters and compile a plan for BugKiller’s survival. The plan warned him against an exclusive cloud-provider deal, and a nearby top-0.3% character panel prompted him to add another line to his notes.

  • Han Luyi endured a painful leveling process, then noticed that his body had become more muscular and his energy cap had risen to 500.
  • Han Luyi tested Lv.3 Sight and found that it reached about two hundred meters while keeping unexamined data collapsed into gray dots.
  • Han Luyi asked himself what to do about BugKiller and received a five-step commercialization plan that put its current survival probability at 31%.
  • Han Luyi noted that an exclusive cloud-provider deal carried a 34% long-term survival rate, recorded the plan, and messaged Su Niannian to meet the next morning.
  • Han Luyi spotted a top-0.3% character panel in apartment 501 and added another line to his notes before closing Sight with 61 energy remaining.
Read chapter

Ch. 37Tai Chi

Han Luyi used Path Compilation to devise a multicloud strategy for BugKiller and persuaded Su Niannian to pursue non-exclusive partnerships. He arranged an introduction through Zhongdun and accepted a meeting with FA Lu Mingzhou, while the cloud marketplace talks awaited BugKiller’s audit report.

  • Han Luyi compiled channel strategies and found that multicloud neutrality offered BugKiller a better long-term survival rate than exclusive binding.
  • Han Luyi convinced Su Niannian that BugKiller should approach Qingyue Cloud or Tianshu Cloud first, then use their interest to negotiate with Kunlun Cloud and seek simultaneous partnerships.
  • Su Niannian drafted a channel outreach plan and proposed upgrading BugKiller’s brand; Han Luyi suggested commissioning Lin Wanqing to create its visual design.
  • Han Luyi asked Zhou Yan about cloud contacts and learned that Zhongdun could introduce BugKiller to Qingyue Cloud and Tianshu Cloud after its audit report was completed in about two and a half weeks.
  • Zhang Haoran introduced Han Luyi to FA Lu Mingzhou Frank, who requested an informal coffee meeting that weekend.
Read chapter

Ch. 38A High-Stakes Gamble

Han Luyi commissioned Lin Wanqing to design BugKiller’s brand identity and recruited finance professional Lu Mingzhou to help the startup prepare for fundraising. The chapter ended with Han heading toward a meeting with Qingyue Cloud’s Developer Ecosystem Director Liang Yu the following Tuesday.

  • Han Luyi asked Lin Wanqing to create BugKiller’s brand design at market rates, and she agreed to consider the project and send a quote.
  • Lu Mingzhou met Han Luyi, praised BugKiller’s product and community, and offered to join the startup rather than act as a fundraising intermediary.
  • Han Luyi and Lu Mingzhou agreed on a 5% equity stake, with an additional 2% from the option pool if Source Code Technology raised funds at a valuation of at least fifty million within a year.
  • Han Luyi told Su Niannian about the deal and asked her to have Lawyer Gu draft an agreement and meet Lu Mingzhou.
  • Zhou Yan told Han Luyi that the audit report was ready and arranged a meeting with Liang Yu of Qingyue Cloud for next Tuesday at two in the afternoon.
Read chapter

Ch. 39Hesitation Means Defeat

Han Luyi and Su Niannian received Qingyue Cloud’s lucrative but exclusive partnership offer and decided to use it to approach Celestial Pivot instead of accepting. Their negotiations remained unresolved as a BugKiller customer reported a competitor’s free offer and another customer cancelled its subscription.

  • Liang Yu offered BugKiller a guaranteed monthly payment, promotional resources, and an eighty-twenty revenue split in exchange for three years of exclusivity on Qingyue Cloud.
  • Han Luyi and Su Niannian left without answering Liang Yu and agreed that they would not sign an exclusive deal.
  • Lu Mingzhou assessed Qingyue’s offer and advised them to use it as leverage while Han Luyi gathered customer requests for Celestial Pivot integration.
  • Han Luyi, Su Niannian, and Lu Mingzhou began contacting Celestial Pivot through customer feedback, former colleagues, and an investment contact.
  • Mr. Li told Han Luyi that CodeSafe was offering free service and cloud vouchers, and Han Luyi saw a cancellation notice for Ruisi Data’s annual plan.
Read chapter

Ch. 40Everything Is Within Range

Han Luyi pursued Celestial Pivot while Azure Peak pressured him to pause negotiations, as BugKiller lost customers and its paid-user numbers declined. He and Su Niannian prepared to meet Celestial Pivot’s business development head, with Han Luyi insisting that they should keep their options open.

  • Han Luyi contacted a customer, Gao Lei, who offered to ask his technical contact at Celestial Pivot for an introduction, while Lu Mingzhou reported that Celestial Pivot’s strategic investment team had requested BugKiller’s figures.
  • Su Niannian handled customer questions about rival CodeSafe Enterprise, while Han Luyi saw two paid customers cancel their subscriptions.
  • Lu Mingzhou arranged a Friday meeting with Celestial Pivot business development head Zhou Mingyuan, and Han Luyi planned to present the upcoming Version 1.3 release.
  • Han Luyi chose Lin Wanqing’s second branding proposal, featuring a seven-spotted ladybug, and shared the finished brand assets with his team.
  • On Friday morning, Azure Peak’s Liang Yu learned that Han Luyi was talking with Celestial Pivot and put Azure Peak’s exclusive proposal on hold.
  • Han Luyi told Su Niannian that they should meet Celestial Pivot before reconsidering Azure Peak, and the two prepared for their meeting.
Read chapter

Ch. 41Not Giving an Inch

Han Luyi negotiated non-exclusive partnership proposals with Tianshu Cloud and Kunlun Cloud, securing a 92% revenue share from Kunlun. As Source Code Technology compared the offers and waited on Azure Peak, Liang Yu called Han Luyi to revisit their earlier talks.

  • Han Luyi and Su Niannian met with Zhou Mingyuan, who reviewed BugKiller’s live Tianshu Cloud data and proposal and promised an answer the following week.
  • Chen Kai from Kunlun Cloud contacted Han Luyi to arrange a meeting, and Han Luyi later met him to discuss a non-exclusive partnership.
  • Han Luyi rejected Kunlun’s standard 85% revenue share and insisted on 92%, which Chen Kai’s superiors approved.
  • Lu Mingzhou and the team compared Tianshu Cloud’s and Kunlun Cloud’s proposals while Han Luyi said Azure Peak would return.
  • Liang Yu from Azure Peak called Han Luyi and said they had handled their previous discussion too hastily.
Read chapter

Ch. 42I Spoke Too Loudly Just Now

Han Luyi renegotiated Source Code’s cooperation with Azure Peak, securing stronger promotional support while preserving the deal’s financial terms. After Lu Mingzhou estimated the company’s valuation and they planned new hires and an office, Han Luyi and Su Niannian went out to eat.

  • Liang Yu offered to remove Azure Peak’s exclusivity clause, and Han Luyi invited him to meet.
  • Han Luyi negotiated expanded promotion for Source Code while keeping the guaranteed minimum and revenue split unchanged.
  • Lu Mingzhou calculated that Source Code’s projected monthly revenue of 600,000 implied a valuation of 35 to 56 million.
  • Han Luyi, Su Niannian, and Lu Mingzhou agreed they needed to hire staff and find an office.
  • Lu Mingzhou left to cook for his wife, and Han Luyi invited Su Niannian to a restaurant for spicy pickled cabbage fish.
Read chapter

Ch. 43Four-Person Company

Han Luyi met Gu Siyue to collect revised contracts for BugKiller’s cloud partnerships, then joined his three colleagues at their new office as Lu Mingzhou presented a growth forecast and valuation. The story left them facing Dingsheng Cloud’s decision to make rival CodeSafe a free, automatic tool for millions of developers.

  • Han Luyi met Duoduo and Lin Wanqing as Duoduo prepared for her first day of elementary school.
  • Han Luyi collected three revised cloud partnership contracts from Gu Siyue, who clarified promotion terms and data ownership language.
  • Han Luyi arrived at BugKiller’s new office, where he worked alongside Lu Mingzhou, Su Niannian, and newly hired finance worker Zhou Li.
  • Lu Mingzhou projected monthly revenue could pass one million within six months and valued BugKiller at 60 million to 80 million, then proposed meeting venture capital firms.
  • Lu Mingzhou showed Han Luyi and Su Niannian that Dingsheng Cloud had made CodeSafe a built-in tool for its users, and asked whether to cancel the planned investor meetings.
Read chapter

Ch. 44Game Dev Story

Han Luyi reassessed the threat posed by CodeSafe and decided BugKiller should focus on helping customers see the difference between the products. While screening job applicants, he discovered that Sight could be programmed to show a concise, customized profile, though using it drained his energy.

  • Han Luyi concluded CodeSafe was more likely part of Dingsheng Cloud’s ecosystem strategy than a direct attack on BugKiller, then discussed pricing and customer outreach with Su Niannian and Lu Mingzhou.
  • Han Luyi and Su Niannian reviewed résumés and joked about several unsuitable applicants.
  • Han Luyi used Sight on a résumé and found that its detailed applicant information made screening harder rather than easier.
  • Han Luyi discovered he could bring up a code-editor-like interface and customize Sight to show only selected fields.
  • Han Luyi refined Sight’s output into brief applicant profiles and continued screening résumés as his energy fell from 437 to 337.
Read chapter

Ch. 45An NP Teacher in the Flesh!

Jiang Yixin, a devoted NP fan with an offer from Celestial Pivot, interviewed at Han Luyi and Su Niannian’s small company, Source Code Technology. After struggling with Han Luyi’s technical questions and revealing her existing offer, she left without knowing whether she had been hired.

  • Jiang Yixin went to interview at BugKiller despite planning to start at Celestial Pivot the following Monday.
  • While waiting, Jiang Yixin met Chen Jianye, who criticized the small company and advised her to choose a major firm.
  • Su Niannian welcomed Jiang Yixin and escorted her to a shared meeting room, where Jiang Yixin met Han Luyi in person.
  • Han Luyi tested Jiang Yixin with difficult technical questions, and Su Niannian asked what feature she would add to BugKiller.
  • Jiang Yixin described her Celestial Pivot offer of 320,000 a year, and Han Luyi ended the interview without giving her a decision.
  • Jiang Yixin messaged her best friend that she had met NP and had been crushed by the interview.
Read chapter

Ch. 46What were they even babbling about?

Han Luyi and Lu Mingzhou met Qihe Ventures partner Lin Zheng to seek investment for Source Code Technology, but Lin Zheng dismissed the company’s prospects. Han Luyi ended the meeting, then reassured Lu Mingzhou that he trusted him and that they could wait for stronger numbers before seeking investors.

  • Lu Mingzhou coached Han Luyi to pitch BugKiller’s technological moat, developer community, and possible future large model, and asked whether Han Luyi and Su Niannian were dating.
  • Han Luyi and Lu Mingzhou met Lin Zheng at The PuLi Hotel, where Lin questioned Han Luyi’s departure from Dingsheng and criticized the product’s user and conversion numbers.
  • Lin Zheng called BugKiller a small utility product in a crowded market with a low ceiling, and Han Luyi used Sight before ending the meeting.
  • In a taxi, Han Luyi offered to buy back Lu Mingzhou’s shares at a fifty-million-yuan valuation if he had doubts, but Lu Mingzhou reaffirmed his faith in the company.
  • Lu Mingzhou warned that Han Luyi’s abrupt exit could hurt their reputation with other investors, while Han Luyi insisted that strong numbers would bring investors to them.
Read chapter

Ch. 47She Thought So Too

Han Luyi learned that Dingsheng had acquired Flash and checked with Gu Siyue about legal risks from the report he filed. At the office, Su Niannian approved Ma Xiaofei’s proposal to create promotional videos, and Ma left Han with a pointed question about Su’s feelings.

  • Ma Xiaofei visited Han Luyi and Su Niannian’s new office to discuss making promotional videos for their product.
  • Ma Xiaofei told Han Luyi that Dingsheng had acquired Flash, and Han asked Gu Siyue whether the acquisition created legal risks from his report.
  • Gu Siyue reassured Han that the reporter’s identity was protected and offered to help if anything happened.
  • Ma Xiaofei asked Han what his relationship with Su Niannian was, then said she had asked him about Han after Han was laid off.
  • Su Niannian approved Ma Xiaofei’s request to write up a proposal for developer-focused promotional videos.
  • Su Niannian asked whether Han was sure about the new developers, and Ma Xiaofei asked Han if Su thought of him the same way.
Read chapter

Ch. 48The First Day of Saving the World

On her first day at the startup, Jiang Yixin learned the Tianshu Cloud adaptation from Han Luyi, received cautious advice from Zhao Lei, and discovered an unusual pattern in BugKiller submissions. After her friend suggested AI-generated code might explain it, Jiang went to find Su Niannian.

  • Jiang Yixin arrived early and mistook Zhao Lei for a legendary expert before meeting the bald Chen Jianye and starting work with them.
  • Han Luyi assigned Chen Jianye to Kunlun Cloud, Zhao Lei to Qingyue Cloud, and Jiang Yixin to Tianshu Cloud, then showed Jiang the existing CI tools.
  • Chen Jianye complained that the company lacked project management and CI, while Zhao Lei warned Jiang to document requirements and verify API versions.
  • Su Niannian asked Jiang to analyze BugKiller submissions, and Jiang found users whose unusually frequent submissions shared similar coding styles.
  • Jiang volunteered to help at the upcoming Cloud Developers Conference, then told her friend about the suspicious submissions and heard that AI-written code could explain them.
  • Jiang locked her phone and went to find Su Niannian.
Read chapter

Ch. 49Vibe Coding

Su Niannian and Jiang Yixin analyzed BugKiller’s anomalous users and discovered that non-programmers were using AI to build products, then relying on BugKiller to fix the resulting errors. Su Niannian identified “Vibe Coding” as a promising market and headed with Jiang Yixin to discuss the opportunity with Mr. Han.

  • Jiang Yixin found that a large group of BugKiller users had unusually similar code and error patterns, and Su Niannian helped visualize and analyze their data.
  • Su Niannian and Jiang Yixin concluded from the users’ job titles, work habits, and code comments that they were non-programmers using AI to generate code.
  • Su Niannian framed BugKiller as technical insurance for people creating products with AI and named the opportunity “Vibe Coding.”
  • Su Niannian’s mother called to urge her to meet a potential partner and mentioned that her parents no longer objected to the out-of-town man she had once dated.
  • Su Niannian outlined the market’s large user base, willingness to pay, and rapid growth, then went with Jiang Yixin to find Mr. Han.
Read chapter

Ch. 50Lifeline

Su Niannian argued that BugKiller should serve non-technical AI coding users, whose repeat purchases suggested they depended on it more than professional programmers did. Han Luyi reviewed the evidence and Sight’s analysis, leaving the product’s direction undecided but revealing strong growth potential and a risk of churn.

  • Su Niannian presented data to Han Luyi showing that non-technical users submitted heavily and paid at higher rates, while Han questioned whether they were worth targeting.
  • Jiang Yixin shared paying users’ requests for an intermediate pricing tier and one-click execution, and Han said he would think about Su Niannian’s proposal.
  • Su Niannian praised Jiang Yixin for independently reviewing support tickets, then checked her call history, where “Mom” remained at the top.
  • Jiang Yixin told her friend Liu Haoyu that she admired Su Niannian and NullPointer and would attend the Cloud Developers Conference with them.
  • Han Luyi used Sight to review an analysis predicting rapid growth and above-average paid conversion among non-technical creators, while warning that BugKiller’s current interactions could cause churn.
Read chapter
Arc 2 of 21
AboutStatsAPIChangelogStatusContactPrivacyTermsDMCA
© 2026 RandomTranslator·v3.26·RSS