-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lesson 7 Feedback #7
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@amelinagzz - Feedback on OOP
OOP: Instead of "attributes" say "properties" so that we're consistent with where they hear it elsewhere. Unless this is Swift nomenclature, in which case, say that attributes are the equivalent of properties in Swift. Same question/suggestion applies to "instance variables"
Creating an Instance: Make sure to explain that the
Person()
call is the actual instantiation.let eddy =
is just assignment, and NOT part of instantiation. This was a big point of confusion in CS 1.1 in Term 1, so would be good to double down and drill in that point hereSuper: Be clear that it calls the super-class method and then ALSO does the code below it in the function
Required / Convenience Initializers: provide more explanation to what these are and how we'd use them
Managing a Hotel - I'm curious how this activity went. Did students need lots of help/further explanation? If so we should make the instructions clearer. Secondly, I would make sure you dedicate time to go over the answer to the activity. Don't need to include it in your slides, but go over it during class to make sure everyone understands the application of the concepts.
The text was updated successfully, but these errors were encountered: