freemansion

import UserNotifications

// 1. Request Permission 
func requestAuthorization() {
    UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .sound]) { (granted, error) in
        if granted {
            // Success
        } else {
            // Error
            print(error?.localizedDescription)

freemansion

#!/bin/sh
#
# Setup a work space called `work` with two windows
# first window has 3 panes. 
# The first pane set at 65%, split horizontally, set to api root and running vim
# pane 2 is split at 25% and running redis-server 
# pane 3 is set to api root and bash prompt.
# note: `api` aliased to `cd ~/path/to/work`
#
session="work"

freemansion

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

freemansion

    ACTION = build
    AD_HOC_CODE_SIGNING_ALLOWED = NO
    ALTERNATE_GROUP = staff
    ALTERNATE_MODE = u+w,go-w,a+rX
    ALTERNATE_OWNER = grantdavis
    ALWAYS_SEARCH_USER_PATHS = NO
    ALWAYS_USE_SEPARATE_HEADERMAPS = YES
    APPLE_INTERNAL_DEVELOPER_DIR = /AppleInternal/Developer
    APPLE_INTERNAL_DIR = /AppleInternal
    APPLE_INTERNAL_DOCUMENTATION_DIR = /AppleInternal/Documentation

freemansion

/// This is a list of Hypertext Transfer Protocol (HTTP) response status codes. 
/// It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes.
/// The first digit of the status code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum.
enum HTTPStatusCode: Int, Error {
    
    /// The response class representation of status codes, these get grouped by their first digit.
    enum ResponseType {
        
        /// - informational: This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line.
        case informational

freemansion

/*
  The "hello world" of neural networks: a simple 3-layer feed-forward
  network that implements an XOR logic gate.

  The first layer is the input layer. It has two neurons a and b, which
  are the two inputs to the XOR gate.

  The middle layer is the hidden layer. This has two neurons h1, h2 that
  will learn what it means to be an XOR gate.
 

freemansion

#!/bin/sh

UNIVERSAL_OUTPUTFOLDER=${BUILD_DIR}/${CONFIGURATION}-universal

# make sure the output directory exists
mkdir -p "${UNIVERSAL_OUTPUTFOLDER}"

# Step 1. Build Device and Simulator versions
xcodebuild -target "${PROJECT_NAME}" ONLY_ACTIVE_ARCH=NO -configuration ${CONFIGURATION} -sdk iphoneos  BUILD_DIR="${BUILD_DIR}" BUILD_ROOT="${BUILD_ROOT}" clean build
xcodebuild -target "${PROJECT_NAME}" -configuration ${CONFIGURATION} -sdk iphonesimulator ONLY_ACTIVE_ARCH=NO BUILD_DIR="${BUILD_DIR}" BUILD_ROOT="${BUILD_ROOT}" clean build

freemansion

import os
import sys
from getpass import getpass

import gdata.docs.service
import gdata.spreadsheet.service


'''
    get user information from the command line argument and 

freemansion

This is a post by Joel Spolsky. The original post is linked at the bottom.

This is such a common question here and elsewhere that I will attempt to write the world's most canonical answer to this question. Hopefully in the future when someone on answers.onstartups asks how to split up the ownership of their new company, you can simply point to this answer.

The most important principle: Fairness, and the perception of fairness, is much more valuable than owning a large stake. Almost everything that can go wrong in a startup will go wrong, and one of the biggest things that can go wrong is huge, angry, shouting matches between the founders as to who worked harder, who owns more, whose idea was it anyway, etc. That is why I would always rather split a new company 50-50 with a friend than insist on owning 60% because "it was my idea," or because "I was more experienced" or anything else. Why? Because if I split the company 60-40, the company is going to fail when we argue ourselves to death. And if you ju

freemansion

Videos

• Introduction to Functional Programming Johannes Weiß - http://kcy.me/1ngiv
• ReactiveCocoa at MobiDevDay Andrew Sardone - http://kcy.me/1nhl3
• The Future Of ReactiveCocoa Justin Spahr-Summers - http://kcy.me/1nhs7
• Enemy of the State Justin Spahr-Summers - http://kcy.me/1njzs
• WWDC 2014 Session 229 - Advanced iOS Application Architecture and Patterns Andy Matuschak - http://kcy.me/1pyva
• Functioning as a Functionalist Andy Matuschak - http://kcy.me/22o45
• Controlling Complexity in Swift Andy Matuschak - http://kcy.me/23sc9
• Functional and reactive programming with Swift Ash Furrow -