What makes CREATE SOMETHING different from AI blogs: we don't just document results—we document the process of building with AI agents.
Every experiment is tracked with automated logging, real costs from APIs, precise time measurements, and intervention documentation. This transforms anecdotes into reproducible experiments.
Work with AI agents as development partners
Hooks capture every prompt, error, intervention
Actual costs, time, errors from APIs
What worked, what didn't, and why
This is research, not blogging.
Real-time logging via Claude Code hooks
47 iterations loggedPrecise counts & resolution times
23 errors, avg fix: 8 minToken usage + infrastructure from APIs
$18.50 Claude + $8.30 CloudflareWhen AI needed human help, and why
12 manual fixes documentedSession duration, not guesswork
26 hours actual vs 120 estimatedDecisions made, alternatives considered
Workflows over Workers (why)Start tracking from day one. Get complete data on every iteration, error, and decision.
High confidence, precise metrics
New experiments starting from scratch
Start tracking on an in-progress project. Combine real-time data with git history reconstruction.
Mixed: estimates for past work, precise for future
Active projects you realize are experiment-worthy
Document already-deployed projects. Reconstruct from git, APIs, and memory.
Lower confidence, acknowledged limitations
Completed projects with production data
The tracking methodology transforms "prompting and hoping" into systematic evaluation with reproducible results. This is what separates research from blogging.
Want to adopt this approach for your own AI-native development research? The experiment tracking system is available as a Claude Code Skill.
Add experiment tracking to your Claude Code setup
Work with Claude Code while automatic logging captures everything
Transform tracked data into reproducible research
Example from Experiment #1: Zoom Transcript Automation
Data sources: Real-time prompt logging via hooks, Claude Code Analytics API, Cloudflare billing API, git commit history
Reproducibility: Starting prompt, tracking logs, and architecture decisions documented