What is Developer.com’s Editorial Policy?
At Developer.com we have two goals:
- Create trust for our readers
- Provide the best possible answer to our reader’s questions
Whether we are answering the question: “What are the best tools to increase developer productivity” or “How do you perform multithreading in Python?”, we believe those two goals go hand-in-hand. Because of that, every product review and tutorial we publish follows the principle of “providing the best answer.” To do this, our team must understand two things: “what information is the user seeking?” and “what is the best answer?”
Our team relies on their subject matter expertise, industry awareness, continual research, and a rigorous editorial process to determine which questions our audience is asking, create content based on those questions, and then uses our combined knowledge and experience to deliver the best answers to those questions.
Developer.com is committed to editorial independence and objective assessment in the software and tools we review and recommend. We also partner with product vendors to make money.
Our readers’ trust is vitally important to us. When anyone reads a programming tutorial or software review on Developer.com, we want them to know they can trust that the article is accurate and objective, and the recommendations we make are based on the expertise and independent analysis of our subject matter experts and editorial staff — not just our partner affiliations.
How can we do that? We start by being transparent about how we make money.
Developer.com partners with companies that provide products and services that can be helpful to programmers, developers, web developers, database developers, and project managers of software development teams. We recommend tons of products on our site, from partners and non-partners, and we may earn commissions when our readers click on links leading to a vendor’s website. Commissions earned are used to grow our own business and help us continue to deliver the best possible answers to our readers’ questions.
Developer.com is committed to partnering with companies that provide the best tools and software in the software development and project management industry and that we believe meet our audience’s unique needs. In addition to making us money, we view this as a service: think of us as a store that answers a user’s questions regarding the best way to complete a project, and then provides recommendations on the tools you might need to accomplish those goals.
Editorial independence means that our editorial staff and writers are free to provide information and recommendation free from the input or guidance of our partners. This editorial independence allows us to list both the pros <i>and</i> cons of software and tools without feeling pressure from our partners to display them “in the best light”. We believe a user has the right to know the advantages and disadvantages of a tool, and, as such, editorial independence is key to our reviews being as transparent and honest as possible.
The recommendations in our reviews and product roundups are made independently, with no influence from our partners or non-partners. Our reviews and suggestions are based on research and our writers’ expert assessments of the software and tools they are evaluating, and nothing more. While we partner with many great companies, those partnerships have no bearing on our software and tool recommendations.
During our review process, our subject matter experts evaluate our partners’ products to determine if they are a good fit for our readers. That being said, reviews featuring our partners’ products are held to the same standards as non-partner product reviews. Any software or tool recommendation is based solely on the product’s merit as determined by the writer (subject matter expert) and editor.
Plagiarism and Duplicate Content Policy
Developer.com does not tolerate plagiarism in any form. The copying of other people’s work and/or ideas is not permitted and our editorial team use tools and techniques to determine if work has been plagiarized or published elsewhere. We have a zero tolerance policy when it comes to plagiarism; if a writer’s work is found to be a copy of someone else’s work, or a duplicate of someone else’s writing, that writer will be terminated.
Developer.com also does not allow a writer’s work to be reused on another website or publish, in part or in whole.
Each and every day, thousands of visitors trust us to provide the best answers to their questions, whether that be a programming language’s syntax or best practices, or a software review for an integrated development environment (IDE) or collaboration tool. Our readers rely on our answers to make informed decisions when purchasing software and tools and to answer business-critical questions related to software development. Our work is based on building trust with our readers through editorial independence and transparency and relying on the combined efforts of our editorial stuff, writers, and subject matter experts to deliver the best answers to our readers’ questions.