shortjared

a4b.amazonaws.com
access-analyzer.amazonaws.com
account.amazonaws.com
acm-pca.amazonaws.com
acm.amazonaws.com
airflow-env.amazonaws.com
airflow.amazonaws.com
alexa-appkit.amazon.com
alexa-connectedhome.amazon.com
amazonmq.amazonaws.com

jarrettmeyer

EXEC sp_configure 'Ole Automation Procedures', 1;
GO

RECONFIGURE;
GO

arobson

Abstraction Suggestions

Summary: use good/established messaging patterns like Enterprise Integration Patterns. Don't make up your own. Don't expose transport implementation details to your application.

Broker

As much as possible, I prefer to hide Rabbit's implementation details from my application. In .Net we have a Broker abstraction that can communicate through a lot of different transports (rabbit just happens to be our preferred one). The broker allows us to expose a very simple API which is basically:

• publish
• request
• start/stop subscription

gist:4545932

// First version
// 1. Multiple return statements (> cyclomatic complexity)
// 2. 'Happy' path comes first
public IEnumerable<ValidationResult> Validate(ValidationContext validationContext)
{
  var startTime = TimeSpan.Parse(StartTime);
  var endTime = TimeSpan.Parse(EndTime);

  if (startTime < endTime)
    return new ValidationResult[] { };

imathis

Why I don't like automated time delayed publishing of drafts in Octopress:

1. It's not hard to publish a draft when you want to.
2. It may be hard to set up due to development environment issues.
3. There are lots of edge cases that aren't obvious at first. Supporting this won't be easy.
4. People could accidentally push a broken site.

Example

You're working on a plugin for Octopress and your task timer goes off. Your blog just starts generating and deploying in the background but you're in a development branch working on some feature. Result: your script generates your test site, but not your blog, and pushes it live in the background.

jarrettmeyer

require "rubygems"
require "date"

# Configuration
base_dir = Dir.pwd
blog_dir = "#{base_dir}/blog"
source_dir = "#{blog_dir}/source"
posts_dir = "#{source_dir}/_posts"
git_remote = "origin"
git_branch = "master"

artero

Launch Sublime Text 2 from the Mac OS X Terminal

Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.

open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl

You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html

Installation

jarrettmeyer

(function ($) {
    $.fn.buildSelectList = function (options) {
        defaults = {
            url: null,                  // URL for the select list options.
            data: null,                 // Data to be passed to the URL.
            value: null,                // Currently selected option value.
            valueProperty: "value",     // JSON property for option value.
            textProperty: "text",       // JSON property for option text.
            type: "GET",                // JSON HTTP method.
            useCache: false,            // Allow outputs to be cached.