View bullshit.txt
selena@taiping:decision #2004 11:57 ♥: nvm install 4.0.0
bash: [: 000000000400000000000000000000: integer expression expected
^C
selena@taiping:decision #2005 11:57 😱: nvm install 4.0
######################################################################## 100.0%
Checksums empty
Now using node v4.0.0
selena@taiping:decision #2006 11:58 ♥: nvm install 4
######################################################################## 100.0%
Checksums empty
View gist:75e846f91467a93a6029
from crashstats.dataservice.models import magic
globals().update(magic)
import sys
View carbon_x1_dec_2014.md
View gist:ad413cc50c453e2a5925
* how would you write a pure restful service in django from scratch?
https://gist.github.com/peterbe/4337d96d0afd53505cbb
from django import http
def meaningoflife(request):
return http.HttpResponse(json.dump({'number': 42}}, mimetype="application/json")
* where in config/setup do you put this information
View gist:fec696bf042164ea123e
# start dataservice_app.py
socorro/dataservice/dataservice_app.py
# insert these into postgresql:
insert into bugs values (1, 'done', 'good', 'stuff');
insert into bug_associations values (1, 'a signature');
# test POST
View rvlvvr_notes.md
View speaker diversity.md

During the PyLadies lunch here at PyCon, I heard 5 people stand up and say that they would not have given a talk if an individual (in many cases Jessica McKellar) hadn't pestered them repeatedly to give a talk. I saw later that someone else had heard this from 10+ people at the lunch.

Increasing speaker diversity is both about sending emails "to the right mailing lists" but it is also largely dependent on individuals reaching out to new (and veteran) speakers to get them to submit talks.

So - a lot of this work has to happen on multiple fronts at the same time - the CFPs need to go out to lots of lists, and individuals need to reach out to lots of individuals.

The only way I have seen this be consistently successful is if many people on the conference committee are all making individual requests to speakers, and the people making the requests are trusted by the talk submitters. It's a systemic issue involving visibility, trust, mentorship in general, talk submission mentoring, and mentorship of talk c

View keybase.md

Keybase proof

I hereby claim:

  • I am selenamarie on github.
  • I am selenamarie (https://keybase.io/selenamarie) on keybase.
  • I have a public key whose fingerprint is 27DF C0BB 7DD6 5ED2 EA12 E223 C34E 5747 E23D D677

To claim this, I am signing this object:

View gist:9375690
-- this output is interesting :)
SELECT json_object_field_text(ucm.rewrite, 'rewrite_to') as release_channel,
json_array_elements(ucm.rewrite->'BuildID') as buildid, -- yeah this is not good here :D
product_versions.product_version_id,
trim(both '"' from (ucm.rewrite->'Version')::text) as version_string,
product_versions.version_string
FROM
product_productid_map ppm
JOIN update_channel_map ucm USING (productid)
JOIN product_versions ON ppm.product_name = product_versions.product_name