Editorial guidelines
The standards Varcore articles are held to: accuracy, tested code, clear trade-offs, transparent corrections and labelled commercial content.
Last updated
Accuracy first
Claims about performance, behaviour or compatibility are based on documentation, source code or measurements we can reproduce. Where something is an opinion or an estimate, the article says so. Benchmarks state their setup and versions so readers can judge whether the results apply to them.
Code is run before it is published
Every code sample is executed against the versions named in the article. Samples favour clarity over cleverness and include enough context to be adapted, not just copied.
Trade-offs over verdicts
Comparisons ("X vs Y") explain what each option optimizes for and in which situations it loses. A recommendation is always attached to the constraints it assumes.
Corrections and updates
Errors are corrected in place as soon as they are verified, and the article's updated date changes. Substantive corrections are noted in the article. Articles that become obsolete are either updated or marked with a note at the top. URLs do not change after publication.
Sponsored content, advertising and affiliate links
Sponsored articles are labelled as sponsored at the top of the page. Affiliate links are disclosed in the article that contains them. Sponsors do not review or approve editorial articles, and no article's conclusions are for sale.
Use of AI tools
Writers may use AI assistants for research, drafting assistance and editing. Every published article is reviewed, fact-checked and edited by a person who takes responsibility for its content. We do not publish unreviewed generated text.
Attribution
Sources are linked. Quotations are attributed. Diagrams and images are our own, licensed, or used with permission and credited.
Feedback
Readers who spot a mistake or disagree with an analysis are encouraged to get in touch. Good-faith technical disagreement makes the publication better.