jonkiparsky / resilient Goto Github PK

I looked over the material, but it seems pretty dense for the audience you are trying to target.

Trying to learn the definitions, theorems, corollaries, and proofs seems like a good way to kill interest.

I think the way to start the engagement and to learn how to use graph theory is to provide practical problems that can be solved with graph theory. Those solutions have to be good solutions.

When they ask why, then dig deeper, but only as deep as their question.

Then, once they have completed a certain number or set of problems, then push them through the theory and the problems. They'll have little pieces of knowledge from those practical problems to anchor the definitions, and theorems to something already familiar in their mind.

I have found that more unfamiliar parts to a project, the more likely I won't get it off the ground.

I think this is really in line with all the things we discussed at Py meetup.

I think next steps is to break up the notes and exercises into what could become a set of problems that could be done.