nzakas

I'm doing some research on how companies use GitHub Enterprise (or public GitHub) internally. If you can help out by answering a few questions, I'd greatly appreciate it.

1. What is the primary setup? Is there an organization and each official repo is owned by that organization?
2. Does every engineer have a fork of each repo they're working on?
3. Are engineers allowed to push directly to the official repo? Or must all commits go through a pull request?
4. Do engineers work on feature branches on the main repo or on their own forks?
5. Do you require engineers to squash commits and rebase before merging?
6. Overall, what is the workflow for getting a new commit into the main repository?
7. What sort of hooks do you make use of?
8. Are there any ops issues you encountered? (Scaling, unforeseen downtime, etc.)

visnup

Today I shall remember what new does

It does exactly this:

function New(constructor) {
  // create a new object, with it's prototype set to the constructor's `prototype`
  var obj = Object.create(constructor.prototype);
  
 // call the constructor function, with `this` set to the new object

dypsilon

Rich Text Editing

External Links

• WYSIWYG HTML
  • TinyMCE
    • looks like bootstrap
    • license: LGPL
    • integrates with Plupload for file uploading (PHP only)
• integrates with MoxieManager for file management (PHP only)

Olical

/**
 * Performs a binary search on the host array. This method can either be
 * injected into Array.prototype or called with a specified scope like this:
 * binaryIndexOf.call(someArray, searchElement);
 *
 * @param {*} searchElement The item to search for within the array.
 * @return {Number} The index of the element which defaults to -1 when not found.
 */
function binaryIndexOf(searchElement) {
	'use strict';

quirkey

#!/bin/bash

# Bandwidth throttling for OSX,
# http://www.macosxhints.com/article.php?story=20080119112509736

case "$1" in
  'start')
    KB=$2
    echo Throttling at $KB Kbytes/s
    sudo ipfw pipe 1 config bw "$KB"KByte/s

pid

# Improving the security of your SSH private key files (
# Better key protection with PKCS#8
# http://martin.kleppmann.com/2013/05/24/improving-security-of-ssh-private-keys.html

mv ~/.ssh/id_rsa ~/.ssh/id_rsa.old
openssl pkcs8 -topk8 -v2 des3 -in ~/.ssh/id_rsa.old -out ~/.ssh/id_rsa
chmod 600 ~/.ssh/id_rsa
# Check that the converted key works; if yes, delete the old one:
rm ~/.ssh/id_rsa.old

dypsilon

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

---

dypsilon

Backend Development

• node.js
  • Installation paths: use one of these techniques to install node and npm without having to sudo.
  • Node.js HOWTO: Install Node+NPM as user (not root) under Unix OSes
  • Felix's Node.js Guide
  • Creating a REST API using Node.js, Express, and MongoDB
  • Node Cellar Sample Application with Backbone.js, Twitter Bootstrap, Node.js, Express, and MongoDB
  • JavaScript Event Loop
• Node.js for PHP programmers

willurd

This is a small collection of scripts showing how to use require.js. It's only one of several ways of setting up a require.js project, but it's enough to get started.

At its core, require.js is about three things:

1. Dependency management
2. Modularity
3. Dynamic script loading

The following files show how these are achieved.

jgable

var fs = require('fs'),
    path = require('path'),
    _ = require('underscore'),
    when = require('when'),
    express = require('express'),
    GhostPlugin = require('../../../core/server/plugins/GhostPlugin'),
    knex = require('../../../core/server/models/base').Knex,
    KudosPlugin;

KudosPlugin = function (ghost) {