abhinemani

// This would be a kind of "code of conduct" or "statement of values" cities would prescribe for potential govtech startup vendors.
// VERY DRAFT & UNOFFICAL

- *Citizen-first experience*: In the private sector, simple, beautiful, and easy to use technology has become commonplace -- and that’s happened because user-centric technologists have prioritized user needs and experiences. The city expects the same for the citizen experience: seamless, smart, and accessible.
- *For (All) the People*: The City doesn’t have the luxury of catering to one demographic; our technology must work for any affected resident, no matter ethnicity, access to technology, gender, etc. Government technology must have a bias towards all.
- *Built to scale*: The City prioritizes software-as-a-service technologies that not only can solve a problem locally but also scale nationally, and with that national reach continually deliver better and better product for citizens.
- *Default to open*: Any technology put in place will generate massi

andy-esch

Code for America -- brief deep dive

Andy Eschbacher, Map Scientist, CartoDB

eschbacher@cartodb.com, @MrEPhysics

06/16/15

You can find this page at:

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

jacobian

Where people struggle learning Django

Over the last 3 years or so I've helped a bunch of companies, small and large, switch to Django. As part of that, I've done a lot of teaching Django (and Python) to people new to the platform (and language). I'd estimate I've trained something around 200-250 people so far. These aren't people new to programming — indeed, almost all of them are were currently employed as software developers — but they were new to Python, or to Django, or to web development, or all three.

In doing so, I've observed some patterns about what works and what doesn't. Many (most) of the failings have been my own pedagogical failings, but as I've honed my coursework and my skill I'm seeing, time and again, certain ways that Django makes itself difficult to certain groups of users.

This document is my attempt at organizing some notes around what ways different groups struggle. It's not particularly actionable — I'm not making any arguments about what Django should or shouldn't do (at least

brennandunn

Client Management

• ???

Proposals

• Bidsketch
• Proposable

Invoicing

twofifty.md

Nice speaker lineup for @BritRuby. Except for the 100% white guys part. I don't think adding diversity at the end works. You have to start with it as one of your goals. Who wants to be the token female? Not meaning to single out @BritRuby, just saying I'm disappointed. I know it's a systemic/cultural problem.

By what metric is @BritRuby "one of Europe’s… most diverse Ruby conferences"? Every speaker is a white man.

To an event organiser like myself @BritRuby's line [i.e. "we tried to reach out to non-white dudes but that didn't work"] is 100% bull... that line is getting stale. If you couldn't reach the speakers you haven't made the effort.

@BritRuby Are you saying minority speakers can't get in on merit? Plenty of confs have great speaker lineups that are not 100% white guys.

@BritRuby The comment is not unfair. Else why do you think selecting based on merit results in 100% white guys speaking?

panthomakos

#!/usr/bin/env ruby

require 'benchmark'

REGEXPS = [
  /^no such file to load -- (.+)$/i,
  /^Missing \w+ (?:file\s*)?([^\s]+.rb)$/i,
  /^Missing API definition file in (.+)$/i,
  /^cannot load such file -- (.+)$/i,
]

jlong

var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"

CFPBadmin

1. USE OF EXTERNAL OPEN SOURCE SOFTWARE

	a) "Open Source Software" (OSS) is software that allows its recipients to modify and redistribute the source code; as such, "open source" is a copyright and distribution framework and makes no implications regarding technical support or indemnification. In almost all cases, OSS meets the definition of "commercial computer software" and shall be given appropriate statutory preference in accordance with 41 USC 264B (reference (b)) (see also FAR 2.101(b), 12_1.html 12.000, 12.101 (reference (c))).

	b) Executive agencies, including CFPB, are required to conduct market research when preparing for the procurement of products or services by 41 USC Sec. 253a (reference (e)) (see also FAR 10.001. Market research for software should include OSS.
		a. There are several positive aspects of OSS that should compel CFPB to seek out OSS when conducting market research on software for Bureau-wide use:
			i. Publicly available source code enables continuous and broad peer review that 

erikh

#!/usr/bin/env sh

##
# This is script with usefull tips taken from:
#   https://github.com/mathiasbynens/dotfiles/blob/master/.osx
#
# install it:
#   curl -sL https://raw.github.com/gist/2108403/hack.sh | sh
#