bobby

(ns datomic-helpers
  (:require [datomic.api     :as d]))

;;; Expose Datomic vars here, for convenience

;;; Ring middleware

(defn wrap-datomic
  "A Ring middleware that provides a request-consistent database connection and
  value for the life of a request."

andphe

/usr/bin/plutil -convert xml1 -o - ~/Library/Safari/Bookmarks.plist | grep -E  -o '<string>http[s]{0,1}://.*</string>' | grep -v icloud | sed -E 's/<\/{0,1}string>//g'

npryce

If you're coming to the Property-Based TDD As If You Meant It Workshop, you will need to bring a laptop with your favourite programming environment, a property-based testing library and, depending on the language, a test framework to run the property-based-tests.

Any other languages or suggestions? Comment below.

.NET (C#, F#, VB)

• FsCheck

Python:

inklesspen

(This gist is pretty old; I've written up my current approach to the Pyramid integration on this blog post, but that blog post doesn't go into the transactional management, so you may still find this useful.)

Fast and flexible unit tests with live Postgres databases and fixtures

I've created a Pyramid scaffold which integrates Alembic, a migration tool, with the standard SQLAlchemy scaffold. (It also configures the Mako template system, because I prefer Mako.)

I am also using PostgreSQL for my database. PostgreSQL supports nested transactions. This means I can setup the tables at the beginning of the test session, then start a transaction before each test happens and roll it back after the test; in turn, this means my tests operate in the same environment I expect to use in production, but they are also fast.

I based my approach on [sontek's blog post](http://sontek.net/blog/

ztellman

;; let's create a simple protocol that just returns a number
user> (defprotocol NumberP (number [_]))
NumberP

;; now we'll create an implementation that always returns '1'
user> (deftype One [] NumberP (number [_] 1))
user.One

;; unsurprisingly, this type only has a single static value, which wraps the '1'
> (-> One .getDeclaredFields seq)

rofl0r

#define _XOPEN_SOURCE 700
#include <signal.h>
#include <unistd.h>

int main()
{
	sigset_t set;
	int status;

	if (getpid() != 1) return 1;

also

# /usr/libexec/java_home -X
$ sudo opensnoop -n java_home
  UID    PID COMM          FD PATH
  501  79809 java_home      3 /System/Library/PrivateFrameworks/JavaLaunching.framework/Versions/A/JavaLaunching
  501  79809 java_home      3 /dev/dtracehelper
  501  79809 java_home      4 /System/Library/CoreServices/SystemVersion.bundle//English.lproj
  501  79809 java_home     -1 /System/Library/CoreServices/SystemVersion.bundle//Base.lproj
  501  79809 java_home      4 /System/Library/CoreServices/SystemVersion.bundle/English.lproj/SystemVersion.strings
  501  79809 java_home     -1 /System/Library/CoreServices/SystemVersion.bundle/English.lproj/SystemVersion.stringsdict
  501  79809 java_home      3 /usr/share/icu/icudt51l.dat

telent

App configuration in environment variables: for and against

For (some of these as per the 12 factor principles) 

1) they are are easy to change between deploys without changing any code

2) unlike config files, there is little chance of them being checked
into the code repo accidentally

3) unlike custom config files, or other config mechanisms such as Java

benmccormick

" A minimal vimrc for new vim users to start with.
"
" Referenced here: http://vimuniversity.com/samples/your-first-vimrc-should-be-nearly-empty
"
" Original Author:	     Bram Moolenaar <Bram@vim.org>
" Made more minimal by:  Ben Orenstein
" Modified by :          Ben McCormick
" Last change:	         2014 June 8
"
" To use it, copy it to

ctford

(ns shades.lenses)

; We only need three fns that know the structure of a lens.
(defn lens [focus fmap] {:focus focus :fmap fmap})
(defn view [x {:keys [focus]}] (focus x))
(defn update [x {:keys [fmap]} f] (fmap f x))

; The identity lens.
(defn fapply [f x] (f x))
(def id (lens identity fapply))