Monday, August 17, 2026Vol. 5 · No. 33 · Whole No. 2176 Pages TodayFree

GitHub Stars 1400+
Open Source Projects 20+

.

This EditionSet by AI

AI FULL STACK INDIE DEVELOPER

The Lead

Turning AI into Products with Code

From NLP algorithm engineer to AI full-stack indie developer — one person turning ideas into products people actually use. Page one records the tradeoffs along the way.

By Ailln · Hangzhou, China

Most of my energy these past few years has gone into one thing: collapsing frontier AI capability into products an ordinary person can just open and use. The models change every week; what survives is whatever actually solved a problem.

Hence Vibe Coding — ship v1 within the hour, then let real feedback decide where it grows. The code I delete usually matters more than the code I write.

Three terminals stay open while I work: Cursor for anything with a screen attached, Claude Code for refactors and migrations, Codex for the long jobs I would rather not sit and watch. Whichever fits the moment gets used, with no stack to defend. What is scarce was never tooling — it is judgement.

cn2an was the first of them, a small utility turning Chinese numerals into Arabic ones, now downloaded a hundred thousand times a month. Its lesson was plain: doing one small thing well enough that others depend on it beats ten half-finished ones.

Open source is part of that method. Publishing the code is the most honest demonstration of capability, and the shortest path to putting a tool in the hands of whoever needs it.

More of them died than shipped. The half-finished ones are all parked under an org called ai-graveyard — the name is a joke at my own expense, and a reminder that most ideas never reach anyone. The code in the graveyard stays public; anyone who wants to pick it up can.

Building alone, writing code turns out not to be the bulk of it. The rest goes to answering issues, rewriting copy, watching errors come in, and working out what the next version should drop. None of that hands off to a model yet.

Also in This Issue

design-vibes

Interactive guide to 24 web design styles

TypeScript

ai-plot

AI Visualization Tool

TypeScript

In This Edition

  • 02
  • 03
  • 04
  • 05
  • 06
Editor
Ailln
Set by
Cursor · Claude Code · Codex
Printed by
Vercel
Offices
Hangzhou, China
Submissions
github.com/Ailln
ABOUT
PAGE 03 / 06

Feature

From Algorithm Engineer to Indie Developer

From owning one segment of the pipeline to owning all of it, from request to deploy.

By Ailln · Hangzhou, China

Continued from Page 01For the years I worked as an algorithm engineer, I owned one segment of the pipeline: clean the data, tune the model, watch the metrics, hand it off. What the product finally looked like was not mine to decide.

Now all of it is mine — from judging whether a request is worth building at all, to shipping it and watching the errors come in. The biggest change was not the stack. It was the bar for calling something finished: I used to ask whether the metric moved, and now I only ask whether anyone actually uses it.

That bar is unforgiving. By its count most of what I build has to be written off as useless; the few that did hold on to people are the ones worth polishing for a long time.

Telling whether something held on is not hard either: whether anyone chases the next release in the issue tracker, and whether anyone has written it into their own dependencies. Neither of those can be faked.

Now I only ask whether anyone actually uses it.

Typeset · Ailln皖ICP备16003789号-12
JOURNEY
PAGE 04 / 06

Tools & Chronology

What I Build With, and How I Got Here

The tools at hand on the left; the timestamps of these years on the right.

TECH

From 2017 to NowA pulse travels the timeline; tools briefly develop beside the years they shaped.TIMELINE · TOOLING

LANGUAGES & FRAMEWORKS

PythonTypeScriptJavaScriptReactNode.jsFastAPI

AI & ML

OpenAIClaudeAnthropicLangChainVector DBPrompt Engineering

TOOLS & INFRASTRUCTURE

DockerGitCursorVercelSupabasePostgreSQL

JOURNEY

  1. 2026

    • Shipped Solo: a navigator for one-person AI companies
    • Open-sourced ai-interview: an AI interview assistant
    • Open-sourced design-vibes: 24 web design styles, interactive
  2. 2025

    • Open-sourced Build AI Template: a starting point for AI apps
    • Moved the projects under the ai-graveyard org, all code public
    • Started writing about AI development on Xiaohongshu (@艾林AI)
  3. 2024

    • cn2an passed 600 GitHub stars
  4. 2023–2017

    • Open-sourced cn2an: Chinese numerals to Arabic, 100K+ PyPI downloads/mo
    • Worked as an NLP algorithm engineer: clean data, tune models, watch metrics

The chronology records only what left a trace. Practice runs and abandoned projects are not listed — they are in the graveyard mentioned on Page 01.

Typeset · Ailln皖ICP备16003789号-12
PHILOSOPHY
PAGE 05 / 06

The Leader

Down to Four Rules

Not maxims — four judgements still in use. Each one has ruled something out.

The Copy Desk Is Still CuttingDense copy passes through the edit; the noise falls away, leaving four clear judgements.EDITORIAL PROOF
  1. 01

    Name the First User

    Before building, I have to name who the first user is and what they make do with today. If I cannot, I drop it — this rule kills more ideas than it approves.

  2. 02

    Ship It Incomplete

    The first version goes out missing features, styling and docs. Only once someone has used it do I know what to fix. Before that, every plan is a guess.

  3. 03

    Narrow but Solid

    cn2an does one thing: Chinese numerals to Arabic ones. A hundred thousand downloads a month rely on it — not for its features, but because the awkward edge cases got fixed one by one.

  4. 04

    Bugs in Public

    Every bug sitting in my issue tracker says what I missed. That is uglier than any résumé, and more credible than any résumé.

Editorial Board · Ailln

Reach the Paper

Typeset · Ailln皖ICP备16003789号-12
PRESS
PAGE 06 / 06

The Press Room

How This Paper Gets Made

Three machines set the pages; one person signs off before it prints. The process is public — copy it if it is useful.

The Benches

Three Machines at PressThe rollers keep turning and paper runs beneath the ink. The night shift is not over.PRESS ROOM · LIVE
  1. 01

    Cursor

    The Copy Desk

    Anything with a screen attached is edited here, the page open alongside so I can see what moved.

    Why itIn a pile of existing code, it is the best at finding the handful of lines that actually need to move.

  2. 02

    Claude Code

    The Composing Room

    The jobs that tear a page down and set it again: refactors, migrations, replacing a whole version.

    Why itHouse rules go in AGENTS.md — spelled out properly, it runs a long way without drifting.

  3. 03

    Codex

    The Night Shift

    Long jobs I would rather not sit and watch: bulk renames, filling in tests, clearing dependencies.

    Why itHand it off and go do something else; collect the whole thing later.

Proofing

  1. 01

    Commission

    What it is and what it is not. If I cannot say, it does not start — this step never goes to a model.

  2. 02

    Set

    The model writes the first version. I do not interrupt.

  3. 03

    Proof

    Read every line. Whether it is right is the one call only I can make.

  4. 04

    Print

    Ship it, then watch the errors come in.

This page was set by the same process as the rest of the site.皖ICP备16003789号-12