rsms

// HTTP client for testing high connection concurrency
// Authors: Richard Jones and Rasmus Andersson
// Released in the public domain. No restrictions, no support.
#include <sys/types.h>
#include <sys/time.h>
#include <sys/queue.h>
#include <stdlib.h>
#include <err.h>
#include <event.h>
#include <evhttp.h>

sydcurie

#Formating options for .h / .m

##File

###Rules

• No EmptyLine at begining of file
• No EmptyLine at end of file
• Must start with FileCommentBlock
• Must end with @end

sydcurie

#Objective-C Style Guide ##Comments ###General Info Block comments /**/ should be avoided in favor of // (though they are not banned).

Inside comments, references to variables, classes and protocols should be surrounded by |.

// This class is responsible for keeping up to date a list of |Item| objects.

cassioeskelsen

DISCLAIMER: pessoalmente não serei atingido pela criação do conselho, 
            minha opinião não é em "defesa de meus interesses""

1. "TI" se faz principalmente nos países do chamado "Primeiro Mundo": Inglaterra, EUA, Japão, 
   China(ok, esse não é bem 1o. Mundo), Coréia do Sul, Finlândia, etc. Nesses países não existe 
   "Regulamentação da Profissão" que impeça profissionais de outras áreas atuar na TI. 
   Vamos nos mirar nesse exemplo ou na Nigéria? (que tem a atividade regulamentada). 

   1.1 Aliás, de forma geral, regulamentação de profissão é mais uma das exclusividades do Brasil, 
       junto da Jabuticaba, da Duplicata e do novo padrão de tomadas

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

wolever

#!/bin/bash
# Reverts HEAD back to ORIG_HEAD, for example after a 'git pull' accidentally
# creates a merge. This is identical to running 'git reset --hard ORIG_HEAD',
# except that unpull prints some helpful information along the way.
# Useage:
#     $ git unpull
#          HEAD: a0ac0fd Merge branch 'master' of /tmp/foo
#                2284c9d some remote commit
#     ORIG_HEAD: 35431fd my local commit
#     Really reset HEAD to ORIG_HEAD? (y/n) y

jbenet

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

sloria

The Best of the Best Practices (BOBP) Guide for Python

A "Best of the Best Practices" (BOBP) guide to developing in Python.

In General

Values

• "Build tools for others that you want to be built for you." - Kenneth Reitz
• "Simplicity is alway better than functionality." - Pieter Hintjens

renatooliveira

# coding: utf-8

from fabric.api import env, cd, run, sudo
from fabric.contrib.files import exists
from fabric.colors import green
from config import (HOST, USER, PASSWORD, APP_DIR,
                    ENV_HOME, PROJECT_NAME, VIRTUALENVS, REPOSITORY, BRANCH)

env.hosts = [HOST]
env.user = USER

zenorocha

// Future versions of Hyper may add additional config options,
// which will not automatically be merged into this file.
// See https://hyper.is#cfg for all currently supported options.

module.exports = {
  config: {
    // default font size in pixels for all tabs
    fontSize: 14,

    // font family with optional fallbacks