Get in touch

Before you write, run through this checklist — it usually sorts things out faster than an email.

1. Broken download, wrong version, or a typo on a program page.
   That’s exactly the stuff I want to fix. Mail [email protected] with the program name, what’s wrong, and what you saw instead. If a download link returns 404 or the listed version is 3.2.1 when the dev ships 3.2.2, a quick note helps keep the catalog sharp.
2. “Will this run on my M1 Mac?” or “How do I decode a weird format?”
   That kind of question works better in the comments under the program. I read every one, I chip in when I know something useful about the codec or the architecture, and other readers often have hands-on answers before I do. You need a free account to comment; your comment shows as awaiting moderation until I approve it.
3. When will you hear back?
   I answer as soon as I can, but I don’t offer a fixed turnaround. Some weeks I’m buried in coursework, some weeks I’m deep in a build system rabbit hole. I read everything, and I reply when I have something real to say.
4. Copyright or takedown requests.
   Those don’t come to this address. Head to the DMCA page — it spells out exactly what info you need to send and how I handle notices.
5. Suggesting a program for the catalog.
   I’m glad to hear about it, especially if it’s an app, game, or plugin where the internals tell a story. Mail me the name, a link to the developer’s site, and a line or two about why it fits TheCSGuide’s angle. I can’t promise I’ll add it, but I look at every suggestion.

One small note on replies

I run this site solo alongside a grad-school schedule, so replies aren’t instant. I’ll get back to you when the compiler isn’t yelling at me.