Editorial Policy
This page explains how I write and maintain the posts on this site, so you can judge how far to rely on them.
Who writes here
Most posts are written by me, Richard Djarbeng, a software and machine learning engineer with an MSc in Electrical and Computer Engineering from Carnegie Mellon University. I am a Research Associate at the Kigali Collaborative Research Center (since October 2026). Before that, as a Research Associate at Carnegie Mellon University Africa, I worked on the design of low-cost weather and air quality sensors deployed in East Africa, which is where most of the environmental posts come from. A few posts are written by guest authors, and each one is credited on the post and listed on the authors page.
Sources
- Factual claims, figures and quotes link to their source, preferably the primary one: the paper, the dataset, the standard or the official announcement.
- When a post is based on my own work or measurements, it says so.
- Opinion is written as opinion. Posts that review or explain a paper link to the paper itself.
Older posts do not all meet this standard yet. I am going back through them, starting with the ones people read and link to most.
Use of AI tools
AI tools are part of how this site is made. I use them for research, editing, code, diagrams, cover images, gallery captions and sometimes first drafts, usually with my own notes and context as the starting point. I decide what gets published, and I am responsible for what it says. If something an AI tool helped produce is wrong, that is my error to fix.
Some posts carry an "AI assistance" note under the title describing how AI was used. I add these where I can, but not every page has one, especially older posts and gallery items, so assume AI may have been involved anywhere on the site.
Updates
Posts show the date they were first published and, when they have been changed since, the date they were last edited. That date comes from the site's version history, which is public on GitHub, so you can see exactly what changed and when.
Fast-moving topics, such as AI models, prices and policies, can go out of date. Check the date before relying on a figure.
Corrections
When an error is reported or I find one, I fix it as quickly as I can.
- Small fixes, such as typos and broken links, are made without a note.
- Corrections to facts, figures or code that readers may have relied on get a dated note on the post saying what was wrong and what changed. When a reader reported the problem, the note thanks them unless they would rather not be named.
An example is the reader note on the Eleventy guide, added after a reader reported a broken code example.
Independence
I do not accept payment for posts or reviews. If that ever changes, or if I have a personal or financial connection to something I write about, the post will say so. Product links are not affiliate links unless the post says otherwise.
Report an error
- Open an issue on GitHub, or
- use the contact form.
Please include the page and what you think is wrong. Thank you; this is how the site gets better.