rreinhardt9

class Bsearch

  def initialize(dictionary)
    @dictionary = Array(dictionary)
  end

  def search(value)
    search_in_chunk(@dictionary, value)
  end

joshmfrankel

#!/bin/bash

# Add Repos
echo ""
echo "============================="
echo "  Adding Third-party Repos   "
echo "============================="
echo ""

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys BBEBDCB318AD50EC6865090613B00F1FD2C19886

joshmfrankel

# NFSD for vagrant
sudo apt-get install nfs-common nfs-kernel-server

# Mouse Flickering
# I had the same problem. You can fix it manually. Open System Settings > Displays. In the Displays window, you will see an Unknown monitor. Click it and disable it.

# libcrypt fix for spotify
https://launchpad.net/ubuntu/+archive/primary/+files/libgcrypt11_1.5.3-2ubuntu4.2_amd64.deb

# Fix login shell bug with gconf-editor

PatrickJS

var EventEmitter = require('events').EventEmitter;
var _ = require('lodash');

// Factory shared
var makePerson = function() {
  var person = {};
  EventEmitter.call(person);
  person.wallet = 0;
  _.extend(person, personMethods)
  return person;

speric

Chapter 1 - Object Oriented Design

The purpose of design is to allow you to do design later, and it's primary goal is to reduce the cost of change.

SOLID Design:

• Single Responsibility Principle: a class should have only a single responsibility
• Open-Closed Principle: Software entities should be open for extension, but closed for modification (inherit instead of modifying existing classes).
• Liskov Substitution: Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
• Interface Segregation: Many client-specific interfaces are better than one general-purpose interface.

Integralist

Rules for good testing

Look at the following image...

...it shows an object being tested.

You can't see inside the object. All you can do is send it messages. This is an important point to make because we should be "testing the interface, and NOT the implementation" - doing so will allow us to change the implementation without causing our tests to break.