Contact

Have a question, found an error, or want to say hello? Use the form below. I read every message, though a reply can take a few days.

    What helps me answer

    If you are writing about a specific tutorial, say which one and what you actually ran. The command, the output you got, and the version of the tool are usually enough for me to reproduce it. Without those it normally takes two or three exchanges before the question is even answerable.

    Corrections and topic requests

    Corrections are genuinely welcome. Several guides here have been rewritten because a reader pointed out that a flag had changed or a command no longer behaved the way it did when the tutorial was written. Tooling in this space moves fast enough that published steps go stale, and I would rather hear about it than leave it wrong.

    For topic requests, describing what you are trying to build is more useful than naming a tool. It tends to produce a guide that answers the real question rather than one that just lists options.

    You may not need to write

    A lot of what gets asked is already covered. The Claude Code, OpenAI, AI Agents, AWS & Cloud and System Design sections are the place to start, and each tutorial ends with its own FAQ.

    What happens to your message

    Messages reach me directly and are not shared, sold, or added to a mailing list. There is no newsletter here to subscribe you to. See the privacy policy for what is stored and for how long.