maraujop

Copyright (c) 2012, Miguel Araujo
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

 * Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.

 * Redistributions in binary form must reproduce the above copyright notice,

mikeyk

from django.contrib.sessions.backends.base import SessionBase, CreateError
from django.conf import settings
from django.utils.encoding import force_unicode
import redis

class SessionStore(SessionBase):
    """ Redis store for sessions"""

    def __init__(self, session_key=None):
        self.redis = redis.Redis(

dpaneda

Programming Achievements: How to Level Up as a Developer

This gist is part of a blog post. Check it out at:

http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer

maraujop

# -*- coding: utf-8 -*-
from django import forms

from crispy_forms.helper import FormHelper
from crispy_forms.layout import Layout, Div, Submit, HTML, Button, Row, Field
from crispy_forms.bootstrap import AppendedText, PrependedText, FormActions


class MessageForm(forms.Form):
    text_input = forms.CharField()

dmcquay

from tastypie.http import HttpUnauthorized

class MultiAuthentication(object):
    """
    An authentication backend that tries a number of backends in order. You may specify using the and_ kwarg
    whether or not all backends must authenticate the user or if authentication should stop after the first success.
    It defaults to False, meaning that only one authentication backend must return True.

    For example, let's say you have three classes:
        MyAuth1

jhclark

L1 cache reference                          0.5 ns
Branch mispredict                             5 ns
L2 cache reference                            7 ns             14x L1 cache
Mutex lock/unlock                            25 ns
Main memory reference                       100 ns             20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy              3,000 ns
Send 1K bytes over 1 Gbps network        10,000 ns    0.01 ms
Read 1 MB sequentially from memory      250,000 ns    0.25 ms
Round trip within same datacenter       500,000 ns    0.5  ms
Read 1 MB sequentially from SSD       1,000,000 ns    1    ms  4X memory

olasitarska

# -*- coding: utf-8 -*-
"""
Builds epub book out of Paul Graham's essays: http://paulgraham.com/articles.html

Author: Ola Sitarska <[email protected]>
Copyright: Licensed under the GPL-3 (http://www.gnu.org/licenses/gpl-3.0.html)

This script requires python-epub-library: http://code.google.com/p/python-epub-builder/
"""

jdmaturen

Who pays when startup employees keep their equity?

JD Maturen, 2016/07/05, San Francisco, CA

As has been much discussed, stock options as used today are not a practical or reliable way of compensating employees of fast growing startups. With an often high strike price, a large tax burden on execution due to AMT, and a 90 day execution window after leaving the company many share options are left unexecuted.

There have been a variety of proposed modifications to how equity is distributed to address these issues for individual employees. However, there hasn't been much discussion of how these modifications will change overall ownership dynamics of startups. In this post we'll dive into the situation as it stands today where there is very near 100% equity loss when employees leave companies pre-exit and then we'll look at what would happen if there were instead a 0% loss rate.

What we'll see is that employees gain nearly 3-fold, while both founders and investors – particularly early investors – get dilute