graingerkid

SELECT
  t.landing_page, t.all_impressions
FROM 
  landing_pages_client_v3 AS t
JOIN 
(
  SELECT
    landing_page, 
    MAX(all_impressions) AS max_all_impressions
  FROM landing_pages_client_v3

graingerkid

SELECT
  t.landing_page, t.all_impressions
FROM 
  landing_pages_client_v3 AS t
JOIN 
(
  SELECT
    landing_page, 
    MAX(all_impressions) AS max_all_impressions
  FROM landing_pages_client_v3

graingerkid

SELECT
  t.landing_page, t.all_impressions
FROM 
  landing_pages_client_v3 AS t
JOIN 
(
  SELECT
    landing_page, 
    MAX(all_impressions) AS max_all_impressions
  FROM landing_pages_client_v3

graingerkid

from pqueue import PersistentQueue

q1 = PersistentQueue("/tmp/queue_storage_dir")
q1.put("1")
q1.put("2")
q1.put("3")
q1.close()

q2 = PersistentQueue("/tmp/queue_storage_dir")
while not q2.empty():

graingerkid

from twython import Twython # pip install twython
import time # standard lib

''' Go to https://apps.twitter.com/ to register your app to get your api keys '''
CONSUMER_KEY = ''
CONSUMER_SECRET = ''
ACCESS_KEY = ''
ACCESS_SECRET = ''

twitter = Twython(CONSUMER_KEY,CONSUMER_SECRET,ACCESS_KEY,ACCESS_SECRET)

graingerkid

>>> import requests
>>> import time
>>> import webbrowser
>>> while True:
...     r=requests.get('https://www.example.co.uk/')
...     if r.status_code == 200:
...         webbrowser.open('https://www.example.co.uk/')
...     else:
...         pass
...     time.sleep(10)

graingerkid

There are many Git workflows out there, I heavily suggest also reading the atlassian.com [Git Workflow][article] article as there is more detail then presented here.

The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.

When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].

Basic branching

When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.

graingerkid

def read_log(log):
    '''
    Returns generator from log files - typically gb of data.
    This allows a better performance due to memory issues of 
    returning the entire file.
    '''
    with open(log) as f:
        # opens log file
        for i in f:
            yield i

graingerkid

def last_50(generator, n):
    '''
    Takes a generator object and returns 
    a specified number (n) into a list.
    '''
    counter = 0
    results = []
    for i in generator:
        if counter == n:
            break

graingerkid

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console