I want this site to do more than summarize a résumé. It should be a place where I can make a new idea tangible, explain what I learned, and improve the system in public.
The content lives with the code in structured Markdown. That means I can add a case note manually, ask Codex or Claude Code to draft one from verified source material, review the change in Git, and publish it through the same workflow.
Learning by building
Building this site has helped me learn CI/CD and the development lifecycle empirically: by making changes, testing them, reviewing what happened, and following them all the way to production. I am doing it because I want to understand the system, not because someone told me I had to.
That kind of curiosity matters to me. Reading about a pipeline can explain the sequence; owning one teaches you where trust, feedback, and recovery actually live. Each iteration turns an abstract idea into experience I can reuse elsewhere.
The rule for the playground
Experiments can be unfinished. Claims cannot be careless.
Anything presented as professional experience should remain grounded in verified work. Learning notes can be exploratory, as long as they are clearly labeled and honest about what is still being tested.
What comes next
The first version focuses on work, notes, and a readable résumé. Later experiments may include small identity demos, automation visualizations, or interactive explanations of systems concepts.