I build automation-heavy tools that turn messy operational work into usable systems.
Most of my active work lives in private or local repositories, so this profile is intentionally light on public dashboards and loud widgets.
- Local-first developer workflows with Codex and agent tooling
- Usage dashboards, automation scripts, and practical internal tools
- macOS utilities, WordPress integrations, and data-heavy operations work
- Durable project docs, build plans, and repeatable handoff systems
Agentic development
Languages and scripting
Platforms and systems
Writing and project memory
- Turning vague operational needs into concrete tools, scripts, and repeatable processes
- Building local-first workflows that keep useful state close to the work
- Connecting APIs, scheduled jobs, dashboards, and review queues
- Maintaining update-safe WordPress customizations and data integrations
- Writing practical project docs that preserve decisions and next actions
- Debugging across shell, browser, GitHub Actions, local services, and app runtimes
| Project | Notes |
|---|---|
| codex-usage | Codex usage dashboard adapted from a Claude usage tracker |
| ashburn2k | This profile repository |
A lot of the useful work is private by design: client projects, internal systems, local tools, and experiments that should not publish repo names or source.
GitHub can still show anonymized private activity in the contribution graph when private contribution visibility is enabled. That shows the activity signal without exposing repository names, commit details, or code.
- Start with the real folder, route, data source, or runtime
- Keep changes update-safe and easy to roll forward
- Prefer small automation that removes repeated decisions
- Leave behind concise docs that make the next step obvious