4 Rules of simple Design - Runs all the tests - Contains no duplications - Expresses the intent of the programmers - Has no superfluous parts Sonntag, 9. Dezember 12
Ping-Pong Programming 1. A writes a new test and sees that it fails. 2. B implements the code needed to pass the test. 3. B writes the next test and sees that it fails. 4. A implements the code needed to pass the test. Sonntag, 9. Dezember 12
Taking Baby Steps 1. Setup a timer for 2 minutes interval when you start 2. Write exactly one test - If the timer rings and the test is red then revert and start over. - If the test is green before timer rings then commit 3. Restart timer 4. Refactor - If the timer rings and the refactoring is not complete then revert start over. - If the refactoring is complete before the timer rings then commit 5. Go to step 1 One important note: there can be no discussions in between timers, everything needs to happen within the timeboxes. Sonntag, 9. Dezember 12
Some Git Help Set up repository and working branch 1. in the console/terminal: go to your project folder 2.
git init → initialize origin/master branch 3.
do initial setup (adding references, building project structure, …) 4. commit How to commit 1.
git add . → track all the new files of the branch to version control 2.
git commit -a -m “commit message” → a = commit all changed files, m = message. The message cannot be missing or be empty. 3.
git status → to check if all changes were committed How to revert 1.
git reset –hard → revert to the last committed changes on the branch 2.
git status → to check if all changes were reverted Sonntag, 9. Dezember 12
Mute Evil Programmer - Ping-pong - one person writes the tests, the other person writes the implementation code - Mute - nobody can talk - Find the Loophole - the implementation person purposely writes the wrong algorithm that still makes the tests turn green. Sonntag, 9. Dezember 12
Object Calisthenics 1. Use only one level of indentation per method 2. Don’t use the else keyword 3. Wrap all primitives and strings 4. Use only one dot per line 5. Don’t abbreviate 6. Keep all entities small - 50 lines per class - 4 lines per method 7. Don’t use any classes with more than two instance variables 8. Use first-class collections 9. Don’t use any getters/setters/properties Sonntag, 9. Dezember 12
sebabenz
kojira
chiroito
yuj1osm
poteboy
akiroom
k1low
biwashi
cimadai
keiko713
is_ryo
shibuiwilliam
coconala_engineer
cherdarchuk
quramy
shlominoach
reverentgeek
sachag
malarkey
wjessup
erikaheidi
edds
csswizardry
palkan
colly