Archive
Browse all Logs and Insights in chronological order.
-
Week 1 Auto-Trading Recap — Apr 29–30
Two live trading days. Weekly realized P&L: +₩40,658. Trailing stop hit three consecutive wins (zero stop-losses). Closing portfolio value ₩4,928,266 — down ₩13,941 from the week's start on unrealized P&L.
-
Auto-Trading Week 1 — Position Rotation Is Starting to Take Shape
A trailing stop sell → cash recovery → RS-qualified buy rotation structure appeared in live trading for the first time. Three consecutive trailing wins, zero stop-losses. The next challenges: high-priced stock handling, holiday detection, and fixing the export bug.
-
Firebase Studio Shutdown — Migrating to Local Dev Environment
Confirmed Firebase Studio end-of-service. Migrated the chulbuji.com development environment to local VS Code on an LG Gram. Cloned the repo, confirmed the build, cleaned up the Astro 5 content config, and pushed to main. Local → GitHub → Cloudflare auto-deploy pipeline secured.
-
KOSPI Hit a Record High — But My Portfolio Was Down
KOSPI hit an intraday record. 4 of my 5 positions were in the red. The system was filling MAX_HOLD=5 slots in order of qualification, not strength. Added an RS filter and removed forced slot-filling. Running BUY_DRY_RUN=True for 2–3 trading days.
-
Filling Slots with Weak Stocks Is Not Diversification — It's Distributing Losses
MAX_HOLD=5 was a ceiling, not a target. When a system runs to fill a number, it picks available stocks, not strong ones. Four positions down on the day KOSPI hit an all-time high proved it.
-
AI Content Assistant MVP — From Dev Setup to Live Service in One Day
VS Code + Claude Code install, Next.js + TypeScript + Tailwind CSS project, GitHub + Cloudflare Pages pipeline, 8 screens implemented, OpenAI GPT-4o API connected, live service deployed — all in one day. 23 seconds from git push to production.
-
One Live Day — Fixed 5 Bugs and Found a Strategy Gap
Morning orders all failed, 18 duplicate KT sell reservations stacked, and a full regime detection redesign. 5 bugs fixed, 6 strategy changes, 4 orders executed. Seed ₩5M → close ₩4.89M.
-
The Stronger the Filter, the More Good Stocks It Blocks
What I built: Regime scoring system (5 conditions) + cash ratio logic tied to total assets. What broke: Wrong balance field caused all orders to fail; duplicate sell orders stacked 18 times. What I learned: The filter that blocks overbought stocks also blocks large-caps in recovery.
-
No Coding Skills, Live in One Day — Why Claude Design + Claude Code Made It Possible
One Claude Design Handoff feature closed the design-to-development gap. The result: an 8-screen app live in production in one day, without writing code.
-
Three Trading Bugs Found and Fixed in One Day
Three bugs in the KIS live auto-trading system — wrong cash field reference, 18 duplicate sell orders for KT, misplaced code fix. All found and fixed the same day. You don't need to read code to debug. Read logs, describe what's off, let AI trace the cause.
-
Read the Logs Before You Read the Code
You don't need to read code to find bugs. Today I fixed three auto-trading bugs in one day — by reading logs, describing what was off, and letting AI trace the cause.
-
AI Content Assistant for Small Businesses — From Idea to Screen to MVP Scope
An idea sketched into a business plan application became a mobile interactive prototype in a single day using Claude Design. v1 feedback led to v2, and it was only after seeing the screens that the MVP scope and dev environment direction became clear.
-
Auto-Trading Live Day 3 — 2 Stop-Losses, System Worked Correctly
Live day 3. KB Financial and Kakao hit the -3% stop-loss, -₩61,800 total. MA60 filter correctly blocked 3 downtrend stocks (NAVER, Kia, Hyundai Motor) — first real-money validation after the 4/21 API replacement. Budget safety margin: success at 13:00, failed again at 14:00. KT entered as new position. Closing balance ₩4,906,290.
-
The Day the System Said 'No'
Whether the system worked correctly became a more important measure than whether I made money. Live day 3 — what -₩61,800 confirmed.
-
Ideas Validate Faster on Screen Than on Paper
Writing an idea into a spec kept growing the feature list. Moving it to a screen changed the question entirely — from 'what features does it have?' to 'will users know what to do here?'
-
Auto-Trading Live Day 1 — 2 Bugs Fixed, 5 Stocks Bought
First day on the live account. Two morning bugs resolved (cached paper token / MA60 data shortage), first buys executed at 10:33. Five stocks — Kakao, Kia, KB Financial, Shinhan, NAVER — ₩4,690,300 deployed. End-of-day unrealized P&L: –₩54,030 (–1.08%), all 5 positions held.
-
Auto-Trading: 1-Week Paper Trade Complete — Switching to Live
7-day paper trading run (Apr 11–17) wrapped up. All core functions validated: regime filter, trailing stop, 5-slot management. 4 bugs found and fixed same-day. Final portfolio: ₩10,058,486. Weekly P&L: +₩45,060 (+0.58%). Live trading starts Monday 08:50.
-
The Day the System Did Nothing Was the Most Important Day
On day one, the system did nothing. That wasn't a bug — it was the right answer. What one week of automated trading taught me wasn't how to buy. It was how not to.
-
Auto-Trading System: First Live Week — Apr 13–16 Operations Log
Four days of first live operations. DRY RUN validation → first buy → first trailing stop trigger → lock file failure recovery → universe expanded to 20 stocks. Weekly realized P&L: +₩15,000. Total portfolio: ₩10,037,479.
-
The System Sold Without Me — Trailing Stop's First Live Trigger
April 15, 2:51 PM. Samsung Electronics was sold automatically. I didn't tell it to. The trailing stop fired in live trading for the first time. I'm verifying whether the strategy is moving as designed.
-
KIS Auto-Trading — First Live Order Filled, Live Transition Complete
10:30 AM. Kakao, 20 shares @ ₩48,350. The system that ran in DRY_RUN mode is now live. Three fixes before the open, trailing activation logs and Telegram position summary in the afternoon, --live flag added to the scheduler.
-
The Stocks That Did Nothing Proved the Strategy Today
The real result today wasn't the one stock I bought — it was the three that got blocked. The MA20 deviation filter stopped SK Hynix at 16.9%, LG Chem at 7.2%, Samsung SDI at 9.4%. A day the system quietly prevented the wrong buys.
-
Website Restructuring — Shifting to a Record-Asset Architecture
Two months after the rebrand, records started piling up and the structure needed to follow. A log of the transition from intro site to long-term asset architecture.
-
KIS Auto-Trading — Two Hours, 11 Items Fixed
Yesterday evening, two hours. Fixed a cash balance field bug, added retry logic, duplicate prevention, improved RSI, and introduced a trailing stop. A confirmation that systems can change this much without writing the code yourself.
-
I Didn't Have AI Fix the Code — I Redesigned the Structure
I shifted from chasing bugs one by one to a structure that separates judgment from implementation. My coding ability didn't change. What changed was where I focus.
-
KIS Auto-Trading — Module Cache Issue Identified & Buy Cycle Restored
The code was updated, but the process was still running on yesterday's state. Found the root cause, patched the MA60 gap in the paper trading environment with a fallback, and restored the DRY_RUN buy cycle.
-
I Fixed the Code. Why Didn't the System Change?
Editing the code and having those edits actually take effect are two different things. What I learned from running an automated trading system wasn't strategy — it was operations discipline.
-
Auto-Trading v1.1 — Operations Setup & First Run Standby Log
Not a day without trades — a day the system correctly refused to trade when it shouldn't have.
-
Auto-Trading MVP Complete — Rule Engine, Regime Filter & Telegram Alerts
KIS API integration, rule engine, loss-limit safety guard, Telegram alerts, and scheduler all done. First automated run starts tomorrow.
-
What I Didn't Know Until I Built an AI Trading System
I didn't write a single line of code. But the skill I used most today wasn't coding. It was the ability to precisely instruct 'what to build.'
-
I Built the House. I Just Wasn't Living In It.
Consistency isn't a willpower problem — it's a structure problem. I realized that only after counting twelve unfinished things.
-
RunBuddy Coaching MVP First Field Test — Start Button, GPS Judgment & Coaching Interval Fixes
After implementing the coaching-focused MVP, I ran a 500m indoor test. Identified three issues: unresponsive start button, mismatched voice coaching due to missing GPS data, and a coaching interval mismatch with the test distance. Each root cause was isolated and fixed. The patched build gets validated in an outdoor run tomorrow.
-
There's No Perfect Prompt. Only the Sense of Keep Moving.
What making the ChulbujiRunning music video taught me again. The more I tried to pack into a single scene, the more it fell apart. AI collaboration isn't about finding the right sentence — it's about breaking scenes down, adjusting the flow, and pushing through to the end.
-
The App Was Done. But I Couldn't Trust the Data.
Cadence hit 3,648 spm. Pace swung between 3 and 14 min/km. The app ran — but the numbers couldn't be trusted. A day of fixing 5 bugs by directing multiple AIs, one step at a time.
-
Today I Ran — and My App Talked Back
I don't know how to code. I've never written a single line myself. But today, the app I built spoke to me. A field test record of Chulbuji RunBuddy.
-
I Shipped Tetris Without Writing a Single Line of Code
4 hours. Questions only. A first-year AI builder's first deployed game — bugs included, fixed in 10 minutes.
-
Clear Roles Make AI Collaboration Work
The reason AI tools hit a wall wasn't the tools — the roles were blurred. A record of the day I designed a production pipeline where three emotional keywords are all it takes to get content flowing.
-
I Broke Bricks with AI — Vibe Coding 'Breakout' + Playground Story
A lunch-break retrospective from someone who built a game without writing a single line of code. From 1-file magic to Z Fold finger feel.
-
Insight 001 Deployed & Log Page Card Structure Transition
A record of deploying the first Insight post on chulbuji.com and restructuring the Log page with a card layout
-
5 Weeks of Transformation: How I Became an AI Product Builder
A 5-week record of a human transforming into an AI Product Builder in the age of AI civilization
-
2 Minutes of Reading, Zero Clicks — Why I Changed One Button
Visitors were reading for an average of 2 minutes, but not a single click on the CTA. Here's why I changed 'Start for Free' to 'Organize My Thoughts for Free' — and the hypothesis behind it.
-
Just Two Songs, But I Built a House
I promoted my channel with only two songs. Strangely, instead of feeling embarrassed, I felt alive.
-
Hackathon D-2: I Used to Guess. Today I Started Seeing 'Clicks'
A solo maker who can't write a single line of code successfully tracked button clicks with GA4+GTM two days before the hackathon. Chulbuji designed what to measure, Meta-chulbuji implemented it. Now I don't guess — I prove.
-
From Morning Ad to First Song: A 2-Hour Rocket Jump with Meta-chulbuji
From seeing an ad and thinking 'I want to try this' to asking Meta-chulbuji, executing through mistakes, and completing my first song 'Chuno: The Outcry' with a channel launch in just 2 hours
-
Learned for 5 Years. Now It's Time to Build: Evolving from DX to AX, from User to Builder
I share my experience of escaping 'Tutorial Hell' and launching my first AI product, the 'Meta-chulbuji Report,' by collaborating with AI as a 'Plus-Human'.
-
Code Isn't Business Until the Receipt Arrives
72 Hours of Monetizing an AI Service - The journey from localhost greenhouse to the wilderness of production where real money changes hands
-
I Argued with Two AIs, and I Lost
The operational strategy I learned from the 'Safety vs. Production' debate
-
I Started Because I Wasn't Perfect
My journey with JoCoding Hackathon and AI. Transforming hesitation into action, incompleteness into flow
-
Embracing AI with the Spirit of Sangseon Yaksu (上善若水)
Building a digital home with AI, journeying through growth with the flow of change. Will you join my rocket jump?
-
The Day I Ditched Long Prompts, and Tokens Came Alive
AI collaboration lessons learned from chulbuji.com rebuild: work small, be precise
-
AI Civilization Survival Guide: Taming the Chief Architect and Declaring v2.0 Guidelines
Recording the starting point of 'true collaboration' where AI handles labor and humans focus on thinking.
-
[Week 1 Log] From Zero to Working Website with AI Collaboration
A beginner's journey escaping from broken link hell through vibe coding
-
Rebrand Launch
Started the transition from lottery sample to record hub. Tools as byproducts, records as protagonists.
-
The Principle of Independent Trials: Do 'Hot Numbers' and 'Cold Numbers' Really Exist in Lottery?
Each lottery draw is an 'independent trial' unaffected by previous results. This post statistically explains why analyzing past 1,000 draws is meaningless for predicting the next winning numbers and why the 'gambler's fallacy' is a trap.