Loosely ordered with the commands I use most towards the top. Sublime also offer full documentation.
| ⌘+X | delete line |
| ⌘+↩ | insert line after |
| ⌘+⇧+↩ | insert line before |
| ⌘+⇧+↑ | move line (or selection) up |
| Request.Twitter = new Class({ | |
| Extends: Request.JSONP, | |
| options: { | |
| linkify: true, | |
| url: 'http://twitter.com/statuses/user_timeline/{term}.json', | |
| data: { | |
| count: 5 | |
| } |
Loosely ordered with the commands I use most towards the top. Sublime also offer full documentation.
| ⌘+X | delete line |
| ⌘+↩ | insert line after |
| ⌘+⇧+↩ | insert line before |
| ⌘+⇧+↑ | move line (or selection) up |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".
| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |
| // ==UserScript== | |
| // @name AWS UI scrubber | |
| // @namespace https://github.com/jamesinc | |
| // @version 1.0 | |
| // @description Make AWS Console shortcuts take up less space | |
| // @author James Ducker | |
| // @match https://*.console.aws.amazon.com/* | |
| // @grant none | |
| // @run-at document-end | |
| // ==/UserScript== |
http://thenewstack.io/monitoring-101-collecting-right-data/
Metrics capture a value pertaining to your systems at a specific point in time.
Metrics are usually collected once per second, one per minute, or at another regular interval to monitor a system over time.
For different Metric Data Types and the metric names they produce see https://docs.datadoghq.com/developers/metrics/types/?tab=histogram#metric-types