| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <script src="xhrproxy.js"></script> | |
| <script> | |
| setupXHRProxy(); | |
| </script> | |
| </head> |
| function keepTrying(otherArgs, promise) { | |
| promise = promise||new Promise(); | |
| // try doing the important thing | |
| if(success) { | |
| promise.resolve(result); | |
| } else { | |
| setTimeout(function() { | |
| keepTrying(otherArgs, promise); |
| easterEgg.BadWorder.list={ | |
| "4r5e":1, | |
| "5h1t":1, | |
| "5hit":1, | |
| a55:1, | |
| anal:1, | |
| anus:1, | |
| ar5e:1, | |
| arrse:1, | |
| arse:1, |
Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
| /* | |
| * base64.js: An extremely simple implementation of base64 encoding / decoding using node.js Buffers | |
| * | |
| * (C) 2010, Nodejitsu Inc. | |
| * (C) 2011, Cull TV, Inc. | |
| * | |
| */ | |
| var base64 = exports; |
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
This is a post by Joel Spolsky. The original post is linked at the bottom.
This is such a common question here and elsewhere that I will attempt to write the world's most canonical answer to this question. Hopefully in the future when someone on answers.onstartups asks how to split up the ownership of their new company, you can simply point to this answer.
The most important principle: Fairness, and the perception of fairness, is much more valuable than owning a large stake. Almost everything that can go wrong in a startup will go wrong, and one of the biggest things that can go wrong is huge, angry, shouting matches between the founders as to who worked harder, who owns more, whose idea was it anyway, etc. That is why I would always rather split a new company 50-50 with a friend than insist on owning 60% because "it was my idea," or because "I was more experienced" or anything else. Why? Because if I split the company 60-40, the company is going to fail when we argue ourselves to death. And if you ju
| # Build Passes | |
| curl -d "room_id=ourRoom&from=BuildBot&message=Build+Status:+Passing&color=green" https://api.hipchat.com/v1/rooms/message?auth_token=AUTH_TOKEN_HERE&format=json | |
| # Build Fails | |
| curl -d "room_id=ourRoom&from=BuildBot&message=Build+Status:+Failing&color=red¬ify=1" https://api.hipchat.com/v1/rooms/message?auth_token=AUTH_TOKEN_HERE&format=json |
| #!/bin/bash | |
| ## combines multiple js files into main.js for deploying to parse | |
| ## Your separate js files should be in a directory 'source' that | |
| ## is at the same level as the 'cloud' and 'config' directories | |
| ## parse uses. | |
| cat source/*.js > cloud/main.js | |
| ## deploy | |
| parse deploy |
| // more information here: http://blog.tomtasche.at/2012/10/use-built-in-feedback-mechanism-on.html | |
| try { | |
| int i = 3 / 0; | |
| } catch (Exception e) { | |
| ApplicationErrorReport report = new ApplicationErrorReport(); | |
| report.packageName = report.processName = getApplication() | |
| .getPackageName(); | |
| report.time = System.currentTimeMillis(); | |
| report.type = ApplicationErrorReport.TYPE_CRASH; |
