erikbern

def get_n_results_dumb(q):
    r = requests.get('http://www.google.com/search',
                     params={'q': q,
                             "tbs": "li:1"})
    r.raise_for_status()
    soup = bs4.BeautifulSoup(r.text)
    s = soup.find('div', {'id': 'resultStats'}).text
    if not s:
        return 0
    m = re.search(r'([0-9,]+)', s)

mbbx6spp

Alternatives to the "Atlassian Stack"

Fuller stack alternatives (replaces at least two of the Atlassian stack)

• Phabricator

• Github

• Gitlab

• Taiga

• Redmine

MaksimAbramchuk

To circle.yml:

dependencies:
  post:
    - bin/cisetup

checkout:
  post:
    - git fetch origin --depth=1000000

jsteiner

RSpec.configure do |config|
  config.before(:suite) do
    DatabaseCleaner.clean_with(:truncation)
  end

  config.before(:each) do
    DatabaseCleaner.strategy = :transaction
  end

  config.before(:each, js: true) do

alex-zige

Rails Rspec APIs Testing Notes

Folders Structure

  spec
  |--- apis #do not put into controllers folder. 
        |--- your_api_test_spec.rb  
  |--- controllers
  |--- models
  |--- factories
 |--- views

domenic

module.exports = and ES6 Module Interop in Node.js

The question: how can we use ES6 modules in Node.js, where modules-as-functions is very common? That is, given a future in which V8 supports ES6 modules:

• How can authors of function-modules convert to ES6 export syntax, without breaking consumers that do require("function-module")()?
• How can consumers of function-modules use ES6 import syntax, while not demanding that the module author rewrites his code to ES6 export?

@wycats showed me a solution. It involves hooking into the loader API to do some rewriting, and using a distinguished name for the single export.

This is me eating crow for lots of false statements I've made all over Twitter today. Here it goes.

nickawalsh

@import compass

$icons: sprite-map("icons/*.png")
$icons-hd: sprite-map("icons-hd/*.png")

i
  background: $icons
  display: inline-block
  @media (-webkit-min-device-pixel-ratio: 1.5), (min-resolution: 144dpi)
    background: $icons-hd

mdigital

// backbone.js continues to impress, I needed to get data from a jsonp api
// I really wanted to do this the "right" backbone.js way and create a model and call fetch. 
// But the default backbone synch is not jsonp
// Turns out you can override a synch on a per model basis (thanks stackoverflow)
// whats nice is backbone.js continue to work as expected with the override

// here's a snippet (some changes to protect our privacy). An improvement could be to create a jsonp model class which MyModel inherits 
// the synch function is most important below, that's what tells backbone it's jsonp

MyModel = Backbone.Model.extend({

elia

#!/usr/bin/env bash
# coding: utf-8

# PROMPT

# more compact
# export PS1="\u@\h\w$ "
# export PS1=">: "                  # LOST style
# export PS1='> '                   # Terminal Icon style

joefiorini

require 'units/spec_helper'
require 'reviews_controller'

class Review; end

describe ReviewsController do

  let(:controller) { ReviewsController.new }

  it { should expose :reviews }