sabondano

Keybase proof

I hereby claim:

• I am sabondano on github.
• I am sabondano (https://keybase.io/sabondano) on keybase.
• I have a public key ASCurpMNgn5-0C9sacs8M1LcmBo0ARo0SlNqprtJivFN8Qo

To claim this, I am signing this object:

sabondano

function Robot(name, programmingLanguage) {
  this.name = name;
  this.language = programmingLanguage;
}

Robot.prototype.sayHello = function () {
  console.log(`My name is ${this.name} and I like to program in ${this.language}.`)
}

function FancyRobot(name, programmingLanguage) {

sabondano

function countdown(seconds, callback){
  var i = setInterval(function() { 
    callback(seconds--); 
      if (seconds === -1) {
        clearInterval(i);
      } 
    ;}, 1000);
}

// countdown(5);

sabondano

function echo() {
  _.forEach(arguments, function(element){ console.log(element)});
}

echo("one");


/*
function echo2() {
  for (var i = 0; i < arguments.length; i++) {

sabondano

function echo(myArray) {
  if (myArray !== undefined) {
    myArray.forEach(function(element) {
      console.log(element);
    });
  }
}

echo();
echo(['one']);

sabondano

Three Git Workflow Tips For Beginners

After you've mastered the basic git commands (init, push, pull, fetch, merge, branch, checkout, log, etc) and the basic GitHub features, you'll be able to contribute more to your teams and build more sustainable/better software if you internalize the following simple git workflow tips.

Write Well Formed Commit Messages

Subject line / summary: The subject line is the first line on your git commit message. It should be capitalized and short (50 chars max). It should be followed by a blank line and serve as a summary of the changes logged by the commit.

Body: Include details that don't fit in the summary and wrap it to 72 columns. (if using vim do :set textwidth=72) Explain here the why behind your commit. The changes (the what) can be seen in the commit itself. Avoid writing a list of all the changes that are being introduced. If future you or your colleagues want to see the changes, they can do that, you don't have to list the changes here for that to be p

sabondano

Programming Greatness Isn't Born. It's Grown.

Why is programming greatness important?

In a previously lost interview from 1995 Steve Jobs explained the difference between the best software developers and average ones:

In most businesses, the difference between average and good is at best 2 to 1, right? Like, if you go to New York and you get the best cab driver in the city, you might get there 30% faster than with an average taxicab driver. A 2 to 1 gain would be pretty big.

The difference between the best worker on computer hard-ware and the average may be 2 to 1, if you're lucky. With automobiles, maybe 2 to 1. But in software, it's at least 25 to 1. The difference between the average programmer and a great one is at least that.

The secret of my success is that we have gone to exceptional lengths to hire the best people in the world. And when you're in a field where the dynamic range is 25 to 1, boy, does it pay off.

sabondano

# Programming Greatness Isn't Born. It's Grown.

## Why is programming greatness important?

In a previously lost interview from 1995 Steve Jobs explained the difference between the best software developers and average ones:
> "In most businesses, the difference between average and good is at best 2 to 1, right? Like, if you go to New York and you get the best cab driver in the city, you might get there 30% faster than with an average taxicab driver. A 2 to 1 gain would be pretty big.
>
> The difference between the best worker on computer hard-ware and the average may be 2 to 1, if you're lucky. With automobiles, maybe 2 to 1. But in software, it's at least 25 to 1. The difference between the average programmer and a great one is at least that.
>
> The secret of my success is that we have gone to exceptional lengths to hire the best people in the world. And when you're in a field where the dynamic range is 25 to 1, boy, does it pay off."

sabondano

# get a path to the data that doesn't
csvs_dir = File.expand_path('data', __dir__)

# load the code
require 'sales_engine'
engine = SalesEngine.new(csvs_dir)

# load the csvs
engine.startup