We migrated this website to a new platform, and are working to correct formatting errors in older blog posts as a result. If you encounter an error, please send an email to scholarslab@virginia.edu. Thanks!
Tomorrow, in an ongoing effort to teach us how to use Ruby, we are embarking on the adventure that is “Pair Programming.” We are going to create a “Jotto” game, courtesy of Eric by breaking it into discrete classes and having each pair work on a different class. The goal is to have one person as the “driver” (typing all the code) and one person as the “navigator” (reading from the ruby documentation). We can now move from the theoretical training that we’ve mostly been doing up until now and get some “on the job” training.
I’m excited to work collaboratively with some of my Praxis cohort. Given how solitary and isolating graduate school work can be, I’m looking forward to a project that is based on working collectively. The natural parallel to draw for tomorrow (thank you David McClure) is Project Runway. In fact once David said it it seemed impossible to not see the parallels.
A group of good looking young people struggling to break into a career that is almost impossible to get into, time deadlines will likely drive us to get into some comedic fights and then reconciliations, and we have a group of calm white guys walking around the office telling us to “make it work!” Fortunately the competitive edge that often drives Project Runway contestants to tears is not looming over our heads. This also means we don’t have to work behind each others backs and form alliances wherein we only share code with certain members of the group. No, I think instead this will be the best of Project Runway, the collaborative spirit that generates new ideas and capitalizes on the productivity of working across lines of difference (either disciplinary or in terms of expertise). If all of that falls through, maybe we’ll at least get a good work out in the process…
