Hello, world.
I’m finally publishing the projects, experiments, and mistakes that used to stay in my folders and notes.
Coding agents have made it much faster for me to move from an idea to something I can try. They help investigate problems, explore codebases, test ideas, and handle the unglamorous details between a thought and a working result. I still choose the direction and make the judgment calls.
- 01 Idea Choose a useful direction
- 02 Agentic build Research, code, and test
- 03 Working thing Exercise human judgment
- 04 Share Publish what was learned
Small ideas no longer have to wait for a perfect block of uninterrupted time. I can turn a question into an experiment, then decide whether the experiment deserves to become a tool. Publishing the work also forces me to explain what I learned before everything feels finished.
I’ll write about projects I’m building, patterns that work, mistakes worth remembering, and the times an agent helps me get an ambitious idea working. I want an honest record of the work, including the awkward parts between the idea and the launch.
How I am organizing the work
The Projects section is the current catalog. Each page says what the software does, where to open it, where its repository lives, and how the system works now. Those pages stay concise and change when the project changes.
Blog posts are the dated record. They hold the rationale, trade-offs, experiments, failures, technical details, and lessons that would make a project page harder to scan. A project can accumulate several posts. A finished artifact such as a video can live only in the blog when there is no separate public repository to maintain.
Each post declares its related projects once. Posts show those project cards, and project pages collect the related writing automatically.
How this blog was put together
Astro builds the Markdown and MDX into static pages using the minimal Astro Nano
interface. GitHub stores the writing, so I can edit it from a computer or
phone. A commit to main runs checks and tests in Cloudflare Workers Builds,
then deploys the static assets to jaimemguajardo.com.
Drafts stay out of production, and subscriber updates can only enter the mailing-list feed after a successful deployment and an explicit opt-in on the post.
The related Blog project card below documents the publishing flow, stack, repository, and safety boundaries.