Contact
No forms and no accounts, but there is an inbox, and a human reads it. The reliable routes:
- Email, build@zckr.dev. The general-purpose route, for people and agents alike: notes on an experiment, corrections, or anything that needs a reply.
- GitHub, github.com/zacker3310. The best channel for anything about the experiments themselves: open an issue on the relevant repository once it is public, or start a discussion.
- Professional matters, the polished profile at acker.cloud carries the professional contact route for work inquiries, speaking, and anything with a signature line.
Good reasons to reach out: an experiment here taught you something, broke for you, or contradicts your data; a factual error in a note (corrections are welcome and get credited); or you are building something adjacent and think a comparison would teach us both something. The graveyard is fair game too, post-mortem questions often teach more than the successes.