This is now an actual repo:
set :application, "example.com" | |
set :deploy_to, "/var/www/#{application}" | |
role :app, "example.com" | |
role :web, "example.com" | |
role :db, "example.com", :primary => true | |
set :scm, :git | |
set :repository, "ssh://shay@example.com/git/example.com" | |
set :branch, "origin/master" |
#!/bin/bash | |
dir="/Users/dave/Sites/" | |
project="" | |
# Check for Git | |
type -P git &>/dev/null || { echo "Git is not installed. Exiting." >&2; exit 1; } | |
# Get a project name | |
while [ -z "$project" ] | |
do |
<?PHP | |
// Generates a strong password of N length containing at least one lower case letter, | |
// one uppercase letter, one digit, and one special character. The remaining characters | |
// in the password are chosen at random from those four sets. | |
// | |
// The available characters in each set are user friendly - there are no ambiguous | |
// characters such as i, l, 1, o, 0, etc. This, coupled with the $add_dashes option, | |
// makes it much easier for users to manually type or speak their passwords. | |
// | |
// Note: the $add_dashes option will increase the length of the password by |
<!DOCTYPE html> | |
<!-- Helpful things to keep in your <head/> | |
// Brian Blakely, 360i | |
// http://twitter.com/brianblakely/ | |
--> | |
<head> | |
<!-- Disable automatic DNS prefetching. | |
#!/bin/sh | |
# have submodules been added? | |
MODS=0 | |
# Github base URL | |
GITHUB="https://github.com" | |
# Default branch | |
DEFAULT_BRANCH="3.0/master" |
<!DOCTYPE html> | |
<html> | |
<head> | |
<title>LABjs Demo</title> | |
<script src="/js/queue.LAB.js"></script> | |
<script> | |
// adding `false` in the queue will signifiy an empty .wait() in the $LAB chain | |
$LAB.queue("http://ajax.googleapis.com/ajax/libs/jquery/1.4.3/jquery.min.js", false); | |
$LAB.queue("http://ajax.googleapis.com/ajax/libs/jqueryui/1.8.6/jquery-ui.min.js", false); |
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
#!/usr/bin/env ruby | |
# watch.rb by Brett Terpstra, 2011 <http://brettterpstra.com> | |
# with credit to Carlo Zottmann <https://github.com/carlo/haml-sass-file-watcher> | |
# original by Brett Terpstra <http://brettterpstra.com/watch-for-file-changes-and-refresh-your-browser-automatically/> | |
# fork by Vaclav Vancura / SAY Media <http://saymedia.com> | |
trap("SIGINT") { exit } | |
filetypes = ['less'] | |
watch_folder = 'content/media/less' |