Editorial policy
How articles are written, reviewed, and corrected.
A short, plain-language statement of how this site treats accuracy, sources, sponsorship, and corrections.
Independence
roman10.net is an independent technical blog. The site is not owned by any vendor, framework foundation, or platform holder. No article is written or revised in exchange for payment, equity, free hardware kept beyond a review, or any other form of consideration. Sponsored posts, paid reviews, and "link insertion" arrangements are declined as a matter of policy.
Authorship
Articles are written by working software engineers. Each article identifies its author. Guest contributors are credited the same way as regular contributors and held to the same standards. Anonymous and pseudonymous publishing is not the norm here, but is allowed in narrow circumstances when the author needs to discuss employer-related work safely.
Technical review
Before publication, every article is read by at least one engineer other than the author who has hands-on experience with the topic. Code samples are run; build instructions are exercised on a clean environment when feasible; commands listed in tutorials are executed verbatim and the output is checked against what the article claims. When something cannot be verified — for instance, behaviour on an old Android version no longer reachable — that limit is stated in the article.
Sources
Where an article relies on documentation, specifications, or external research, sources are linked inline. We prefer primary sources (RFCs, language specifications, vendor documentation, source code) over secondary ones. When a tutorial follows a recipe published elsewhere, that prior work is credited.
Updates
Software platforms move. Articles age. When a published article is invalidated by a platform change — a new Android API level, a removed FFmpeg flag, a deprecated Linux subsystem — the article is updated in place with a clear note at the top describing what changed and when. We do not silently rewrite history.
Corrections
If an article is wrong, the right move is to fix it. Send corrections to editor@roman10.net with the article URL, the passage at issue, and ideally a pointer to a source. Substantive corrections are acknowledged at the bottom of the article with a short note describing what was changed. Trivial corrections (typos, broken links) are made silently.
Comments and reader contributions
The site does not run an open comments section. Reader feedback is funneled through email so that it can be read carefully, integrated into the article when warranted, and credited. Drive-by remarks rarely improve a technical post.
Conflicts of interest
When an author writes about a tool, library, or platform that they are also professionally involved with — as a contributor, employee, advisor, or otherwise — that relationship is disclosed inside the article itself.
Affiliate links and reviews
See the Review Disclaimer for the specific policy on affiliate links and tool reviews. Short version: the site does not place affiliate-driven recommendations in editorial content.