Skip to content

Instantly share code, notes, and snippets.

View adamwiggins's full-sized avatar

Adam Wiggins adamwiggins

View GitHub Profile
adamwiggins /
Created September 9, 2016 15:07
Keybase proof

Please publicly post the following Gist, and name it

Keybase proof

I hereby claim:

  • I am adamwiggins on github.
  • I am adamwiggins ( on keybase.
  • I have a public key ASCSw8hgZLEfeQSMT7V4bEn51DCKl71kscxP4gUUiCFBFgo
adamwiggins / Gemfile
Created November 18, 2013 23:27
Raspberry Pi sample program
source ""
gem 'sinatra'
adamwiggins / roku-curl.txt
Created November 9, 2013 22:26
Roku API query example
$ curl
<app id="12" version="3.1.6014">Netflix</app>
<app id="13" version="4.10.13">Amazon Instant Video</app>
<app id="2016" version="3.2.7">Crackle</app>
<app id="2285" version="2.7.6">Hulu Plus</app>
<app id="13842" version="1.3.2">VUDU</app>
<app id="28" version="3.1.7">Pandora</app>
adamwiggins /
Last active November 24, 2022 11:40
End of a chapter: my Heroku departure message

It's with a heavy heart that I announce that Friday, May 31 2013 will be my last day at Heroku.

How can I possibly put into words what Heroku has meant to me these last six years? I can say it was a tremendous experience; or the opportunity of a lifetime; or the greatest thing I have ever been a part of. I can say that Heroku has been my life's work, as I did recently in a public blog post. All of those things are true, but none seem to capture the enormity of what's transpired these past six years.

I tend to focus on mechanical elements of a company: product, code, design, process. But what has surprised me the most at Heroku is that none of these things is the best part. The best part is the team.

I've never had the chance to work with a more singular group of people. Talented, passionate, skilled, dedicated. Most of all, sharing a set of values: elegance, craft, maniacal focus on simplicity; and an uncompromising belief that the future will be made of software, and how that software gets made will shape

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

source :gemcutter
gem 'sinatra', '1.2.1'
gem 'thin', '1.2.11'
valkyrie:~$ heroku
=== General Commands
help # show this usage
version # show the gem version
list # list your apps
create [<name>] # create a new app
keys # show your user's public keys
source :gemcutter
gem 'sinatra', '1.0'
director routing_mesh round-robin {
.backend = {
.host = "...some ip...";
.port = "...some port...";
.first_byte_timeout = 90s;
.between_bytes_timeout = 90s;
# ...more backends...
#!/usr/bin/env ruby
require 'aws/s3'
class S3Cmd
include AWS::S3
def initialize
:access_key_id => ENV['AWS_ACCESS_KEY_ID'],