David's Commandments: Difference between revisions
Jump to navigation
Jump to search
Created page with "* Thou shalt honor thy commitments. To thine own self, to David, and to others. If you agree to do something, do it or renegotiate the commitment. Don't miss meetings. Kee..." |
m Typo fix... is it blasphemy to correct the word of D-H-L? |
||
| Line 1: | Line 1: | ||
* Thou shalt honor thy commitments. To thine own self, to David, and to others. If you agree to do something, do it or renegotiate the commitment. Don't miss meetings. Keep your travel plans up to date in dhlgroup google calendar. | * Thou shalt honor thy commitments. To thine own self, to David, and to others. If you agree to do something, do it or renegotiate the commitment. Don't miss meetings. Keep your travel plans up to date in dhlgroup google calendar. | ||
* Thou shalt honor thy e-mail. Respond promptly. | * Thou shalt honor thy e-mail. Respond promptly. | ||
* Thou shalt | * Thou shalt keep thine work accessible. Publication source goes in /pro/graphics/papers. Grant proposal source in /pro/graphics/proposals. Bodies of data go in /research/data/graphics or /data/graphics. Code goes in the group's source control repository. | ||
* Thou shalt commit early and often. All code, experimental or not, should be in the group's source control repository. Commit changes often. But don't break the build. | * Thou shalt commit early and often. All code, experimental or not, should be in the group's source control repository. Commit changes often. But don't break the build. | ||
* Thou shalt test thine code. Any code that others depend on should be a part of the overnight regression testing process and should have a test sufficient to catch likely bugs. | * Thou shalt test thine code. Any code that others depend on should be a part of the overnight regression testing process and should have a test sufficient to catch likely bugs. | ||
* Thou shalt avoid copying code in place of branching in source control. Source control is explicitly for managing multiple versions of evolving code. Use it, don't make multiple copies other ways -- they are much more difficult to manage. | * Thou shalt avoid copying code in place of branching in source control. Source control is explicitly for managing multiple versions of evolving code. Use it, don't make multiple copies other ways -- they are much more difficult to manage. | ||
Latest revision as of 22:30, 14 February 2012
- Thou shalt honor thy commitments. To thine own self, to David, and to others. If you agree to do something, do it or renegotiate the commitment. Don't miss meetings. Keep your travel plans up to date in dhlgroup google calendar.
- Thou shalt honor thy e-mail. Respond promptly.
- Thou shalt keep thine work accessible. Publication source goes in /pro/graphics/papers. Grant proposal source in /pro/graphics/proposals. Bodies of data go in /research/data/graphics or /data/graphics. Code goes in the group's source control repository.
- Thou shalt commit early and often. All code, experimental or not, should be in the group's source control repository. Commit changes often. But don't break the build.
- Thou shalt test thine code. Any code that others depend on should be a part of the overnight regression testing process and should have a test sufficient to catch likely bugs.
- Thou shalt avoid copying code in place of branching in source control. Source control is explicitly for managing multiple versions of evolving code. Use it, don't make multiple copies other ways -- they are much more difficult to manage.