How we research and write

The blog covers the same ground as our work: websites and software, AI and automation, hosting, search, IT support, security, integrations, cloud and data. Each article starts from a question readers bring to a search engine, and answers it before it goes into detail.

Facts come from the source that owns them: the standard itself, the vendor's documentation, the regulator's page or the study, rather than a summary of it. We open every source we cite. A claim we cannot check at its source does not go in.

Each claim links its source in the sentence where it is made, and every article lists all of its sources at the end, with the publisher. The links go to the publisher's current page, because standards and product documentation change.

Figures carry their source, and the version or date they describe. When an article covers a product or a standard that changes, it says which version it describes, so a reader can tell whether it still applies.

We never name clients. Examples from our own work name the industry and the technology, never the company. We do not invent statistics, quotes or testimonials, and where something is uncertain or still changing, the article says so.

The illustrations are made for each article, to explain the paragraph beside them. They are diagrams of how something works, not photographs of real people, products or events.

Every article shows when it was first published and when it was last revised. The revision date changes when what the article says changes, not for a typo.

If you find an error, email support@computese.com with the article's address. We check it against the source, correct the article and update its revision date.

Articles are published by Computese under the name of Duong Quan Nguyen, our CEO.