$8 top-shelf cocktails look as delicious as they taste
http://www.facebook.com/pages/Mister-Lews-Win-Win-Bar-Grand-Sazerac-Emporium/169898556394601
$8 top-shelf cocktails look as delicious as they taste
http://www.facebook.com/pages/Mister-Lews-Win-Win-Bar-Grand-Sazerac-Emporium/169898556394601
[pod_services] [Fri, 22 Jul 2011 05:25:55 +0000] INFO: service[pod-services] not queuing delayed action create on ruby_block[pod-services] (delayed), as it's already been queued | |
: stdout | |
[pod_services] [Fri, 22 Jul 2011 05:25:55 +0000] INFO: service[pod-services] sending create action to ruby_block[pod-services] (delayed) | |
: stdout | |
[pod_services] [Fri, 22 Jul 2011 05:25:55 +0000] INFO: Processing ruby_block[pod-services] action create (pod-services::default line 55) | |
: stdout | |
[pod_services] Loaded suite /usr/local/bin/chef-solo | |
Started: stdout | |
[pod_services] | |
[pod_services] #<Class:0x00000001539f98>::ChefMiniTestRunner::DHCPTest#test_request: : stdout |
/* | |
Play entrance music | |
*/ | |
/* defining a new responder is probably the best way to insulate your hacks from Campfire and Propane */ | |
Campfire.EntranceMusician = Class.create({ | |
initialize: function(chat) { | |
this.chat = chat; | |
case $i in | |
(0) set -- ;; | |
(1) set -- "$args0" ;; | |
(2) set -- "$args0" "$args1" ;; | |
(3) set -- "$args0" "$args1" "$args2" ;; | |
(4) set -- "$args0" "$args1" "$args2" "$args3" ;; | |
(5) set -- "$args0" "$args1" "$args2" "$args3" "$args4" ;; | |
(6) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" ;; | |
(7) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" "$args6" ;; | |
(8) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" "$args6" "$args7" ;; |
#include <stdio.h> | |
#include <stdlib.h> | |
#include <math.h> | |
#include <float.h> | |
int main | |
(int argc | |
,char *ac []){int i, count = argc - 1; | |
double * dvalues=malloc(01- 01+count* | |
sizeof(double)+1); double mi=DBL_MAX,ran=.0,ma =DBL_MIN,mo;for(i= 00; argc>1 | |
&&i<count;i=i+8-7) {double val = atof(ac[i+1]) ;if(23&&val<mi)mi= val;if(val |
#!/usr/bin/env ruby | |
# | |
# Annotate your "bundle outdated" with GitHub compare URLs | |
# | |
require 'open-uri' | |
require 'json' | |
def rubygems_gem_info(gem_name) |
;(function($) { | |
document.addEventListener('click', function(event) { | |
if (event.metaKey || event.altKey) { | |
var link = $(event.target).closest('a[href]') | |
if (link.size()) event.stopPropagation() | |
} | |
}, true) | |
})(jQuery) |
// outdated | |
// see https://github.com/technoweenie/camo.go |
You can now find this packaged up nicely in a rubygem as rollout-zk.
I've implemented a zookeeper-based storage adapter for [rollout][] that does not require any network roundtrips to check if a feature is active for a user.
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.
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.