beelarr

#!/usr/bin/env python
from bs4 import BeautifulSoup
from twilio.rest import TwilioRestClient
import json
import os
import re
import requests


url = 'https://postmates.com/los-angeles'

beelarr

#!/usr/bin/env python
from bs4 import BeautifulSoup
from twilio.rest import TwilioRestClient
import json
import os
import re
import requests


url = 'https://postmates.com/los-angeles'

beelarr

git rm -r --cached node_modules
git commit -m 'Remove the now ignored directory node_modules'
git push origin master

beelarr

Box 3.1. Undoing things Even when you’re very careful, things can sometimes go wrong when developing Rails applications. Happily, Rails has some facilities to help you recover.

One common scenario is wanting to undo code generation—for example, when you change your mind on the name of a controller and want to eliminate the generated files. Because Rails creates a substantial number of auxiliary files along with the controller (as seen in Listing 3.6), this isn’t as easy as removing the controller file itself; undoing the generation means removing not only the principal generated file, but all the ancillary files as well. (In fact, as we saw in Section 2.2 and Section 2.3, rails generate can make automatic edits to the routes.rb file, which we also want to undo automatically.) In Rails, this can be accomplished with rails destroy followed by the name of the generated element. In particular, these two commands cancel each other out:

rails generate controller StaticPages home help

beelarr

Originally published in June 2008

When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.

To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.

What to expect

Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.

beelarr

def fibonacci(n)
   n <= 1 ? n :  fibonacci( n - 1 ) + fibonacci( n - 2 ) 
end
puts fibonacci( 10 )

beelarr

//  Write an efficient method that takes stock_prices_yesterday and returns the best profit I could have made from 1 purchase and 1 sale of 1 Apple stock yesterday.

stock_prices = [12, 10, 7, 5, 8, 11, 9]

def get_max_profit quote
  min_price = quote[0]
  max_profit = min_price - quote[1]
  
  quote.each_with_index do |price, index|
    next if price.zero?

beelarr

Make great software and the tooling and learning will come.  

// Event Delegation

An event listener is fired on all child elements (event bubbling)
An event listener is fired on all parent elements (bubble up)

Target is what was actually clicked
Current Target is what the event listener is attached to
///////////////////////////////////////////////////////////

beelarr

// What is a class?
- They hold data
- They have methods that interact with that data
- They instantiate objects

// What is an object?
- An instance of a class
- Classes descend from the Object root class

// What is a module?

beelarr

SOLID

Single Responsibility Principle - class should have one job 
Open Closed Principle - Objects should be OPEN for extension but closed for modification
Liskov Substitution Principle - can a subtype substitute for a base type 
  -- if S is a subtype of T, then objects of type T may be replaced with objects of type S
Interface Segregation Principle - “many client-specific interfaces are better than one general-purpose interface--no client should be forced to depend on methods it does not use
Dependency Inversion Principle - High-level modules should not depend on low-level modules. Both should depend on abstractions.

/////////////////////////////////////////////