Patrick Schneider pschneider

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
Once documentation has been written, development should commence, and test-driven development is preferred.
Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
When a feature is being modified, it should be modified documentation-first.
When documentation is modified, so should be the tests.

Wil Turner, Brook Callhan: Speakers

##3 Main components/concepts that enable UI Testing:##

UITesting
- Find and interact w/ UI elements
- Validate UI properties and state
UIrecording
- Updated test reports to include UI testing data
- UI testing is enabled by XCTest and UI Accesibility

Switch To Vim For Good

NOTE: This guide has moved to https://github.com/bpierre/switch-to-vim-for-good

This guide is coming from an email I used to send to newcomers to Vim. It is not intended to be a complete guide, it is about how I switched myself.

My decision to switch to Vim has been made a long time ago. Coming from TextMate 1, I wanted to learn an editor that is Open Source (so I don’t lose my time learning a tool that can be killed), cross platform (so I can use it everywhere), and powerful enough (so I won’t regret TextMate). For these reasons, Vim has always been the editor I wanted to learn, but it took me several years before I did it in a way that works for me. I tried to switch progressively, using the Janus Vim distribution for a few months, then got back to using TextMate 2 for a time, waiting for the next attempt… here is what finally worked for me.

Original gist with comments: https://gist.github.com/bpierre/0a0025d348b6001394e0

PerfectLibのexampleをnginxで動かす

Swift, PerfectLibのインストール

こっちを参考 -> UbuntuにSwiftとPerfectLibをインストールする

nginxのインストール

$ sudo apt-get install nginx

	# see the current limits
	$ sysctl -a \| grep maxproc

	# increase it
	$ sudo sysctl -w kern.maxproc=xxxx
	$ sudo sysctl -w kern.maxprocperuid=xxx

	# run at startup
	$ sudo vim /etc/sysctl.conf

	extension NSURL {
	func getKeyVals() -> Dictionary<String, String>? {
	var results = [String:String]()
	var keyValues = self.query?.componentsSeparatedByString("&")
	if keyValues?.count > 0 {
	for pair in keyValues! {
	let kv = pair.componentsSeparatedByString("=")
	if kv.count > 1 {
	results.updateValue(kv[1], forKey: kv[0])
	}

	#!/bin/sh

	#
	# Script for Xcode and Carthage
	# ------------------------------
	#
	# Dismisses changes to all the frameworks except the given frameworks in the iOS build folder.
	# This is used to undo the changes done to the framework build after `carthage update` command.
	#
	#


	/* How to Hook with Logos
	Hooks are written with syntax similar to that of an Objective-C @implementation.
	You don't need to #include <substrate.h>, it will be done automatically, as will
	the generation of a class list and an automatic constructor.

	%hook ClassName

	// Hooking a class method
	+ (id)sharedInstance {

	func fetchUserId() -> Observable<String> {
	return create{ (observer) -> Disposable in
	Client.fetchUserId() { [unowned self]
	(userId: String?, err: ErrorType?) -> Void in
	if let _ = err{
	observer.on(Event.Error(err!))
	} else {
	observer.on(Event.Next(userId))
	observer.on(Event.Completed)
	}

	//
	// Swift-KVO
	//
	// Created by Jim Correia on 6/5/14.
	// Copyright (c) 2014-2015 Jim Correia. All rights reserved.
	//
	// Update: 6/17/2014
	//
	// KVOContext has gone away; use the same idiom you'd use from Objective-C for the context
	//