https://labviewwiki.org/w/index.php?action=history&feed=atom&title=Common_Programming_PrinciplesCommon Programming Principles - Revision history2026-05-09T13:00:04ZRevision history for this page on the wikiMediaWiki 1.43.0https://labviewwiki.org/w/index.php?title=Common_Programming_Principles&diff=31060&oldid=prevQ: Started page2021-03-15T00:03:04Z<p>Started page</p>
<p><b>New page</b></p><div>{{underconstruction}}<br />
A simple internet search for '''Programming Principles''' will return many articles. Below is a list of '''Common Programming Principles''' that appear on multiple lists.<br />
{{TOCright}}<br />
== Keep It Simple, Stupid (KISS) ==<br />
Keep the code simple. Simple code is easier to read, extend, and maintain. If the code is simple, other developers, or "future you", will be able to understand the code logic and be able to continue with the code. <br />
# Attempt to split complex code into smaller components by using [[SubVI]]s<br />
# Remove unnecessary code<br />
# Don't try to write clever code<br />
<br />
== Write DRY Code ==<br />
The '''Don't Repeat Yourself (DRY)''' principle means to avoid duplication of code. This also pertains to data or logic. <br />
# Use [[SubVI]]s for logic used in many places<br />
# Don't duplicate/copy data storage. Inevitably, one of the copies will be out-of-date or wrong.<br />
<br />
== Open/Closed ==<br />
Make the code '''Open''' to extension but '''Closed''' to modification. Organize the code in such a way that it encourages extension but prevents direct modification. This separates core behavior from modified behavior so that if the core behavior is changed, it won't break the extended, modified behavior.<br />
#<br />
<br />
== You Aren't Going to Need It (YAGNI) ==<br />
<br />
== Document Your Code ==<br />
<br />
== Refactor ==<br />
<br />
== Low Coupling, High Cohesion ==<br />
<br />
[[Category:Programming Principles]]</div>Q