| /* This function runs when the spreadsheet is opened and populates a menu option | |
| labelled Zendesk that contains two options (7 days and 30 days) which are tied | |
| to the listed functions | |
| */ | |
| function onOpen() { | |
| var sheet = SpreadsheetApp.getActiveSpreadsheet(); | |
| var entries = [{ | |
| name : "Pull Satisfaction Data (last 7 days, rolling)", | |
| functionName : "getSatisfactionDataLast7" |
Slack doesn't provide an easy way to extract custom emoji from a team. (Especially teams with thousands of custom emoji) This Gist walks you through a relatively simple approach to get your emoji out.
If you're an admin of your own team, you can get the list of emoji directly using this API: https://api.slack.com/methods/emoji.list. Once you have it, skip to Step 3
HOWEVER! This gist is intended for people who don't have admin access, nor access tokens for using that list.
Follow along...
Peter Naur's classic 1985 essay "Programming as Theory Building" argues that a program is not its source code. A program is a shared mental construct (he uses the word theory) that lives in the minds of the people who work on it. If you lose the people, you lose the program. The code is merely a written representation of the program, and it's lossy, so you can't reconstruct
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
I hereby claim:
To claim this, I am signing this object:
| Team Usage | Cost Before | Cost Now |
|---|---|---|
| 1 repo, 5 users | $25 | $25 |
| 1 repo, 10 users | $25 | $70 |
| 11 repos, 5 users | $50 | $25 |
| 11 repos, 10 users | $50 | $70 |
| 5 repos, 50 users | $25 | $430 |
| 50 repos, 5 users | $100 | $25 |
| 50 repos, 50 users | $100 | $430 |
| class Roro | |
| def initialize(host, speakers = []) | |
| @host = host | |
| @speakers = speakers | |
| end | |
| def start | |
| @host.speak | |
| end | |
| end |
| Original text here: http://www.heartmindcode.com/blog/2013/08/loyalty-and-layoffs/ |
| #!/usr/bin/env ruby | |
| gem "parser", "~> 1.4" | |
| require "parser" | |
| require "parser/ruby19" | |
| require "set" | |
| class ConstantDeclarationAndUseProcessor < Parser::AST::Processor | |
| attr_reader :declared, :used | |
| def initialize |
