hyperupcall

// I'm tired of extensions that automatically:
// - show welcome pages / walkthroughs
// - show release notes
// - send telemetry
// - recommend things
//
// This disables all of that stuff.
// If you have more config, leave a comment so I can add it!!

{

bpierre

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

pedro

Batch APIs

• Common requirements

  • Are they atomic?
  • What kind of operations are supported?

• Existing approaches

  • Google storage
    • Multipart/mixed content-type

• POST /batch

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

ryandotsmith

Tales From a Heroku User

Here are some things I have learned along the way.

Last Updated: 2013-02-08

Original Audience: Hack Reactor

About

jclem

name=gifify_`date +%s`
echo -ne $name | pbcopy

osascript <<EOF
tell application "System Events"
  set visible of process "Terminal" to false
end tell

tell application "QuickTime Player"
  activate

jakeonrails

data:text/html, <style type="text/css">#e{position:absolute;top:0;right:0;bottom:0;left:0;}</style><div id="e"></div><script src="http://d1n0x3qji82z53.cloudfront.net/src-min-noconflict/ace.js" type="text/javascript" charset="utf-8"></script><script>var e=ace.edit("e");e.setTheme("ace/theme/monokai");e.getSession().setMode("ace/mode/ruby");</script>

jclem

#!/bin/bash

function printHelpAndExit {
  echo 'Usage:'
  echo '  gifify -coux filename'
  echo ''
  echo 'Options: (all optional)'
  echo '  c CROP:   The x and y crops, from the top left of the image, i.e. 640:480'
  echo '  o OUTPUT: The basename of the file to be output (default "output")'
  echo '  u:        Upload the resulting image to CloudApp'

csquared

/*
 Heroku Office Status Monitor

 What it is:  Arduino + Ethernet Shield
 What it does: Networked device that provides status monitoring.
 
 
 Components:
 - Status site monitor
 HTTP GET to http://outage-lights.herokuapp.com/status to consume current Heroku Platform status.

pamelafox

describe('catalogyBody', function() {

  var chai        = require('chai');
  var path        = require('path');
  var env         = require(path.join(testDir, 'lib', 'environment'));
  var requirejs   = env.requirejs(staticDir);
  var sinon       = requirejs('js/lib/sinon');
  var fs          = require('fs');
  var server;
  var router;