Skip to content
View tzh476's full-sized avatar

Block or report tzh476

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.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. 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
tzh476/README.md

Stephen Smith / tzh476

Independent engineer available for small, bounded remote projects.

Engineering evidence / project resume

Technical writing samples

Digital product

Cash-First Opportunity Scorecard — USD 29 via PayPal. A 15-minute scorecard for deciding whether a bounty, paid writing call, or fixed-price gig is actually worth starting. Advertised prizes are not income.

Available for one new bounded milestone. The fastest starting point is a USD 300 diagnosis-and-fix milestone: reproduce one backend, API, automation, or data-pipeline defect; deliver the smallest verified correction; add a regression test; and provide a concise handoff. Scope and payment terms are agreed in writing before work begins.

Open a structured milestone request or request a scoped estimate by email.

Good first milestones

Scope Typical fixed range
Deploy a Codex-built MVP with a verified staging URL and runbook USD 300–900
Reproduce and fix a backend or data-pipeline bug, with regression tests USD 300–600
Integrate an API, LLM agent, RAG, or MCP workflow USD 500–900
Stabilize a Python, TypeScript, or Go automation pipeline USD 400–900

The exact price is agreed from a written scope before work starts. A first milestone should have explicit inputs, acceptance criteria, and a reproducible verification path. I can work asynchronously and disclose any AI-assisted tooling used during delivery.

For deployment work, the first milestone can cover diagnosis, corrected build and runtime configuration, a staging deployment, health and smoke checks, and a rollback/runbook handoff. Production access and infrastructure charges are not required for the initial diagnosis.

Working style

  • Source-grounded diagnosis before implementation
  • Small diffs, automated tests, and explicit failure handling
  • No production secrets or customer data needed for an initial milestone
  • Clear distinction between verified results, assumptions, and limitations

Public repositories below show work across Python, TypeScript, Go, C/C++, data systems, automation, model tooling, and infrastructure.

For a scoped inquiry, use the structured request or email link above, or contact tzh476@gmail.com. Include the repository or system, desired outcome, available fixtures, deadline, and budget range. Do not send passwords, tokens, private keys, or regulated personal data.

Pinned Loading

  1. zvm zvm Public

    Java 实现 JVM

    Java 249 55

  2. nju-os nju-os Public

    1

  3. innodb-viewer innodb-viewer Public

    Java 6

  4. os-workbench-2022 os-workbench-2022 Public

    Forked from NJU-ProjectN/os-workbench-2022

    Makefile