Contact
This site is written and run by one developer, and email reaches that person directly. Messages are answered on a best-effort basis, usually within a few days.
Reports, requests, and policy questions all go to the same address.
Prefer GitHub? Open an issue or a discussion at github.com/rshday.
Guide corrections
A wrong example, output that does not match, an out-of-date version, or a typo. Include the guide URL and what you expected instead — a failing snippet or a link to the current documentation is the fastest way to get it fixed.
Topic and tool requests
A syntax topic that is missing, or a small browser utility that would save you time. Naming the language, the method, and the situation that made you look for it helps prioritise it.
Copyright and policy
Questions about reuse, attribution, the privacy policy, advertising, or a takedown request. Rights holders should include the material and the claim, and it will be reviewed promptly.
Before you write
Many reported tool problems turn out to be input that is not quite valid, such as JSON with a trailing comma, an expired token, or a cron expression with five fields where six were expected. Check the reference section on the tool page first; if the answer is still missing, that gap is worth reporting too.