How would we introduce a few levels of basic instruction that have a related and linear curriculum? about pycar

[chrislkeller]

@esagara raises an awesome point/idea/opportunity...

I feel we need to present python in a way that is easily accessible to new users - i.e. an environment they will be able to easily recognize when launching up python for the first time when they return home.

I like the @mikejcorey line of thinking here:

I would suggest rebranding those as specialized (and highly worthwhile) topics: "Refactoring your code" or "object-oriented Python" and "Python for data analysis."

[tommeagher]

And to be really ambitious, can we map those levels to other tools/languages across the conference?

Is there a level for scraping that's offered in Python, Ruby and JS, or one on aggregating data in SQL, R, Python and Excel?

[hbillings]

(comment moved to #17, where it fits better)

[richardsalex]

As part of having more top-down guidance on classes for various programming languages, I think we've addressed this somewhat. Classes tend to address similar concepts across languages (where applicable) — collection, analysis, viz, etc. In the past, people used to pitch sessions and we'd end up with variations of similar classes. If progressions existed, it wasn't always clear to attendees. We're still working out kinks on naming conventions for classes in Denver, but look for those to be more clear as well.