I hereby claim:
- I am kalefranz on github.
- I am kalefranz (https://keybase.io/kalefranz) on keybase.
- I have a public key whose fingerprint is 19EC 56B9 63DF F1EA 529B 9508 B2BF 5972 608A D308
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
import time | |
import uuid | |
from boto.exception import S3ResponseError | |
from boto.s3.connection import S3Connection | |
from boto.s3.key import Key | |
def create_key(): | |
return str(time.time()) + '-' + uuid.uuid4().hex |
"""The Enum class here is a python27 port of the python34 Enum, but extended with extra | |
functionality. | |
TODO: The API should be a strict superset of the python34 Enum. | |
""" | |
from transcomm.common.crypt import as_base64, from_base64 | |
Core Assertion: The company owns the code, not the contractor.
If you're a contractor, why wouldn't you want to keep the actual source to yourself? You lock the company your contacting for into using your services in perpetuity. Good for the contractor; very bad for the company. My guess is that less-than-compentant and more "old school" contractors who aren't able to keep up with technology's pace will push this tactic for their own job security. But the contractor lock-in prevents the company from moving forward with their product using another contractor if the relationship sours with the current contractor. It also prevents the company from transitioning away from contract work to an in-house development team.
The rest of this document contains steps necessary to have the best chance for getting quality code from a contractor. I would consider each item mandatory. There are also plenty of "nice to haves," but I want to keep th