pushpak

/**
 * Inspired by AngularJS' implementation of "click dblclick mousedown..." 
 *
 * This ties in the Hammer events to attributes like:
 * 
 *   hm-tap="add_something()"
 *   hm-swipe="remove_something()"
 *
 * and also has support for Hammer options with:
 *

pushpak

var migrationManager = (function() {

  /**
   * Our db instance
   * @type {Database}
   */
  var db = null;

  /**
   * Our versions, add a version when needed

pushpak

#!/usr/bin/perl
#
# Eric Jiang
# http://notes.ericjiang.com/posts/54
# This software is public domain.
#
use bytes;

my $data;

pushpak

Never Expose DB Results Directly

1. If you rename a field, then your users are fucked. Convert with a hardcoded array structure.
2. Most DB drivers [for PHP] will show integers as numeric strings and false as "0", so you want to typecast them.
3. Unless you're using an ORM with "hidden" functionality, people will see passwords, salts and all sorts of fancy codes. If you add one and forget to put it in your $hidden array then OOPS!

Use the URI sparingly, and correctly

1. Use the query string for paired params instead of /users/id/5/active/true. Your API does not need to be SEO optimised.
2. ?format=xml is stupid, use an Accept: application/xml header. I added this to the CodeIgniter Rest Server once for lazy people, and now people think it's a thing. It's not.

pushpak

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

pushpak

#!/usr/bin/env bash

# Upgrade Base Packages
sudo apt-get update
sudo apt-get upgrade -y

# Install Web Packages
sudo apt-get install -y build-essential dkms re2c apache2 php5 php5-dev php-pear php5-xdebug php5-apcu php5-json php5-sqlite \
php5-mysql php5-pgsql php5-gd curl php5-curl memcached php5-memcached libmcrypt4 php5-mcrypt postgresql redis-server beanstalkd \
openssh-server git vim python2.7-dev

pushpak

Business Models

Advertising

Models	Examples
Display ads	Yahoo!
Search ads	Google

pushpak

(function() {
  window.frame = require("nw.gui").Window.get();
  window.frame.isFocused = true;

  var windowFocusHandler = function() {
      window.frame.isFocused = true;
    }
    , windowBlurHandler = function() {
      window.frame.isFocused = false;

pushpak

var port = 0;
var endpoint = 0x01;
var device = { vendorId: 0x04b8, productId: 0x0202};

var connect = function(callback) {
  chrome.permissions.getAll(function(p) {
    if (p.permissions.indexOf('usb') >= 0) {

      //construct permission object for our device
      var obj = { usbDevices: [device] };

pushpak

#
# Wide-open CORS config for nginx
#
location / {

     if ($request_method = 'OPTIONS') {

        add_header 'Access-Control-Allow-Origin' '*';
        
        #