task dependency graph

Just to give you an idea of how I think about these things, here’s a picture of my project.

This format is called a “task dependency graph”, and I have adapted it myself to show iterations and completion.

• Dark outlined circle (libspotify example) is completed. 
• Arrows are dependencies. 
• "Critical path" is the longest chain of work, 
  • "compile mixxx <- mixxx library example <- mixxx libspotify plugin" for this example. 
• The stuff below the wavy line is the next iteration.

Sidebar thought: I notice that often times when I explain this stuff to people I realize I have lots of formal methods and tools that I use without realizing it… when I explain I have to dig up names and analogies by which they were taught to me, so I should try to explain things to people as much as I can. the old idea “the best way to learn is to teach” incarnate.

But then I turned this into a blog post, because I don’t blog enough.