DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

What Is Plagiarism? How to Avoid It and Cite Sources

When it comes to plagiarizing, we only have one thing to say: don't.

Lindsay Smith user avatar by
Lindsay Smith
·
May. 03, 19 · Tutorial
Like (19)
Save
Tweet
Share
27.63K Views

Join the DZone community and get the full member experience.

Join For Free

Plagiarism, as defined by the Oxford English Dictionary, is “the action or practice of taking someone else's work, idea, etc., and passing it off as one's own.”

This includes copying and pasting text from other sources and inserting them into your own work, or even just rewording text from another source. Anything that does not reflect your own thoughts or ideas, with incorrect attributions, or a lack thereof, is an act of plagiarism.

There are also less obvious forms of plagiarism. In an article covering common forms of plagiarism, Bowdoin University provided an example of indirect plagiarism:

Original Source Student Writer
"Contrast the condition into which all these friendly Indians are suddenly plunged now, with their conditions two years previous..."
"Only two years later, all these friendly Sioux were suddenly plunged into new conditions."


While this does not directly copy text from the source, it does provide an almost identical explanation with similar wording. Instead of "friendly Sioux were suddenly plunged into new conditions," the author could have summarized the text, saying: "the Sioux tribe, a group of amiable individuals, found themselves in uncharted territory."

This effectively communicates the information from the source, but in a new and original way. The key here is that the phrasing is all your own.

Additionally, taking a quote and using a thesaurus, so the words are not identical, is also an act of plagiarism. Discover Magazine wrote an article titled, "Copy, Paste, Thesaurus?" where they show specific examples of this:

ORIGINAL THESAURUS VERSION

Lore perpetuates the myth of innovation as a solitary act, a flash of creative insight, an Aha! moment in the mind of a genius. People apparently prefer to believe in the rugged individualism of discovery, perhaps because they rarely get to see the sausage-making process behind every breakthrough innovation.

Three decades of research has clearly revealed that innovation is most often a group effort. Thomas Edison, for example, is remembered as probably the greatest American inventor of the early twentieth century. From his fertile mind came the light bulb and the phonograph, along with more than a thousand other patented inventions over a sixty-year career. But he hardly worked alone.

Wisdom perpetuates the legend of modernism as a private act, a spark of originality imminent, an Aha! Instant in the brain of a mastermind. People in fact favor to consider in the rough individuality of detection, possibly since they hardly ever get to see the sausage-making process behind every get through modernism.

Three decades of investigate has obviously exposed that modernism is most often a group attempt. Thomas Edison, for example, is remembered as almost certainly the most American discoverer of the untimely 20th century. From his productive intelligence came the brightest bulb and the turntable, along with additional than a thousand further untested inventions over a sixty-year vocation. However, he only just worked by yourself.


In the example from Discover, you see that while the text is different, this is not an original piece of writing by any means. 

How Can You Avoid Plagiarizing?

Now that we've defined plagiarism, let's take a look at some ways to avoid it.

Avoiding plagiarism is easy; you simply inform the reader of where you found your information. That's it. As shown above, I found my definition of plagiarism on the Oxford English Dictionary's website. I provided the exact source and used the insert link option, which is highlighted in blue in the image below. 

Image title

Super easy.

While DZone doesn't require authors to use internal citations within their article, we do ask that any direct quotes reference the original source via a URL link. For example:

According to Brian Goetz's book Java Concurrency in Practice, "It is far easier to design a class to be thread-safe than to retrofit it for thread safety later."

You can also provide references to sources further down the page, as long as the sources are not directly quoted. This is especially handy if your source is not available online, like a book, talk, etc. It could look something like this:

References:

  • Brian Goetz's Java Concurrency in Practice

  • Bert Bates and Kathy Sierra's Head-First Java

Why Does Attribution Matter?

Plagiarism is theft. And it's not cool. At DZone, we take pride in our authors. We never want to publish someone else's hard work without the proper citations. DZone is all about creating a collaborative, learning community for developers. So we need to make sure we are all giving credit where credit is due. 

We hope this short guide helps you in your writing process. If you have any further questions about plagiarism, or how to properly reference sources on DZone, please feel free to drop a comment below or email us at editors@dzone.com.

article writing

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Key Considerations When Implementing Virtual Kubernetes Clusters
  • Visual Network Mapping Your K8s Clusters To Assess Performance
  • PostgreSQL: Bulk Loading Data With Node.js and Sequelize
  • Top Five Tools for AI-based Test Automation

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: