This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
// includes bindings for fetching/fetched | |
PaginatedCollection = Backbone.Collection.extend({ | |
initialize: function() { | |
_.bindAll(this, 'parse', 'url', 'pageInfo', 'nextPage', 'previousPage'); | |
this.page = 1; | |
}, | |
fetch: function(options) { | |
options || (options = {}); | |
this.trigger("fetching"); |
# First, create the synonyms file /opt/elasticsearch/name_synonyms.txt | |
# with the contents: | |
# | |
# rob,bob => robert | |
# | |
## CREATE THE INDEX WITH ANALYZERS AND MAPPINGS | |
curl -XPUT 'http://127.0.0.1:9200/test/?pretty=1' -d ' | |
{ |
curl -XGET 'http://127.0.0.1:9200/test/member/_search?pretty=1' -d ' | |
{ | |
"query" : { | |
"bool" : { | |
"should" : [ | |
{ | |
"text" : { | |
"first_name" : { | |
"boost" : 1, | |
"query" : "rob smith" |
# this is a configurable version of an EventMachine syslogger | |
# It was build to replace https://github.com/melito/em-syslog | |
# | |
# You can instantiate many of them (no global variables) as | |
# well as configure the facility. It also quacks like a ruby | |
# logger so it can be interchanged with a ruby logger. | |
# | |
# Example: | |
# | |
# # 11 is the facility code for an FTP daemon |
// Backbone.ModelRouter | |
// -------------------- | |
// | |
// v0.0.0 | |
// | |
// Resolve an :id parameter is a `.modelRoutes` hash, to load | |
// a model and then run the callback method with the specified | |
// model as the arguments, instead of the id parameter. | |
// | |
// Copyright (C) 2012 Muted Solutions, LLC. All Rights Reserved. |
If you have two days to learn the very basics of modelling, Domain-Driven Design, CQRS and Event Sourcing, here's what you should do:
In the evenings read the [Domain-Driven Design Quickly Minibook]{http://www.infoq.com/minibooks/domain-driven-design-quickly}. During the day watch following great videos (in this order):
Title: PostGIS 2.0 Cheatsheet CSS : css/cheaters.css
Permalink to PostGIS 2.0 Cheatsheet
PostgreSQL PostGIS Geometry/Geography/Box Types |
---|
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
Time: 25-30 minutes.
Goal: Better back, front, and overhead squats. Very basic gymnastic conditioning.
"Limber 11" ([video][limber-11])