Backstory: I decided to crowdsource static site generator recommendations, so the following are actual real world suggested-to-me results. I then took those and sorted them by language/server and, just for a decent relative metric, their Github Watcher count. If you want a heap of other projects (including other languages like Haskell and Python) Nanoc has the mother of all site generator lists. If you recommend another one, by all means add a comment.
// | |
// KDPersistantCache.h | |
// KDPrototype | |
// Stores NSCoding compliant objects persistantly in the NSCachesDirectory | |
// for a specified period of time. | |
// | |
// Created by on 18/04/2012. | |
// Copyright (c) 2012 __MyCompanyName__. All rights reserved. | |
// |
authors: | |
hanzou: | |
name: Hanzou Hattori | |
display_name: Hanzou | |
gravatar: c66919cb194f96c696c1da0c47354a6a | |
email: [email protected] | |
web: http://company.com | |
twitter: company | |
github: hhattori | |
jorgen: |
YARD CHEATSHEET http://yardoc.org
May 2020 - updated fork: https://gist.github.com/phansch/db18a595d2f5f1ef16646af72fe1fb0e
cribbed from http://pastebin.com/xgzeAmBn
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
This is a barebones GYP file to compile 1 C source file. We are demonstrating that the cflags
parameter in gyp files gets completely ignored :(
$ ../gyp/gyp -f make --depth=. hello.gyp
$ V=1 make
cc -fasm-blocks -mpascal-strings -Os -gdwarf-2 -MMD -MF out/Default/.deps/out/Default/obj.target/hello/hello.o.d.raw -c -o out/Default/obj.target/hello/hello.o hello.c
./gyp-mac-tool flock out/Default/linker.lock g++ -Lout/Default -o "out/Default/hello" out/Default/obj.target/hello/hello.o
LINK(target) out/Default/hello: Finished
# ... | |
gem 'carrierwave' | |
gem 'fog', '~> 1.0.0' # Need to specify version, as carrierwave references older (0.9.0) which doesn't allow configuration of Rackspace UK Auth URL |
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