This intro to OOP is ... far too rudimentary. And the examples aren't parallel.
Maybe discuss language hierarchy?
Discuss Smalltalk in more detail?
Introduce the idea of abstraction, necessary for human thought, but which doesn't actually translate to the code.
Hey! Let's avoid any similitude to the examples from Learning iOS Development! (Don't use cars).
Also, let's avoid subtly insulting groups of people in the example using humans and zombies!
Hey! Let's avoid ridiculously verbose method names in the examples!
What is the linter?
Relate class objects : instance objects :: printing die : printed paper. Much better metaphor, or blueprint and house. If the class object is an object, what's the value in creating an instance? Set up the problem.
Let's wait to discuss custom initializers until the next unit which already includes it.
The reading doesn't really follow its title-topic. Should this stick to a discussion of OOP?
This intro to OOP is ... far too rudimentary. And the examples aren't parallel.
Maybe discuss language hierarchy? Discuss Smalltalk in more detail? Introduce the idea of abstraction, necessary for human thought, but which doesn't actually translate to the code.
Hey! Let's avoid any similitude to the examples from Learning iOS Development! (Don't use cars).
Also, let's avoid subtly insulting groups of people in the example using humans and zombies!
Hey! Let's avoid ridiculously verbose method names in the examples!
What is the linter?
Relate class objects : instance objects :: printing die : printed paper. Much better metaphor, or blueprint and house. If the class object is an object, what's the value in creating an instance? Set up the problem.
Let's wait to discuss custom initializers until the next unit which already includes it.
The reading doesn't really follow its title-topic. Should this stick to a discussion of OOP?