Community Data Science Workshops (Fall 2014)/Reflections: Difference between revisions

Content added Content deleted
imported>Ddailey
No edit summary
(add more raw notes)
Line 1: Line 1:

Community_Data_Science_Workshops_(Fall_2014)/Reflections

'''
'''
Scheduling the next workshop''': Not too close to the end of the quarter.
Scheduling the next workshop''': Not too close to the end of the quarter.
Line 178: Line 175:


The pragmatism of what is taught demonstrates a clear value. It would be helpful to make sure that all mentors are clear that part of what is expected of them they give pragmatic coaching. That is they should lead mentees to something that works rather than telling them what an expert would do.
The pragmatism of what is taught demonstrates a clear value. It would be helpful to make sure that all mentors are clear that part of what is expected of them they give pragmatic coaching. That is they should lead mentees to something that works rather than telling them what an expert would do.

== Mako's Raw Notes ==

* general

anaconda solved problems

- next time recruit less mentors for hte first session

sticky notes didn't work as well this time

- especially during the lectures
- we did this better last time

-> hjave better sticky notes would ahve been helpful

rooms:

maybe get the oodegard room
architecture of the space has quickly become the limiting factor

checkout
- not everybody loves the checkout, maybe there's a way we can make it more fun?

communiate the whole setup process to the mentors ahead of time

-> maybe stream line the process

-> finding the directory continues to be hard



we moved the curriculum from cmd to powershell

- windows xp is broke now. make sure you ahve a person with xp skills on hand

not a single person in our session had ip

we can move away from 3 separate installations in the setup information.

- everybody can use zip instead of a zip/tar.gz both


maybe we can consoldiate the wiki pages into a singel page which will be much eaiser to instlla nd keep updated in the future

generally, lets stop copying and pasting new stuff into the wiki. we when archive the old version, we can create links to teh old version of the wiki pages (intstall the templates from english wikipedia)

get rid of pages that are event specific

* friday evening

better material/training and information for mentors on what to expect

mentors should meet 15-20 minutes early to get to know each oand go over things

- maybe t-shirts buttons, etc or something to distinguish mentors

- encourage peoplt o reach out

topics to cover:

how much should you help? (not too much)

anaconda

- non-free and we're unhappy witht hat

- linux seems like we might actually want ot do sidewizse but it does work

- if something fully free and almost as good comes along, we'll use it

-> write installation instructions for linux

3 people who used it out of 80 had problems

-> anaconda choked on a person unicode path because the users homedir was in simplified chinese

broader unicode support wont be fixed until we can move to python3 and we still seem a little while away from that



* demorgraphics

people come in: departments? maybe build a table?

* org suggestions

let people joiun int he later session

making letting peopel skpi #1 could be usefuil

-> maybe we can accept people after words

-> alternatively, we can try to accetp more newsiebes and improve retention

mixed feelings






ways to improve and retain people

-> layout what we're going to do int he next sessions

go to show why are learning things up front

focus on broad research questions

pair programming?
encouraging people to work iun teams or with other on problems they suggest

next time maybe mine the registration for a list of research questions

note:

next time make it explicit that folks can work in grousp

tip: introduce mentors to everybody very clearly

introductions would have been good but are hard to do

* sesion 1

bring folks back together to go over things

- post examples of code used in teh lectures

- create code base

- turn on loggin gin the concsol and post it after the lecture

mentor workshop:

- get people together before
encourage people to get involved maybe bar meetup

- track diversity of people along more dimensions

- the sql workshops was well received although slight mixed in terms of feedback

more breakout session next time
colorwall was gone and nobody missed it

* babynames

- try to integrate more year
- huge success
- may split rooms into two baby names



list questions up front and let folks choose what to work on and what to bring back together

generally:

- note places to bring folks back together

* session 3

generally:

showcase what students ahve accomplished and places people can change things and do things differently

e.g., the fergeson thing with the exmaple from ha=rry party

strong connection between the lecture and the introduction

-> more connections and takeaways to emphasize the session more clearly

how to tap mentors on topics more effectively

wordplay

- kinda borning

next time

- public healtha nd epi data session

end of semseter was too late. maybe have it early next year

twitter:


- have people do the setup ahead of time

-> that was clear ahead of time and it happened in the beginnginf of class. either fix the instruction and make sure that everybody is doing the same thing

speed was an issue

the opaqueness of tweepy was a problem.. option to creat ea version of tweppty that just gives you json

or miku or michael for details onhow to do that

dharma might be able to do this.


sql session:

- maybe split this into two session next time

- merge in some more python this time

#1 intro into sql

#2 using pythong o tgra data and bring python and pandas

wikipedia

- too slow

we can do it faster

lecture
*stress defining functions more and earlier.. maybe in the first project and certain in session #2 so we can use it in the afternoon projects and tweepy



session 3:

show and tell at the end was very effectively

we need a designated mc who can go =between rooms

bring people up to the

matplot lib

- maybe replace it with seaborn?
- tommy will teach it

ideomatic ptyhon

talk to chris to try to fix those things
Retrieved from "https://wiki.openhatch.org/wiki/Community_Data_Science_Workshops_(Fall_2014)/Reflections"