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

arthurnn

require 'active_support/all'
require 'active_record'
require 'logger'

ActiveRecord::Base.logger = Logger.new(STDOUT)

spec = { 'test' => {adapter: 'sqlite3', database: ':memory:'},
         'test_readonly' => {adapter: 'sqlite3', database: ':memory:'},
         'shared_test' => {adapter: 'sqlite3', database: ':memory:'},
         'shared_test_readonly' => {adapter: 'sqlite3', database: ':memory:'}

brunophilipe

https://maps.googleapis.com/maps/api/staticmap?size=576x576&zoom=12&center=41.386162%2C%202.172800&style=feature%3Aall%7Cvisibility%3Aoff&style=feature%3Aroad%7Celement%3Ageometry%7Ccolor%3A0x000000%7Csaturation%3A0%7Cweight%3A0.2%7Cvisibility%3Aon&scale=2&key=YOUR_API_KEY

shagunsodhani

TAO

• Geographically distributed, read-optimized, graph data store.
• Favors availability and efficiency over consistency.
• Developed by and used within Facebook (social graph).
• Link to paper.

Before TAO

• Facebook's servers directly accessed MySQL to read/write the social graph.

vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

jch

require 'rack'

# Track changes in rack requests and responses made by middleware.
#
# SomeMiddleware
#   request: ...
#   response: ...
# AnotherMiddleware
#   request: ...
#   response: ...

lenaschoenburg

#![feature(lang_items, asm)]
#![crate_type = "staticlib"]
#![no_std]

const GPIO_BASE: u32 = 0x3F000000;
const GPIO_SET: u32 = 0x3F200020;
const GPIO_CLR: u32 = 0x3F20002C;
const GPIO47: u32 = 0x8000;

fn sleep(value: u32){

fitnr

[
  {
    "city": "Amsterdam",
    "urls": [
      {
        "link": "GVB",
        "url": "http://www.gvb.nl/"
      }
    ]
  },

fasterthanlime

State of emergency in France

Sources

• Loi n°55-385 from 1955
• Wikipedia / Etat d'urgence en France (general structure)

Process

blithe

read () {
  open "http://blitherocher.com"
}

article () {

# change in to the directory where I keep my journal project
cd /projects/personal_projects/personal_site

echo "Creating article '$@'"