pablasso

Pod::Spec.new do |s|
  s.name         = "TURecipientBar"
  s.version      = "2.0.0"
  s.summary      = "A UIView to handle entering recipients similar to iOS Mail."
  s.homepage     = "http://github.com/pablasso/TURecipientBar"
  s.license      = 'BSD'
  s.author       = { "David Beck" => "[email protected]" }
  s.source       = { :git => "https://github.com/pablasso/TURecipientBar.git", :branch => 'standalone-bar' }
  s.platform     = :ios, '6.0'
  s.source_files = 'TURecipientBar/*.{h,m}'

pablasso

### Keybase proof

I hereby claim:

  * I am pablasso on github.
  * I am pablasso (https://keybase.io/pablasso) on keybase.
  * I have a public key whose fingerprint is 1CD2 0E79 B96F 75E8 D110  C5EB FBA8 13AD 8B74 C3CF

To claim this, I am signing this object:

pablasso

Keybase proof

I hereby claim:

• I am pablasso on github.
• I am pablasso (https://keybase.io/pablasso) on keybase.
• I have a public key whose fingerprint is 5732 9BB1 4218 0189 060A 4C7A BFE1 884D EB5A 5310

To claim this, I am signing this object:

pablasso

for (var i=1; i<=100; i++) {
  if (i % 3 === 0) {
    console.log('Fizz');
  }
  else if (i % 5 === 0) {
    console.log('Buzz');
  }
  else {
    console.log(i);
  }

pablasso

from django.forms.models import model_to_dict


class ModelDiffMixin(object):
    """
    A model mixin that tracks model fields' values and provide some useful api
    to know what fields have been changed.
    """

    def __init__(self, *args, **kwargs):

pablasso

# flake8: noqa

from datetime import datetime
import time


class QueueRunnerTimeoutException(Exception):
  pass

pablasso

from django.core.management.base import BaseCommand
from django.db import transaction


class Command(BaseCommand):
    args = ''
    help = ''

    def handle(self, **options):
        for i in range(0, 5):

pablasso

How to write a Specification

So why should we write specs? you may be asking.

Why won't people write specs? People claim that it's because they're saving time by skipping the spec-writing phase. They act as if spec-writing was a luxury reserved for NASA space shuttle engineers, or people who work for giant, established insurance companies. Balderdash. First of all, failing to write a spec is the single biggest unnecessary risk you take in a software project. It's as stupid as setting off to cross the Mojave desert with just the clothes on your back, hoping to "wing it." Programmers and software engineers who dive into code without writing a spec tend to think they're cool gunslingers, shooting from the hip. They're not. They are terribly unproductive. They write bad code and produce shoddy software, and they threaten their projects by taking giant risks which are completely uncalled for.

*– Joel Spolsky on [Painless Functional Specifications](http://www.joelonsoftware.com/articles/fog0000000036

pablasso

Title

Contents

• A. Disclaimer
• B. Author
• C. Overview
• D. Nongoals
• E. Hypothesis
• F. Theory of Operation