This page describes how content on Ebuhu is researched, written and corrected. It exists so you can judge for yourself how much weight to give what you read here.
What we publish and why
Ebuhu covers software development, PHP and AI-assisted coding. The aim of every article is to answer the question that brought you here, completely enough that you do not need to open five more tabs.
How articles are researched
We work from primary sources wherever a primary source exists. For a rule, that means the body that publishes the rule. For a specification, the manufacturer's own documentation. For a regulation, the regulator. For a study, the study, not a summary of it.
Sources are named in the article, not gestured at. If a figure appears here, you should be able to see where it came from and go and check it. That is the point.
When a figure cannot be verified, we say so rather than publishing it. Numbers circulate in every niche that trace back to nothing, a rounded estimate that became a statistic through repetition. Where we cannot establish where a number came from, we leave it out and explain the mechanism instead. An article that admits what it does not know is more useful than one that guesses confidently.
What we do not claim
We do not claim hands-on testing we have not done. Where an article discusses a product or a procedure, it is built from published specifications, documented behaviour and reasoning, not from a test bench, unless the article says otherwise and describes the test.
We do not publish invented experience. No fabricated anecdotes, no "when I tried this", no first-person account of something nobody here did.
Where the limits are
Every article that touches a subject with real consequences, health, money, safety, legal obligations, says plainly where the article stops and where a qualified professional starts. The Disclaimer covers this in more detail, and it is not boilerplate: it is specific to what this site writes about.
Corrections
If something here is wrong, we want to know, and we will fix it. Corrections are made to the article itself rather than buried, and where a correction changes the substance of what was said, the article notes that it was corrected.
You do not need to be an expert to report an error, and you do not need to be polite about it. A reader who says "this number looks wrong" is doing us a favour.
Updates
Subjects covered here change, rules are revised, products are discontinued, regulations are amended. Articles carry the date of the research behind them, and where a topic is known to move quickly, the article says so and tells you where the current position is published.
Last updated 2026-08-11.