Contact

Found a mistake, an outdated command, or an explanation that didn't make sense? Want a topic covered? I'd like to hear about it — reader reports are how these tutorials get better.

Email

Email is the best way to reach me. I read every message and reply to most within a few days.

hello@shellrag.com

Making a report useful

Errors in a tutorial

Include the page URL, the command you ran, the output you got, and your OS and tool version (for example bash --version). Fixes are re-tested before they go live.

Topic requests

Tell me what you were trying to do and where you got stuck. Requests that fit an existing learning path are the most likely to be written.

Site problems

Broken links, pages that don't render, or layout problems on your device — include the browser and device you used.

Help with your own scripts

I can't debug individual projects, but if a tutorial didn't cover your situation, that is useful to know.

Learning paths