Project 1 about pycar14

[tommeagher]

Chris, you are on the right track. I like your approach here quite a bit. I had a few thoughts and questions as I went through this.

• You might think about changing the names of the functions in each step to different names (opencsv, logcsv, countcsv, etc)
• I think once you're happy with this, make one last file that combines all of these steps and functions into one, and then create a separate set of the files with just the comments and no code. A cheat sheet for the white board exercise might be good too.
• For part step 2, should we write out a for loop,or are we comfortable with throwing folks into the deep end of the list comprehension?
• Should we think about pushing punt the concepts of lists, indexing and slicing to Project 2?
• In Project 2, should we also write to a CSV or change/clean values?

Any thoughts from others? From my vantage point, you're moving in the right direction. Let's keep going!

Tom

[tommeagher]

Thinking more about this. Should we start with a lightning quick overview of variables, strings, integers, lists, dicts before writing the first lesson? Or should I include that in the intro talk?

[chrislkeller]

I think that idea makes a lot of sense. I didn't know if the whiteboarding would include that, but I think having something concrete in front of folks would help.. Is it just a markdown file that runs through definitions and examples?

[hbillings]

It wouldn't hurt to do a quick overview of all of those, but I think we should definitely go over them again as we use them so we're not expecting people to retain that info.

[tommeagher]

Maybe that's in the intro section, where I demo these concepts and give broad explanations and then we repeat, repeat, repeat the ideas through the day. Could make that its own iPython notebook to speed things up.

[kevinschaul]

Having a reference sheet with types could be very helpful. Project 4 (as it stands now, at least) requires knowledge of lists and dicts, and it goes into the parallels of those with JSON.

[tommeagher]

Great idea.
Before I go reinvent the wheel, has anyone seen or Googled a good one that's already out there that we can fork?

This is my phone. There are many like it, but this one is mine.

On Feb 13, 2014, at 1:23 PM, Kevin Schaul [email protected] wrote:

Having a reference sheet with types could be very helpful. Project 4 (as it stands now, at least) requires knowledge of lists and dicts, and it goes into the parallels of those with JSON.

—
Reply to this email directly or view it on GitHub.

[zstumgoren]

@tommeagher Here's a cheatsheet I've found handy. Might work for you.

And yes, I've been spying on you all :) Love how you're crowdsourcing this. You're forcing me to revisit some of my own way-to-complex bits of code for our class, and making me wish we'd taken this approach in years past. Can't wait to swing by the class and watch you all in action!

[tommeagher]

@zstumgoren, thanks for the cheatsheet. This is great and will be an awesome resource to share with everyone. Much appreciated.

And, while we're at it, thanks for pulling us together to teach the class. I'm also really looking forward to your beyond the basics sessions on Saturday!

[tommeagher]

Can we work .split() and .strip() in either this project or the second one? Think these are crazy useful string methods.