Work in progress — This wiki is an active migration / mirror of Homestar Runner Wiki and is not finished yet. Account registration and public editing are turned off until the migration is further along. For status updates, see the migration thread on the forums.

HRWiki Once And Only Once: Difference between revisions

From HR Wiki Twice
Jump to navigationJump to search
imported>HRWikiMirrorBot
Imported from hrwiki.org via Wayback Machine (HTML→wikitext)
 
imported>HRWikiMirrorBot
Reimported from hrwiki.org Wayback HTML→wikitext (full reconvert)
 
Line 1: Line 1:
<!-- Mirrored from Homestar Runner Wiki (hrwiki.org) via Wayback Machine; HTML converted to wikitext. Formatting may be imperfect. -->
<!-- Mirrored from Homestar Runner Wiki (hrwiki.org) via Wayback Machine -->
<div id="shortcut" style="border: 1px dashed blue; background: #FFF; margin: 0em 1em 0em 1em; text-align: center; padding:5px; float: right; clear: both;">
Shortcuts:


Shortcuts:<br />
HRW:OAOO
[[HRWiki:OAOO|HRW:OAOO]]<br />
[[HRWiki:ONCE|HRW:ONCE]]


</div>
HRW:ONCE
The principle of '''&quot;Once and Only Once&quot;''' originated in the world of programming, where it is considered foolish to do something twice that only needs to be done once. As it applies to a wiki, it means that you shouldn't duplicate any information or keep multiple copies of documents organized in different ways.
 
The principle of '''"Once and Only Once"''' originated in the world of programming, where it is considered foolish to do something twice that only needs to be done once. As it applies to a wiki, it means that you shouldn't duplicate any information or keep multiple copies of documents organized in different ways.


The violation of this principle can lead to many problems. These complications could include (but are certainly not limited to):
The violation of this principle can lead to many problems. These complications could include (but are certainly not limited to):
Line 15: Line 14:
* Responsibilities in our community become scattered, leading to documents that are difficult to understand.
* Responsibilities in our community become scattered, leading to documents that are difficult to understand.


It becomes immediately clear that none of these outcomes would be good for our wiki or our wiki community, therefore, we feel that the &quot;Once and Only Once&quot; principle should be adhered to as closely as possible.
It becomes immediately clear that none of these outcomes would be good for our wiki or our wiki community, therefore, we feel that the "Once and Only Once" principle should be adhered to as closely as possible.
 
[[Category:HRWiki Policy]]
<div id="catlinks" class="catlinks">
 
<div id="mw-normal-catlinks">
 
[/wiki/Special:Categories Category]: <span dir="ltr">[[Category:HRWiki Policy|HRWiki Policy]]</span>
 
</div>
 
</div>



Latest revision as of 14:24, 14 July 2026

Shortcuts:

HRW:OAOO

HRW:ONCE

The principle of "Once and Only Once" originated in the world of programming, where it is considered foolish to do something twice that only needs to be done once. As it applies to a wiki, it means that you shouldn't duplicate any information or keep multiple copies of documents organized in different ways.

The violation of this principle can lead to many problems. These complications could include (but are certainly not limited to):

  • One of the versions will soon be out of date, since it can be very difficult to remember to update them all. Worse, some wiki editors may not even be aware that the copies exist, and therefore won't realize that they need to edit the copy if they have edited the original.
  • We will have more to overcome when we want to change the format of or reason for the documents' existence.
  • Responsibilities in our community become scattered, leading to documents that are difficult to understand.

It becomes immediately clear that none of these outcomes would be good for our wiki or our wiki community, therefore, we feel that the "Once and Only Once" principle should be adhered to as closely as possible.