Skip to content
View ashburn2k's full-sized avatar
  • Lawrence Berkeley National Laboratory
  • Berkeley, CA
  • 14:09 (UTC -12:00)

Block or report ashburn2k

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ashburn2k/README.md

Hui Zhang

Automation-heavy Local-first Private-work aware macOS Profile views

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.

Current Focus

  • 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

Tools I Use

Agentic development

Codex OpenAI GitHub GitHub Actions

Languages and scripting

Python TypeScript JavaScript Swift PHP Bash SQL

Platforms and systems

Node.js React WordPress Docker SQLite Homebrew

Writing and project memory

Markdown Obsidian Git

Skills

Automation design Workflow orchestration Agent tooling API integration Data pipelines Dashboarding WordPress systems macOS development Documentation systems Debugging

  • 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

Public Work

Project Notes
codex-usage Codex usage dashboard adapted from a Claude usage tracker
ashburn2k This profile repository

Private Work

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.

How I Like To Build

  • 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

Pinned Loading

  1. ashburn2k ashburn2k Public