dcramer

from django.db.models.signals import post_init

def track_data(*fields):
    """
    Tracks property changes on a model instance.
    
    The changed list of properties is refreshed on model initialization
    and save.
    
    >>> @track_data('name')

jdmaturen

import logging

from math import exp
from random import random
from time import sleep
from time import time
from uuid import uuid1

from redis.exceptions import WatchError

dcramer

# create a dummy heroku app
heroku create --stack cedar

# add sentry
heroku addons:add sentry

# fetch your config
heroku config | grep SENTRY_DSN

# configure your application via http://getsentry.com/guide/

jimbojsb

Step 0:

Get Homebrew installed on your mac if you don't already have it

Step 1:

Install highlight. "brew install highlight". (This brings down Lua and Boost as well)

Step 2:

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:

dcramer

import heapq
from threading import Lock


class HeapQueue(object):
    def __init__(self, values=None, maxsize=None, reversed=False):
        """
        Create a new heap queue.

        - ``maxsize`` will create a capped queue.

mattrobenolt

"""
cramermath
~~~~~~~~~~

Usage:

  >>> import cramermath
  >>> cramermath.log(10)
  0.014728067495500818
"""

dcramer

When an update comes into the system we fire off something like the following:

>>> app.buffer.incr(
>>> 	Group,  # model class,
>>> 	{'times_seen': 1},  # counters
>>> 	{'id': group.id},  # filter restrictions, sometimes a composite key
>>> 	{'last_seen': now},  # metadata to update when buffer is processed
>>> )

This would get stored in a hash key as following:

dcramer

Questions to answer:

• Is it a productivity hit?
• What happens when only new hires are required to do code review?
• How bad at large patches?
• What about lack of automated tests?
• Does a lot of back and forth (e.g. comments) indicate problems?
• Does assigning more people (or less) to reviews improve anything?
• How does a person spending more time committing (vs reviewing) affect the team?

karmi

.DS_Store
tmp/