-
Notifications
You must be signed in to change notification settings - Fork 4
TA Feedback Feb 26 meeting
James Devito edited this page Feb 26, 2015
·
2 revisions
In the future the main rule,
Before we work on things in the assignment ask Alex if we are skipping anything
EX: from part 2: Everything we did was good but didn't go over and check everything (missing parts)
In issues Alex thinks we can link him in git issues ie: @alex...
Part 3: UML again with asking alex, Before we go and don't do something ask alex
UML was missing - Some comments, Some activities (server saving), primitive obsession
Consider changing design a bit to extract some example(make a currency class similar to claimstatus)
was happy with addressing feedback
look at the rubric
Overrall good work but be more thorough