February 13th, although a Saturday, was also the first day that most tech companies resumed work.
At 8:50 a. m., Lin Yizhou arrived at the company, where his supervisor was standing at the entrance handing out red envelopes (lucky money) for the start of the workday.
After accepting the red envelope, Lin Yizhou smiled and said "Wishing you prosperity" to his supervisor before clocking in and sitting down at his workstation.
I opened the red envelope, and inside was a twenty-yuan bill.
This time, Lin Yizhou genuinely smiled.
Forget it, no matter how much money is inside, going to work is never a happy thing.
I turned on the computer, entered the password, and opened the last work order I made before the holiday.
Looking at the code he hadn't seen for over a week, Lin Yizhou had only one thought: Did I write this last week? What was I thinking back then?
Unfortunately, during the week-long Spring Festival holiday, Lin Yizhou was intensively working on his personal website and couldn't remember any of the company's code logic.
Lin Yizhou is a backend programmer with five years of experience. He recently switched jobs from a small company and now works at a second-tier internet company in Pengcheng.
The company's main business is CRM (Customer Relationship Management). During a previous employee meeting, the boss talked at length about how much money they had made this year, how good the company's performance was, and how bright its future was.
When it came time to distribute bonuses, HR pulled everyone aside for a private meeting. When they got to Lin Yizhou, the first thing he said was:
This year, there have been strategic adjustments, a frozen overall budget, and a poor industry environment. The reasons may vary, but the conclusion remains the same.
There is no bonus.
Lin Yizhou really wanted to ask the HR: Didn't the boss say that we made several hundred million this year?
But he swallowed his words. The HR's salary was also paid by the boss. If he really pressed for details, he would be the one to be affected by the next "strategic adjustment."
After changing jobs, my salary increased, but my work experience became worse.
The development process at that small factory was terrible, but at least they provided their employees with BugKiller Enterprise Edition, which made coding much more enjoyable.
After jumping to this second-tier company, Lin Yizhou realized what the price of so-called "standardization" was.
Every tool has to go through a procurement process; there's not even a BugKiller. The company only provides bloated software from various big companies.
He originally jumped ship with the desire to learn and grow, hoping to see a bigger world on Daping, only to find that the so-called Daping was just a bigger cog in a machine workshop.
Not to mention that process -
Back in my days working in a small factory, once a work order came in, that was it—just do it.
In large tech companies, when a work order comes in, it first goes to the product manager for review. After the product manager reviews it, it goes to the project manager for scheduling. The project manager holds a meeting to align the granularity with the technical manager. By the time the technical manager assigns it to you, half a month has already passed since the work order was created.
After only a few months at the company, the novelty of changing jobs had worn off, and the former prestige of working for a big company was gone.
Lin Yizhou now goes to work every day with the feeling of going to a funeral.
But today, besides the annoying daily work routine, there was something else that made him particularly unhappy.
You cannot use Riding the Wind at the company.
After the public beta launch of Riding the Wind before the Lunar New Year, Lin Yizhou immediately applied for an account.
And then I was so engrossed in it throughout the entire holiday that I couldn't stop.
He originally created a game forum in his spare time, which he built using the open-source Discuz! when he was in college. At the time, it was both for practice and out of interest. He would Add One features as needed, piling up all sorts of bad logic and bad code. He maintained it for so many years that it had reached the point where even he couldn't understand it anymore.
He's wanted to reconstruct this mountain of shit for almost two years, but he hasn't dared to start yet.
This truly reflects the old saying among programmers: if it can run, don't move it; don't worry about why it can run.
The moment he got the Riding the Wind, he tried it out on this shit mountain.
Amazing!
After Riding the Wind finished scanning the entire project for the first time, he compiled a "code check-up report" for him, which included a logical breakdown of seven modules, more than twenty boundary bugs, and three hidden injection vulnerabilities.
Then, in one afternoon, the entire project was refactored into a front-end and back-end separation, the front-end was completely rebuilt, and the whole system was replaced with React components.
Anyone who sees this will surely praise it as "modern"!
Lin Yizhou had been wanting to add an "anonymous account" feature, and from the initial description of the requirement to its deployment, it took less than twenty minutes.
This feeling is like Xiangzi, who had always pulled a rickshaw, suddenly driving a supercar.
It's even self-driving!
So the first thing Lin Yizhou did when he came to work was to find out if he could use the Riding the Wind at the company.
He wasn't the only one who asked; several of his programmer colleagues who usually pay close attention to the AI industry also asked him.
Less than an hour later, the company posted an announcement on its internal system.
<Statement Regarding the Use of AI Tools Within the Company>
The statement was short, filled with grandiloquent phrases like "the company encourages everyone to embrace AI" and "fully explores AI empowerment," before abruptly shifting to "for data security, it is imperative to use the AI solutions collectively procured by the company."
Finally, here's a list: Microsoft Copilot, Dingsheng CodeSafe, Dingsheng Qianyuan Code Generator----
The implication is that Riding the Wind is some kind of low-quality software and shouldn't be used.
Lin Yizhou sat back down at his workstation, turned on his computer, and looked at the work orders in his hand.
"Add a multi-tag feature to the customer list, allowing users to filter the customer list by combining multiple tags."
It looks simple on the surface, but in reality, it requires modifying the database table structure, front-end multi-select components, back-end filtering APIs, list pagination performance, and also implementing permission isolation.
At a normal work pace, it might take him a week to write.
I wonder how long it will take to build the Riding the Wind.
Unfortunately, the company doesn't allow us to use Riding the Wind.
Lin Yizhou thought for a moment, opened the Dingsheng Qianyuan interface, and entered a line of text. "Add One many-to-many tag column to the customers table. The front end supports multi-select filtering, and the back end supports querying by tag combination."
The page scrolled for two minutes, then displayed a large chunk of code and prompted Lin Yizhou to add it to a specific file.
Lin Yizhou first glanced at the database migration file. Qianyuan had created a customer-tags association table for him, which looked alright.
Then I looked at the backend code and wondered, "What is this?"
How can it conflict with a newly created table?
The two documents looked like they were written by two interns who hadn't even talked to each other.
Lin Yizhou had no choice but to re-enter his requirements, this time in greater detail.
The generated code looked like a match, except for one call that he found odd.
Isn't this a method I should be implementing? How come it can already be called directly?
He copied and pasted the code into the project, tried running it, and sure enough, it didn't work; the method didn't exist.
Then, returning to Qianyuan, I asked, "Where did you get this method from?"
Qianyuan didn't mince words either, posting a link that pointed to an internal document.
Looking at the document's title, Lin Yizhou laughed in exasperation—wasn't this the design document I wrote myself before the New Year? I wrote a method name in it, and you're just going to assume it works? If this method really existed, why would I even need to design anything?
Artificial intellectual disability.
Lin Yizhou sighed and shut down the AI tool used for the company's "official procurement."
Well, Xiangzi's sports car is gone, and he's back to the Stone Age.
After fiddling around like that, Lin Yizhou lost interest in working and decided to slack off for a while.
Open Weibo, criticize Qianyuan, and praise Riding the Wind!
On her first day back at work, Jiang Yixin arrived at the office happily.
There weren't many people in the office when she entered.
Jiang Yixin, carrying her laptop bag, walked from the entrance towards the product team. As she passed the development area, every engineer had Riding the Wind running on their screen.
Jiang Yixin's lips curled up slightly.
If a tool is good enough, users will choose it willingly.
This is the case internally at Source Code Technology, and it remains the same for external users after the public beta.
Although it's the Spring Festival holiday these past few days, she's been constantly scrolling through news about Riding the Wind on her phone at home.
The overwhelmingly negative feedback during the initial beta testing has now transformed into a debate between two factions: the "AI embracers" and the "AI threat" faction.
But Jiang Yixin is no longer worried.
She noticed a clear trend in the online debates.
Those who "embrace AI" are all loyal users of Riding the Wind, and what they share are their real experiences using Riding the Wind.
Those who claim to be "AI threats" are mostly cloud users. They probably haven't even used Riding the Wind, let alone pointed out the loopholes in its product logic or programming capabilities. They only talk about macro-level narratives like "AI is untrustworthy" and "something big will happen sooner or later."
Stop making baseless accusations, you armchair gamers!
The launch of Riding the Wind was undoubtedly a success, and its success was not due to successful marketing, but rather to the product itself.
If everyone who has used a product says it's good, then it's truly good.
At this point, you shouldn't pay too much attention to the opinions given by people who haven't used it.
Sitting at her workstation, Jiang Yixin finished up the work she had fallen behind on before the Lunar New Year, and then began to organize the data after the public beta launch of Riding the Wind.
During the Spring Festival holiday, the background curve did not decline as she had originally worried due to the holiday; instead, it showed several significant increases after New Year's Eve.
Especially from the third to the sixth day of the Lunar New Year.
The number of new registrations, Daily Active Users, and project scans continues to rise.
The code adoption rate is also slowly increasing.
Jiang Yixin clicked on the detailed data.
On the first day of the public beta, many users were just curious and wanted to try it out. The average depth of project integration was not high, and a large number of users only did code scanning and simple Q&A.
However, starting from the third day, the structure of the data used changed significantly.
More and more users are starting to let Riding the Wind directly modify the entire project. From modifying single files to linking multiple files, and then to letting Riding the Wind generate tests, refactor modules, and handle code merging feedback.
This shows that for many users, Riding the Wind has crossed the initial trust threshold and is no longer a novelty toy, but a trustworthy tool.
Jiang Yixin's palms still felt a little warm as she recalled the press conference she had hosted.
In just over a week, Riding the Wind's Daily Active Users have reached 100,000, and registered users have exceeded 870,000.
What does this growth mean?
It took Netflix three and a half years to reach one million users, Facebook ten months, Instagram two and a half months, and ChatGPT five days.
Riding the Wind is likely to reach one million registered users within the next two days.
This would be a ChatGPT-level achievement.
It's important to understand that Riding the Wind is a development tool, which requires users to have some technical knowledge. This is inherently a barrier to entry.
Han Luyi and Su Niannian's initial judgment was correct: controversy brought traffic, traffic brought exposure, and exposure ultimately translated into user numbers.
I've heard that a new tool has been created that could potentially kill the programmer profession, and those programmers will more or less want to click in and take a look.
And programmers are precisely Riding the Wind's target customers.
Based on BugKiller's experience, at this scale, it's time to consider pricing models and paid conversions.
After organizing the data, Jiang Yixin browsed Weibo again with the hashtag [#Riding the Wind].
She comforted herself, "I'm not slacking off; I'm collecting user feedback."
A trending post caught her eye.
<Please, how did you guys get your company to approve the use of Riding the Wind during work hours?>
The poster was a user named "A Leaf on a Flat Boat," who is clearly a programmer.
In his post, he complained about his company's strict procedures, saying they wouldn't approve the use of Riding the Wind, claiming it provided other software available on the market.
Tools, but those tools are all junk, not even as useful as a single hair from the Riding the Wind.
Then, below, I wrote about my own real experience.
Today is the first day back to work for many companies, and the problems he encountered are also encountered by many others. Everyone expressed their approval and shared their feelings in the comments.
[@WorkingManNo.3: No need to apply, I just brought my own computer to work. The company-provided computer is just gathering dust.]
[@SaltedFishHasLieDown: Method: Resign, currently working well]
[@BackendBoy-XiaoZhuang: OP, at least your company provided Copilot, we don't even have that, I'm still manually developing it.]
[@Slacker: No need for approval, I just told my boss it's an "internal AI assistant developed by the company," and he believed me.]
Then she saw a familiar name: Pengcheng Cross-Border Reach, a loyal user of BugKiller.
[Pengcheng Cross-Border Reach: Our company is now fully using the complete suite of tools from Source Code Technology. We will purchase the official version of Riding the Wind for every employee as soon as it is released. Resumes are welcome.]
As she read through the comments, Jiang Yixin's smile gradually faded.
She suddenly realized a problem.
Riding the Wind's reputation among programmers is gradually improving, but it is, after all, a development tool. The largest market for development tools is in the B2B (enterprise) sector.
If we want to target the enterprise market, then ensuring compliance and building trust are the most important issues to address next.
BugKiller has been on the market for more than six months. Even though it has passed the most stringent Auditing reports and its client-side algorithm is open source, it has countless subscriptions from small businesses, but orders from large enterprises have grown slowly.
If Riding the Wind wants to continue down this path, he'll probably have to be prepared for a protracted battle.
The next battleground is not on users' computers, but in the purchasing and Legal Departments of clients' companies, and in the sales departments of Source Code Technology.
This is no longer a contest of technology, but a competition of commerce.
Of course, Source Code Technology already has its own advantages in this arena. When the tools are good enough that employees actively request the company to purchase them, that in itself is a signal.
Thinking of this, Jiang Yixin quickly created a new document and wrote down all her thoughts.
The document is titled <Riding the Wind Enterprise Edition Access Plan (Draft)>.
This wasn't within her job scope, but she felt it was something Riding the Wind needed for its next step, and also something Source Code Technology needed for its future development.
After she finished organizing her thoughts, Jiang Yixin realized that she hadn't read the "Eight A.M. Digest" she had saved up in Lark yet.
This is a robot that Jiang Yixin wrote herself. Every day, it collects key keywords about Kaiwu and AI tools from the External Network to help her understand AI information overseas.
Recently busy with Riding the Wind's work, Jiang Yixin has delegated all the work on Kaiwu Overseas Edition to Li Wen.
However, she has obsessive-compulsive disorder and has to clear out the messages sent by the robot every day.
With that in mind, she opened Lark, clicked on the "Eight A.M. Digest" interface, and prepared to quickly scan it and mark it as read.
However, the first news headline that caught her eye made her eyes widen.
Neuus AI Releases the World's First Agent Programming Tool
No, you copied me again?