-
Notifications
You must be signed in to change notification settings - Fork 36
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
Comments
I think the 1 On Fri, Jan 29, 2016 at 8:08 PM, Alex Richards [email protected]
Adriana Homolova data journalist +31-652245912 | 0F097E0F | @naberacka |
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). |
I really like that second link. I can take a stab at stubbing something
out.
|
👍, Heather. Thanks! Holler if you want any help or feedback. |
Will do! I'll post a draft here when my brain gives up, haha.
|
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. |
@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. |
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? |
@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. |
@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! |
@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. |
+1, @zufanka, looks great! |
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?
The text was updated successfully, but these errors were encountered: