Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handout(s)? #27

Open
tommeagher opened this issue Jan 29, 2016 · 14 comments
Open

Handout(s)? #27

tommeagher opened this issue Jan 29, 2016 · 14 comments

Comments

@tommeagher
Copy link
Collaborator

One piece of early feedback we got last year was that some students really love paper and wanted handouts.
We provide a lot of links in the repo. Would any of these work as a good one or two page handout? Or do you know of another that would be better?

@chrislkeller
Copy link
Collaborator

Some kind of reference for during the class would certainly be helpful.

This is linked to off the take home page and could do the trick.

This is also a good printable reference.

@richardsalex
Copy link
Collaborator

These aren't terrible either: 1, 2.

I can talk to the home office about having these printed up and waiting for the class in Denver once we decide on the best materials.

@zufanka
Copy link
Collaborator

zufanka commented Jan 30, 2016

I think the 1
https://ddi.ifi.lmu.de/probestudium/2013/ws-i-3d-programmierung/tutorials/python-referenzkarte
that Alex proposed is the best (2
http://www.cogsci.rpi.edu/~destem/igd/python_cheat_sheet.pdf gives 404
btw)
We might also however want to also include functions of the modules we will
be using (most importantly BeautifulSoup and regex I'd say).

On Fri, Jan 29, 2016 at 8:08 PM, Alex Richards [email protected]
wrote:

These aren't terrible either: 1
https://ddi.ifi.lmu.de/probestudium/2013/ws-i-3d-programmierung/tutorials/python-referenzkarte,
2 http://www.cogsci.rpi.edu/%7Edestem/igd/python_cheat_sheet.pdf.

I can talk to the home office about having these printed up and waiting
for the class in Denver once we decide on the best materials.


Reply to this email directly or view it on GitHub
#27 (comment).

Adriana Homolova

data journalist

+31-652245912 | 0F097E0F | @naberacka

@tommeagher
Copy link
Collaborator Author

This link is working for me now. I like this one the best, though we could certainly add to it if we wanted to add, as @zufanka suggested, information on requests or bs4. Many of the other tipsheets are inscrutable to me, even as someone who's been writing Python for years. I don't think they'd be as useful for apprehensive journalists who might not know where to start. I'd find them pretty off-putting, personally.

Does anyone else like this approach? Anyone want to take a stab at fleshing this out a little bit for our audience? (Obviously doesn't have to be a one-pager).

@hbillings
Copy link
Collaborator

hbillings commented Feb 5, 2016 via email

@tommeagher
Copy link
Collaborator Author

👍, Heather. Thanks! Holler if you want any help or feedback.

@hbillings
Copy link
Collaborator

hbillings commented Feb 5, 2016 via email

@richardsalex
Copy link
Collaborator

I may have spoken too soon on the ability to have these handouts waiting for us in Denver; it seems as the conference has grown (and grown and grown) to a whopping 13+ rooms, IRE stopped trying to deal in physical materials for classes ahead of time. The best course of action may just be to give attendees a PDF copy of what we come up with so that they can print it out later.

Also, there was a lingering question about having a whiteboard. This should be possible, and I'm going to work on coordinating with the hotel to have one of these for PyCAR and probably the intermediate class taught by Serdar and Eric. It's probably not going to feasible to have them in all the Python rooms, unfortunately.

@tommeagher
Copy link
Collaborator Author

@richardsalex, I think it's fine if we don't have physical printouts for people. With what Heather is working on, we can feature it prominently in the README and in the class to make it clear that this is the one cheatsheet to rule them all.

And a whiteboard would be great. Thanks for following up on this.

@zufanka
Copy link
Collaborator

zufanka commented Feb 28, 2016

I made a short presentation on debugging and created a simple buggy script. The aim is to do this within half an hour. I'm also working on one A4 cheatsheet for types of errors (I still need to work out the examples). What do you think?
@tommeagher would you please help me to integrate it into this repo?

@tommeagher
Copy link
Collaborator Author

@zufanka, I added your script to the repo and a link to your slide deck in this commit. I think they look good and will be a good addition to the day.
The debugging cheatsheet will be super helpful too. Once you have that done and @hbillings does the general handout, we'll close this issue.

@zufanka
Copy link
Collaborator

zufanka commented Mar 5, 2016

@tommeagher hereby the cheatsheet. Did I miss something important? Also: could it be printed in color? If not I have to come up with something else. :) Looking forward to seeing you all in Denver!

@tommeagher
Copy link
Collaborator Author

@zufanka, this debugging tipsheet looks good. We're actually not going to be able to print them off for people, but they'll be able to see the colors on the PDF and print them at home. Very nice. Thank you for pulling it together! I'll add it to the repo in the morning.

I'm not sure if @hbillings will still be able to do the more general python tipsheet as she's just starting her new job, but we should be good to go otherwise.

@richardsalex
Copy link
Collaborator

+1, @zufanka, looks great!

@tommeagher tommeagher modified the milestone: NICAR 2017 Jan 19, 2017
@tommeagher tommeagher modified the milestone: NICAR 2017 Mar 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants