Review disclaimer
How tool, book, and platform reviews are handled.
The ground rules for any review-style article on this site, so readers know exactly what they are reading.
What this disclaimer covers
Articles on roman10.net occasionally evaluate developer tools, books, libraries, frameworks, IDEs, programming languages, build systems, and online platforms. This page describes the rules that apply whenever a piece can be read as an evaluation rather than purely a tutorial.
Independence
Reviews and recommendations published here are not influenced by affiliate rewards, vendor relationships, sponsored placement, or any other form of consideration. Publishers may send books or vendors may grant free trial licenses for products under review; that fact does not alter the editorial conclusions. When a copy or trial has been provided, the article says so explicitly.
No paid placements
We do not accept payment in exchange for positive coverage, the placement of a tool inside a tutorial, or the insertion of a link into an existing article. Outreach asking for any of these things is declined. We do not run a "best-of" affiliate funnel — articles that compare tools do so on technical merit and the bias of the author's own experience.
Affiliate links
The site does not depend on affiliate revenue. Where an external link is included in editorial content, it is included because the link is genuinely useful to the reader. Should an affiliate or referral parameter ever appear on a link in editorial content, that fact will be disclosed inline. Routine technical references (e.g., to documentation, RFCs, source repositories) never carry affiliate parameters.
Conflicts of interest
When an author has a professional relationship to a tool or platform they are reviewing — as a contributor, employee, former employee, advisor, or competitor — that relationship is disclosed inside the article. We err on the side of over-disclosing rather than under-disclosing.
Negative reviews
Critical commentary about a tool or library is allowed and protected by the editorial policy. Vendor pressure to remove or soften an article's conclusions is not entertained. Substantive technical rebuttals — the kind that include reproducible counter-evidence — are taken seriously and may lead to corrections, updates, or follow-up articles.
Out of date
Tools change. A negative review of an old version may not reflect the current state of the project, and vice versa. When a tool is re-evaluated and the conclusion changes, an update note is added to the original article and a new article is published rather than retroactively rewriting the old one.
Questions
If a published article appears to violate any of the above, please email editor@roman10.net. Verifiable concerns are taken seriously and acted on quickly.