The opentaps Way of Coding

From Opentaps Wiki
Revision as of 22:35, 21 February 2011 by Sichen (talk | contribs) (New page: __TOC__ ==Why the opentaps Way of Coding== Writing code is easy. Maintaining that code through its entire lifecycle is much, much more complicated. We are always thinking of how to c...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Why the opentaps Way of Coding

Writing code is easy.

Maintaining that code through its entire lifecycle is much, much more complicated.

We are always thinking of how to create code that is easy to maintain and extend. Over time, we have developed a distinctly "opentaps Way of Coding" to help maintain your customizations through multiple versions of opentaps. Our goal is to give you a way to separate your code, whether it's customizations to the base system or enhancements on top of it, cleanly and to keep your code compatible with future versions as they are released.

The opentaps Way follows these principles:

  • Segregate your code
  • Use the compiler to maintain your code