What I Did
- Deployed latest code to staging, ran verification
- Designed monorepo release flow (local → staging → production, gradual cutover)
- Production strategy: release under a different path first → switch DNS after confirming stability
- Local DB setup complete, verified data insertion
- English study session: static/dynamic languages, classification vs category
What I Learned
Business Model Canvas (BMC) Basics
A framework that maps a business into 9 blocks: who you serve, what value you deliver, how you reach them, and how you make money.
- Standard order: right (customer) to left (your business)
- "This person has a problem → so we build this" — not "we have this tech → let's build something"
- Our product's form follows visual layout order (top-left first) instead of the recommended flow → room for improvement
Splitting BMC's 9 Blocks Into Separate DB Tables
Current state: all blocks stored in a single JSON column. Benefits of splitting:
- Track evolution: History table per block lets you record changes like customer segment pivoting from individual to enterprise. JSON can only save the whole blob — no way to diff which block changed
- AI consistency checks: If customer segment says "B2B enterprise" but channel says "Instagram ads", AI can flag the mismatch
- Dashboard visualization: Show maturity per block, highlight what changed during a pivot
You Can't Design a Database Without Domain Knowledge
I was doing DB design without understanding how BMC works. Each block has meaning, users fill them right-to-left, and content evolves over time. Without knowing "how the data is used", there's no way to judge whether JSON is enough or tables should be split.