The fastest way to reach the author is by email. Please use the address below and a brief subject line that describes the topic of the message.
What I respond to
- Corrections. If an article contains a factual error, a broken code sample, an incorrect citation, or a misleading claim, a short message identifying the article and the issue is the most useful kind of feedback I receive.
- Clarifying questions about a post. If something in an article is unclear or could be explained better, please write. Many improvements to existing posts have come from reader questions.
- Topic suggestions. If there is a topic you would find useful, write briefly about the problem you are trying to solve. I do not promise to write every requested topic, but reader requests influence the publication schedule.
- Working-engineer questions about implementation. If you are working through a problem related to one of the topics covered on this site, a concise question with the relevant context tends to produce a useful reply.
Response time
I read every message and try to reply within a few working days. Replies to lengthy or research-style questions can take longer, particularly when verification or testing is required. If a message has gone unanswered for two weeks, a polite follow-up is welcomed — it occasionally helps the message get the attention it deserves.
What I do not respond to
- Requests for personalised financial, legal, medical, or other professional advice. The site does not publish content in those areas, and I am not qualified to advise on them.
- Unsolicited sales pitches, paid-link or guest-post requests, or affiliate-marketing proposals.
- Requests to remove articles or change article conclusions in exchange for payment.
- Generic mass emails sent without reading the site.
Editorial process
For details on how content is researched, written, fact-checked, and updated, please see the Editorial Standards page. The About page describes the author and the scope of the publication.
Privacy
For information on how visitor data is handled, please see the Privacy Policy.
Last updated: June 2026.