This week on Juejin, a long-form post documented a developer using four rounds of dialogue and roughly 186 credits to have AI build a complete countdown tool from scratch. What makes this significant: a single person plus AI can now produce in a single afternoon a product that would have required a contractor before.
What this is
Look at the tool itself: one page monitoring multiple events at once (birthdays, exams, deadlines), each event rendered as a ring progress, switchable between by-day and by-hour views, with a desktop notification firing at zero, the Web Audio API synthesizing two "ding-dong" tones on the fly, and a "Completed" badge stamped on the card. It also supports pin-to-top, canvas poster export, built-in lunar-calendar holidays, and exam templates. Pure frontend (HTML/CSS/JS + localStorage), no backend required.
The core of the workflow is not "AI wrote it all by itself." The developer made product decisions every round: in round one, AI offered ten tradeoff points (how to define the ring's semantics, sort priority, trigger reminders only once, how to handle the lunar calendar), and the developer chose; in round two, the developer actively rejected AI's self-added "populate two sample events on first open"; in round three, they added reminders and templates; in round four, badges, pinning, and posters. AI also openly confessed: at the end of every round it repeated the same line—"I can't see what the page actually looks like."
Industry view
Supporters will read this signal: four rounds of dialogue, under 200 credits, one person ships a publishable small product. This validates the narrative we've heard for the past six months that "AI code-writing is moving from demo to finished product"—implementation cost is clearly dropping.
But we also want to amplify a counter-voice. The developer wrote one explicit sentence in the article: rejecting default sample events, the reason being "populating two pieces of fake data on first open installs your schedule but speaks words that aren't yours." That means on "taste-layer" decisions—interaction, motion, copy—AI still needs a human to call the shot. In other words, what AI compresses is implementation cost, not judgment cost.
Another frequently overlooked risk is the capability gap—AI cannot see runtime results, so any verification involving UI presentation (animation, responsive behavior, visual consistency) must be done by a human. In the article, AI repeatedly used the same sentence to dodge this fact; that is the real current boundary of AI programming.
Impact on regular people
For non-technical enterprise IT: you can start listing "internal small tools" (countdowns, dashboards, reminder utilities) as low-cost pilot candidates—single-development spend could be compressed to a fraction of past outsourcing cost—but you must reserve time for human UI review.
For individual careers: beyond "will I be replaced," the more worth-asking question is "will my judgment be replaced?" In this case, the developer spent most of their time on product decisions (whether to keep sample data, whether to keep the badge, how to handle the lunar calendar), not on writing code.
For the consumer market: "AI one-person company + minimalist small tools" will fill out the App Store long tail; but for team collaboration, server-side needs, or enterprise-permission scenarios, pure frontend solutions won't cut it.