- type
- state
- status
- data (yes, and datum, datas, etc.)
- correct, especially in tests. What is correctness in this context?
- object
ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats
| #!/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 |
| # | |
| # Working with branches | |
| # | |
| # Get the current branch name (not so useful in itself, but used in | |
| # other aliases) | |
| branch-name = "!git rev-parse --abbrev-ref HEAD" | |
| # Push the current branch to the remote "origin", and set it to track | |
| # the upstream branch | |
| publish = "!git push -u origin $(git branch-name)" |
Based on Mislav's gist and vim-tmux-navigator.
Since tmux hosts vim I disliked that I had to install a vim plugin for this. Instead I think it's cleaner to control vim from tmux.
My actual goal was to achive the following behaviour though (I have a default setup similar to the one Mislav shows in the gist. Two vertically split tmux panes, where the left one hosts vim, which has two vertically split windows):
- On the leftmost window in vim: when I hit
C-h(do not wrap to the rightmost tmux pane, but) zoom the left tmux pane. - On the rightmost tmux pane: when I hit
C-l(do not wrap to the leftmost tmux pane, but) zoom the right tmux pane. - All other navigation: work as given in Mislav's gist
Discourse http://www.discourse.org
Mini Profiler https://github.com/miniprofiler/rack-mini-profiler
rbtrace https://github.com/tmm1/rbtrace
memory_profiler https://github.com/SamSaffron/memory_profiler
fast_stack: https://github.com/SamSaffron/fast_stack
| # | |
| # CORS header support | |
| # | |
| # One way to use this is by placing it into a file called "cors_support" | |
| # under your Nginx configuration directory and placing the following | |
| # statement inside your **location** block(s): | |
| # | |
| # include cors_support; | |
| # | |
| # As of Nginx 1.7.5, add_header supports an "always" parameter which |
| module Reportable | |
| extend ActiveSupport::Concern | |
| module ClassMethods | |
| # Chain on a scope and specify the fields to extract. | |
| # Example: | |
| # User.enabled.report %{ | |
| # :email_opt_in, | |
| # 'created_at as sign_up_date' | |
| # } |
Update: We had meetups in London and Dortmund, Germany
Tuesday 11 March
7:30pm
Shoreditch Village Hall
The prep-script.sh will setup the latest Node and install the latest perf version on your Linux box.
When you want to generate the flame graph, run the following (folder locations taken from install script):
sudo sysctl kernel.kptr_restrict=0
# May also have to do the following:
# (additional reading http://unix.stackexchange.com/questions/14227/do-i-need-root-admin-permissions-to-run-userspace-perf-tool-perf-events-ar )
sudo sysctl kernel.perf_event_paranoid=0