Content deleted Content added
→Continuous integration: wikilink |
→Shared understanding: new subsection: Self-documenting code |
||
Line 153:
=== System metaphor ===
The system metaphor is a story that everyone - customers, programmers, and managers - can tell about how the system works. It's a naming concept for classes and methods that should make it easy for a team member to guess the functionality of a particular class/method, from its name only. For example a library system may create loan_records(class) for borrowers(class), and if the item were to become overdue it may perform a make_overdue operation on a catalogue (class). For each class or operation the functionality is obvious to the entire team.
=== Self-documenting code ===
Extreme Programming backers advocate code that is [[self-documenting]] to the furthest degree possible. This reduces the need for [[Comment (computer programming)|code comments]], which can get out of sync with the code itself.<ref>http://guzdial.cc.gatech.edu/squeakbook/new-lecture-slides/xp.ppt</ref>
==Programmer welfare==
| |||