cblunt

# ...

gem 'carrierwave'
gem 'fog', '~> 1.0.0' # Need to specify version, as carrierwave references older (0.9.0) which doesn't allow configuration of Rackspace UK Auth URL

mtitolo

• Andre/Dave - Opening Remarks
• Matt Kelly - Mobile Web Landscape
• Fil Maj - Whats new in PhoneGap 2.0
• Gord Tanner - CordovaJS
• Pamela Fox - PhoneGap Pain Points
• James Burke - RequireJS and PhoneGap
• Patrick Mueller - debugging cordova apps
• Simon MacDonald - Corinthian and code
• Don Coleman - PhoneGap Plugins
• Andrew Lunny - PhoneGap/Build

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

garann

I was inspired by Selena Deckelmann's list of Career Resources for Women (http://www.chesnok.com/daily/career-resources-for-women/), but couldn't think of much to contribute. So I thought maybe those of us already in the field and in a position to mentor could work on creating more. Please fork or comment and add your own!

Also: there is a wealth of info online and elsewhere dating back to the first time it occurred to our species to exchange labor for currency on these topics in general. What I hope we can provide here is our take as individuals. What we would say to someone if we were sitting across from her acting as a mentor. I don't think we should worry about being objectively "right", or about duplicating topics. I add this bit of anti-editorializing in hopes that women will contribute without feeling pressured to be experts, which I worry might prevent them from doing so. TY. :)

Applying for jobs

• "developer resumes in < 5 minutes" from @garann https://vimeo.com/47550018
• "Cover Letters in 5 m

selenamarie

#!/usr/bin/env python

import tweepy
from BeautifulSoup import BeautifulSoup as parser
import urllib
import sys


import argparse
import ConfigParser

aufi

class DragWindow < NSWindow
    
    def awakeFromNib
        self.registerForDraggedTypes [NSFilenamesPboardType]
    end
        
    def performDragOperation(sender)
        filenames = sender.draggingPasteboard.propertyListForType(NSFilenamesPboardType)
        
        p filenames.inspect

courtenay

# output

> gh = Redcarpet::Render::GithubStyleTitles.new
> puts Redcarpet::Markdown.new(gh).render "test\n\n# test 1\n\n# test 2\n\n# test 1\n\n# test 1"

=> 

<a name="test-1" class="anchor" href="#test-1"><span class="anchor-icon"></span></a><h1 id="test-1">test 1</h1>

<a name="test-2" class="anchor" href="#test-2"><span class="anchor-icon"></span></a><h1 id="test-2">test 2</h1>

chengyin

// 1. Go to page https://www.linkedin.com/settings/email-frequency
// 2. You may need to login 
// 3. Open JS console
//    ([How to?](http://webmasters.stackexchange.com/questions/8525/how-to-open-the-javascript-console-in-different-browsers))
// 4. Copy the following code in and execute
// 5. No more emails
//
// Bookmarklet version: 
// http://chengyin.github.io/linkedin-unsubscribed/

jvns

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

boredzo

First, some context.

I urged the AltConf organizers to publish a Code of Conduct for their attendees and speakers. In that Twitter conversation, I repeatedly cited Ashe Dryden's Code of Conduct 101 + FAQ.

This is what they published on their website as their code of conduct (as of 2014-05-06):

AltConf is provided free of charge, on a first-come, first-served basis, without warranty or liability, by volunteers, for the good of our community.

To participate in our conference in any way (attendee, speaker, sponsor, etc), you must agree to abide by the instructions of the volunteers and the decisions of the organizers, and acknowledge that you may be barred from participation at any time, for any reason.