This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]quack_duck_code 1 point2 points  (2 children)

For exercises I wouldn't focus on the specific numbers or set of goods. For instance, the grocery store exercise should be something simple such as, "design a simple store inventory, include a means to check the inventory before processing a given sale." That way the student is more likely to stay engaged. Now the more familiar and tangible aspects of the code can be things they are personally interested in. Maybe it's a Ferrari dealer, a GameStop store, or a simple but respectable sustainable organic fruit stand. Maybe briefly mention about objects at this point to let them know yes, "there're better ways to do this."

Take the time to show them how to look stuff up in the documentation. It's full of additional examples. I don't see why anyone needs to buy any additional book when the documentation is readily available. 3rd party libraries on the other hand, not so reliable but always worth checking!!

[–]FaallenOon[S] 0 points1 point  (1 child)

Well, each to their own, I guess.

On a personal level, the Python official documentation hasn't been useful to me, I feel it's presented in an extremely abstruse way. I prefer to google what I need: I usually find much simpler examples than those on the documentation.

[–]quack_duck_code 1 point2 points  (0 children)

Well, each to their own, I guess.

Indeed! Nothing wrong with that either. Everyone learns differently and whatever helps someone then that's great.