EN 简 繁 日

Blog

My Story: Taking BaZi Global — With Zero Code

A Founder's Story · SQ the Wayfarer · July 2026

A 50-something serial entrepreneur. Can't write a line of code. Friends gave occasional technical advice. Two AI agents did the heavy lifting, and I refused to quit. Less than two months later, a BaZi-based cultural export platform was live. This is what actually happened.

Who I Am

I'm a Buddhist lay practitioner. Over 50. Spent 30 years building communication hardware for international markets — more than a decade of that living overseas. Serial entrepreneur.

I've spent years reading Chinese classics — the Tao Te Ching, Wang Yangming, Liao-Fan's Four Lessons, the Heart Sutra, the Diamond Sutra, the Platform Sutra, the Yogācāra teachings. Not for fortune-telling. For understanding myself better.

This project — taking BaZi overseas — is the starting point, not the destination. It's my first attempt to translate Eastern wisdom into a language the rest of the world can hear, using everything I learned in 30 years of crossing cultures.

Middle May 2026. I decided to do it. I couldn't write a single line of code. Didn't know what an API was. Had never touched Astro, Stripe, or Dify.

My technical team: two AI agents. CODEX handles strategy and architecture review. CLAUDE writes the code and deploys. I handle direction, product design, content, testing, and every final decision. Less than two months. From zero to live. These are the parts I remember.

Phase One: Figuring Out What Even Works (May)

First two weeks, I couldn't tell the difference between Dify and ChatGPT. Tried Coze, tested platforms, cycled through everything. Eventually chose self-hosted Dify — full control over the AI workflow.

The BaZi charting engine had to be built from scratch. No off-the-shelf library exists. Charting requires True Solar Time correction, Daylight Saving Time detection, Solar Term alignment, and midnight boundary rules — every step pure mathematics, not mysticism. We validated against nearly 500 historically documented birth charts with established scholarly consensus — black-box parameter tuning until the scoring engine consistently matched traditional interpretation while reading naturally in a modern, cross-cultural context.

Phase Two: Pricing and Content Architecture (June)

Global pricing. One benchmark price worldwide, adjusted by region. Thirty years of selling overseas taught me this: purchasing power differs, but the price tag must never make anyone feel discriminated against.

Product architecture. Three products — SilentBloom (love), SilentPair (relationships), BetweenCycles (life rhythm) — all running on the same backend pipeline: chart calculation → scoring engine → language library → Dify workflow.

Building the workflows ate the most time. Starting from zero, every node had to be screenshotted and sent to an AI for advice. Over a dozen node configurations tested. Took 20-plus days to stabilize. After that, I wrote the prompts based on my own understanding of these traditions. CLAUDE translated them into Dify workflows. CODEX reviewed outputs for Western cultural fit. I made the final call. Twenty-some iterations later, the output is stable.

Phase Three: July — From Soft Launch to Real Operations

July 1: Soft Launch

Site went live. Seed users started testing.

July 9: English Reports Were Blank — Five Layers Deep

All English-language report pages across three products showed nothing but white.

Not a one-fix bug. Round one: component nesting. Fixed. Still blank. Round two: rendering mode conflict. Fixed. One blank page gone, two left. Round three: architectural — switched rendering on all 16 pages. Another blank gone, one left. Round four: the English language pack was missing three fields. Chinese, Traditional Chinese, and Japanese all had them. English didn't. Fixed. Better. Round five: six string replacements crashed when data hadn't arrived yet. Added fallback guards. Actually fixed.

I don't understand code. But 30 years of hardware engineering taught me one thing: systemic failures can't be patched at the surface. Those five layers weren't five independent bugs. They were one problem stacked five deep. At the bottom: the architecture had zero tolerance for change.

After this, every deployment gained one extra step: deploy → stare at the server for 10 seconds → run the full smoke-test. Two seconds of checking can prevent 27 minutes of outage.

July 9 (same day): Who Does What

The weeks before, we kept fixing one bug and introducing another. Root cause: my judgment during code changes and CLAUDE's execution had no clear boundary.

We fixed it:

One person writes code. Others give advice. One brain, one pair of hands. No directional drift since.

July 10: 2 AM — 325 Crashes in 27 Minutes

Middle of the night. Every language. Every product. Down.

Root cause: I edited one line of source code directly on the server. The build produced a JavaScript file with a syntax error. pm2 reload spun it into a crash loop — 325 restarts in 27 minutes.

The fatal mistake wasn't the bad code. It was that after reload, I didn't look at the process list. The restart counter was screaming upward. I only had to glance — two seconds — and I'd have known the deploy failed. I didn't.

That night, non-negotiable rules were written: never edit source code on the server. After every deploy, immediately check the restart counter. Run the smoke-test — all five checks green before you walk away. These rules are now the first thing I review every morning.

July 12-15: Features Built at Speed

Card system. Three days to build Daily Energy Card, Monthly Energy Card, and Love Season Card. The English copy went through five rounds. Example: "childhood" became "early nature" — because the Year Pillar isn't about childhood. "Hidden in the XX sign" became "hidden in the XX year" — "sign" is an astrology word, not a zodiac word.

Traditional Chinese cleanup. Simplified characters were scattered all over the Traditional site. Built a character-level conversion function. Now every Chinese string auto-converts in Traditional mode. No manual maintenance.

Text-to-speech. Someone said reading 800 Chinese characters on a card every day strains the eyes. Two hours. Browser's built-in speech API. Zero cost. Three cards plus the report page now each have a 🔊 button.

Price first. Moved the price tag above the form. User sees the value, then decides whether to fill anything in.

July 15-21: Rewriting Every Landing Page

Three products. Four languages. Twelve pages. All rewritten.

The old copy read like translation software run forward and backward. This time, everything was written in the brand's own voice. BetweenCycles' Chinese site got the brand line: "知天地轮转 · 溯人生本源" — Know the turning of heaven and earth. Trace life back to its source. The English site replaced four Tang Dynasty poems with Shakespeare and Tolkien. Not laziness — 30 years of cross-cultural instinct: the language you use to explain BaZi to a Westerner is not the same language you use with a Chinese reader. Bridge with images they already know. It works better than forcing unfamiliar culture on them.

SilentPair's copy was aimed at one narrow person: someone who can't let go of someone else, and came looking for an answer.

SilentBloom kept the tenderness of "Before Love Has A Name." But the hero description went from translation-ese to something that could actually land.

July 17: Invite Codes and Referral System

Two types of codes in parallel: founder codes (time-limited, quota-limited) and user share codes (permanent). Every successful friend invitation adds 30 days of membership. No cap.

July 19-21: Turning the Books I've Read Into a Product

Tao Te Ching. Liao-Fan's Four Lessons. Heart Sutra. Diamond Sutra. Platform Sutra. Wang Yangming. The Yogācāra teachings. I've read them for years. This time, I wrote them into the foundation of the product.

I organized everything into a three-layer framework: BaZi (know your pattern), Liao-Fan (change your path), Yogācāra (transform at the root).

BaZi shows what your birth energy configuration looks like. Liao-Fan says that configuration isn't fixed — it can be changed. Yogācāra goes deeper: your troubles aren't in your thinking mind. They're old seeds stored in the deepest layer of consciousness. Know this, and when anxiety rises, you don't fight it. You just watch an old seed sprouting.

All three layers are now in our Learn pages, in both Chinese and English. Alongside "System Standards and Time Calculation" — an article explaining True Solar Time from a global perspective, with Beijing and New York as examples, and why we use Hong Kong Observatory time accurate to the second. That's my confidence in this engine.

July 20: AI Couldn't Find Us

Checked the site and discovered: GPTBot, ClaudeBot, Google-Extended — every major AI crawler — all blocked by Cloudflare by default. Someone asks ChatGPT "any BaZi-based tools?" and it can't see us at all.

Spent an afternoon untangling Cloudflare panel switches. Added Schema.org markup. Eventually, it worked. Same day, found English knowledge base retrieval was weaker than Chinese — Rerank was off for the entire English pipeline. Fixed. All three languages now aligned.

The Worst Day

Afternoon of July 17. I was chasing a report preview bug. To trace the root cause, I switched between several code versions on the server. When I finished debugging — the database had been rebuilt.

One hundred founder invite codes. All payment records. All registered members. All referral relationships. Gone.

I sat there for a long time.

Those codes — I'd given them out one by one. Old friends. Young people I admired. Strangers who helped me test. Now all vanished.

I didn't want to message each person asking "does your code still work." I made a different choice: wrote a script so that any AIF-format code from the old system auto-resurrects the next time someone tries to redeem it. Then I opened the original file on my desktop — 98 codes — and restored them manually, one at a time.

Same day, a smaller fire: every landing page form threw "Failed to fetch." Turned out the server was blocking those three domain addresses. Five minutes. One line in the CORS whitelist. Fixed.

But 100 codes' worth of damage isn't undone in five minutes. Since that day: automatic database backups run before every deploy. The founder code is baked into the system startup script — can't be deleted, can't be lost. The worst day built the strongest defenses.

What I Actually Think

I can't write code. But I understand systems. Thirty years of building communication hardware taught me: systemic failures can't be patched at the surface. That instinct transfers.

AI doesn't replace people. It amplifies them. I've never written a line of code. With two AI agents and clear division of labor, I shipped a BaZi-based cultural export product from zero to live in less than two months. I'm not smart. But I know where we're going, and I know how to assign who does what.

Traditional culture isn't mysticism. It's an empirical framework. BaZi isn't fortune-telling. It's a system for observing life rhythms, refined over centuries. My years overseas convinced me: this framework has as much value for Westerners as for Chinese. It just needs to be spoken in a language they can hear.

The worst moments pour the strongest foundations. Database lost → automatic pre-deploy backups. Build corrupted → post-build syntax validation. Founder codes gone → baked into startup code, undeletable. Every defense grew out of a wound.

Tech Stack

One Last Thing

Less than two months. From zero knowledge to live product. Not because I'm good — because the direction was right, the division of labor was clear, and the AI tools pulled their weight.

If you're a 20-something developer, none of this may impress you. If you're like me — a hardware entrepreneur who's never written code but wants to build something — I hope this record shows you one thing: the barrier isn't technical. The barrier is figuring out how to work with AI the right way.

This story isn't polished. It isn't prettied up. It doesn't pretend to be calm. It's just one ordinary person, stumbling forward, falling down, getting up — and making something he genuinely loves.

AI Fortune is still evolving. Come try it.

SQ the Wayfarer · July 2026