| eval "$(ssh-agent -s)" | |
| eval ssh-add ~/.ssh/id_rsa | |
| Enter passphrase for /Users/developer/.ssh/id_rsa: | |
| Identity added: /Users/developer/.ssh/id_rsa (/Users/developer/.ssh/id_rsa) | |
| npm install |
| #!/bin/bash | |
| # | |
| # Usage: | |
| # $ echo "host1 host2 host3" | ./sshmany uname -a | |
| # $ cat myservers | ./sshmany echo Hello world | |
| # | |
| cmd="$@" | |
| servers="$(cat)" | |
| i=37 | |
| for server in $servers; do |
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.
I am building a SaaS application and I would like to be able to publish the source code while retaining commercial rights to the application. I did some research and it seems that most popular licenses are not structured to fit this model. I realize this kind of license may not fit with the general spirit of open source, but the alternative for most SaaS companies is that their primary code base is closed source. I am not convinced that has be the case. Why couldn't an app like Github or Basecamp be open source? Why couldn't community members submit pull requests and be paid for their work? There may be valid reasons this model won't work, but I am interested in exploring this further and hearing opinions
| /** | |
| * Module dependencies | |
| */ | |
| var express = require('express'); | |
| var fs = require('fs'); | |
| var mongoose = require('mongoose'); | |
| var Schema = mongoose.Schema; | |
| // img path |
| var http = require('http'); | |
| var sys = require('sys'); | |
| var exec = require('child_process').exec; | |
| var util = require('util'); | |
| var fs = require('fs'); | |
| http.createServer(function(request, response) { | |
| var dummyContent = '<!doctype html><html><head><title>Test</title><meta charset="utf-8"></head><body><p>Hello world!</p></body></html>'; | |
| var htmlFileName = "page.html", pdfFileName = "page.pdf"; | |
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 python | |
| # | |
| # based on XMPPLoggingHandler, Copyright 2011 Calvin Rien, | |
| # based on ExceptionRecordHandler, Copyright 2007 Google Inc. | |
| # | |
| # Licensed under the Apache License, Version 2.0 (the "License"); | |
| # you may not use this file except in compliance with the License. | |
| # You may obtain a copy of the License at | |
| # | |
| # http://www.apache.org/licenses/LICENSE-2.0 |
| <!DOCTYPE html> | |
| <html"> | |
| <head> | |
| <script src="/static/js/jquery.min.js"></script> | |
| <script type="text/javascript" src="http://maps.google.com/maps/api/js?sensor=false"></script> | |
| </head> | |
| <body> | |
| <h2 class="headline">New Talk</h2> | |
