taylor-smith

{
        "key": "cmd+1",
        "command": "workbench.action.openEditorAtIndex1"
    },
    {
        "key": "cmd+2",
        "command": "workbench.action.openEditorAtIndex2"
    },
    {
        "key": "cmd+3",

taylor-smith

var myLib = (function() {
    // Using IIFE + Closure
    var $cachedLookup = $('.element');

    function hideCachedElement() {
        $cachedLookup.hide();
    }

    return {
        hide: hideCachedElement

taylor-smith

validate: function(attrs, options){
		if (attrs.data[0].value === null ||
			attrs.data[1].value === null ||
			attrs.data[2].value === null ||
			attrs.data[3].value === null ||
			attrs.data[4].value === null ||
			attrs.data[5].value === null ||
			attrs.data[6].value === null ||
			attrs.data[7].value === null ||
			attrs.data[8].value === null ||

taylor-smith

var TodoItem = Backbone.Model.extend({});


var TodoView = Backbone.View.extend({
  render: function(){
    var html = '<h3>' + this.model.get('description') + '</h3>'
    this.$el.html(html);
    return this;
  }
});

taylor-smith

namespace :type_of_task do
  task :name_of_task => [:task_dependency] do
    puts "I Work!"
  end

  task :task_dependency do
    puts "I am working as well!"
  end
end

taylor-smith

require 'sqlite3'


namespace :type_of_task do
  task :name_of_task => [:task_dependency] do
    puts "I Work!"
  end
end

namespace :db do

taylor-smith

* Pair programming vs pair learning
	* pair learning: use two computers, get a chance to get some muscle memory going, but also interact with each other to reinforce the concepts. **Even if you find a concept easy to accomplish, there is undoubtedly reinforcing you can do.**
	* pair programming: use **one** computer, you should have one keyboard between two people, and one monitor/laptop. Decide who will be "driving" and who will be "navigating"
		* driver: your goal is to write code. You should be spending most of your time doing one of two things, writing code based on your discussions with the navigator, or discussing/researching what to write along with the navigator
		* navigator: your goal is to keep the driver writing good code, or discussing what could be done to enable writing good code. You might think of the steps necessary to complete the task at hand, and what files/external resources might be the next thing to do. On top of this, you should be looking out for syntax and logic errors to help miti

taylor-smith

from http://www.rubular.com/r/PySQB8NvUY

(?:\s|^)(?:#(?!(?:\d+|\w+?_|_\w+?)(?:\s|$)))(\w+)(?=\s|$)

Test String:
#blah Pack my #box with #5 dozen #good2 #3good liquor.#jugs link.com/liquor#jugs #mkvef214asdwq sd #3e4 flsd #2good #_hello and #hello_ , how to just allow #hello2_world or #hello_23 #first#second #3


Match 1
1.	blah

taylor-smith

{
	"color_scheme": "Packages/flatland-mks/Flatland-MKS.tmTheme",
	"ensure_newline_at_eof_on_save": true,
	"file_exclude_patterns":
	[
		".DS_Store"
	],
	"folder_exclude_patterns":
	[
		".bundle",

taylor-smith

'default': 'disk',

  // Persistent adapter for DEVELOPMENT ONLY
  // (data is preserved when the server shuts down)
  disk: {
    module: 'sails-disk'
  },