Contact

If you’d like to reach me about anything on this blog — corrections, collaboration, feedback, or something else — the channels below are the best way. I usually reply within 1–2 business days.

Email

My everyday working email:

• geraldchen890806@gmail.com

Good for:

• Article corrections and factual fixes
• Technical collaboration invitations
• Business inquiries
• Media and interview requests
• Content licensing requests

To help me triage quickly, please put the topic type in the subject line, e.g. “[Correction] About X in blog158” or “[Collaboration] Invitation regarding Y”.

Social Media

For day-to-day technical exchange and quick conversations:

• GitHub: @geraldchen890806 — code discussions, issue reports, follow my projects
• X (Twitter): @geraldchen89 — where new articles are announced first, plus tech discussions and quick feedback

What This Page Is Good For

Content Feedback

• Factual errors in articles or code samples that don’t run
• Technical descriptions that contradict official documentation
• Suggestions for important updates worth adding

When I receive this kind of feedback, I add a correction note to the original article with a visible revision date, and for significant errata I’ll let the original reporter know.

Technical Collaboration

• Co-authoring technical articles
• Open-source collaboration
• Internal sharing sessions or talk invitations
• Consulting in AI agents / frontend engineering

Content Licensing

Articles on this blog are published under Creative Commons 4.0 (Attribution-NonCommercial-ShareAlike) by default. For:

• Commercial publishing (books, paid courses)
• Internal corporate training material
• Any other use outside the default license

please reach out by email to discuss licensing — in most cases I’m happy to work something out.

What I Won’t Take On

To keep my focus on the blog itself, these kinds of requests generally won’t be processed:

• “Mentor me” or referral requests — I’m not at a big company and have no internal referral channels
• One-on-one paid technical consulting — limited bandwidth, though I can point you to professional alternatives
• Sponsored/advertorial placements — this blog doesn’t sell ad slots
• Publishing AI-generated content on someone’s behalf — declined; I take authorship responsibility for everything published here

Response Times

• Weekday email: usually within 1–2 business days
• GitHub issues: for projects I maintain, usually within 24 hours
• X DMs: checked irregularly — use email for anything urgent
• Public holidays and personal time off: replies may take up to a week

If you haven’t heard back within a week, feel free to send a reminder — your email may have been caught by the spam filter.

Privacy Note

Anything you send me via email, GitHub, or X DMs will be:

• Used only to respond to the specific matter you raised
• Never shared with third parties
• Never used for marketing or promotion

See the full Privacy Policy for details on data handling.