it’s my community now, it’s your community too ようこそ！
. .back to my employer. .
hacking culture at GW Libraries in several steps
we write code for libraries among many other things, but this is code4lib, so. .
goal: write meaningful code that helps people reliably well
we use github extensively github . com / gwu - libraries
we use a university-approved free software license
step 0 - write code step 1 - share code but..
we did not talk with each other enough about our code
a “rough code and no consensus” local culture
two ways to talk about code •review each other’s code •read other people’s code
old workflow: make a change, publish the change
new workflow: propose a change, someone else decides whether to publish
use github culture • create a git branch • commit changes local y • push branch to github • create a pull request • review each others’ pull requests
≥2 people see every change and discuss issues
take a global practice make a local workflow
code read • once per week • open up some code on github • read it together • include col eagues from other departments • so far: pymarc, bagit.py, bento_search (ruby/rails), arduino, catmandu (perl)
why read code? • people ask questions • teach each other about how code works • no ego - somebody else’s code!
who’s qualified? •everyone who comes! •self-selected - if you want to attend, you’re qualified •acknowledge, temper Imposter Syndrome * * wikipedia.org/wiki/Impostor_syndrome
code read benefits • engages non-coder specialists in algorithmic thinking • engages coder in other areas of specialization • deepens respect for each other • helps non-coders talk about code • helps coders talk with each other