goldtag

  Two projects are done. 20 installments for Tarot Master, 20 for Four Pillars of Destiny (Saju). Across 40 total dev diary entries, my approach to AI collaboration kept evolving. It started with "wait, this actually works?" and ended with "how did I ever do this without it?" In this final installment, I look back at the journey. Tarot — Discovering Speed What I discovered in the Tarot project was speed. How fast you can ship code when collaborating with AI. Manually entering data for 78 tarot cards would have taken days — AI generated it in hours. Reading logic, UI components, state management — features that traditionally take 2-3 weeks were running in days. AI collaboration in the Tarot project was a "turbo booster." A tool that made things I already knew how to do dramatically faster. It felt like an extension of my existing development workflow, just with the speed dial cranked up. The key discovery at this stage: AI is overwhelmingly efficient at rep...

  Write the document before writing a single line of code. Every developer knows the principle; few actually follow it. But working with AI, I discovered this isn't just a best practice — it's a productivity multiplier. Especially in a complex domain like Four Pillars of Destiny (Saju), the gap between having and not having design documents was night and day. The Tarot Approach — Conversation to Code Let's look back at the Tarot project. The workflow went like this: chat with AI about "how should we structure the data for 78 cards?", AI proposes something, and you immediately translate it into code. If it works, move to the next feature. If there's a problem, continue the conversation and iterate. This approach was fast and intuitive. For Tarot's complexity level, it worked fine. 78 cards, fixed interpretation texts, relatively straightforward reading logic. The entire structure fit in my head, so conversational development maintained consistency. But the ...

  "The reading I got from this app is different from another app." If you build a Saju app, you will inevitably face this question. Same birth data, different results — naturally confusing for users. Instead of hiding this issue, we decided to confront it head-on. That was the starting point for what we call "Calculation School Settings." Why the Same Birth Data Produces Different Results Four Pillars of Destiny (Saju) is a discipline with thousands of years of history. Over that time, numerous schools of thought emerged, each with subtle differences in calculation methods. The key differences boil down to four areas. Late Night Hour (Yajasi) handling. For someone born between 11 PM and midnight, how do you determine the Day Pillar? One school says the day changes at 11 PM. Another says it changes at midnight. This single difference can change the entire Day Pillar, which cascades into every Ten Gods (Sipsin) relationship. True Solar Time application. Clock time and...