stt

/* 
 * Jison rules for parsing simple boolean expressions
 * (c)2011, <samuli@tuomola.net>
 * 
 * Usage: npm install jison && jison sqlaus.jison && node test-sqlaus.js
 * 
 * Meant primarily for generating SQL clauses for m:m table structure.
 *
 * Depends on shared scope to provide..
 * functions:

jaysonrowe

for (var i=1; i <= 20; i++)
{
    if (i % 15 == 0)
        console.log("FizzBuzz");
    else if (i % 3 == 0)
        console.log("Fizz");
    else if (i % 5 == 0)
        console.log("Buzz");
    else
        console.log(i);

liamcurry

Moving from jQuery

Events

// jQuery
$(document).ready(function() {
  // code
})

iros

Title

<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>

• URL

  <The URL Structure (path only, no root url)>

• Method:

zachharkey

// OOCSS Media Object
@mixin media-object($img: '.media-img', $bd: '.media-bd', $margin:10px, $position: left, $formatting-context: 'overflow') {
  @include pie-clearfix; // or extend a .clearfix class
  #{unquote($bd)} {
    @if $formatting-context == 'overflow' {
      overflow:hidden;
    } @else {
      display:table-cell;
      width:10000px;
      *width:auto;

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

mikermcneil

A Modest Proposal: Events

Sails.js v0.10

Events are a new feature of the Sails core as of 0.9.

Core events

Lifecycle

aras-p

// Just before switching jobs:
// Add one of these.
// Preferably into the same commit where you do a large merge.
//
// This started as a tweet with a joke of "C++ pro-tip: #define private public",
// and then it quickly escalated into more and more evil suggestions.
// I've tried to capture interesting suggestions here.
//
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,

sindresorhus

# npm publish with goodies
# prerequisite: `npm install -g trash`
# `np` with an optional argument `patch`/`minor`/`major`/`<version>`
# defaults to `patch`
np() {
	trash node_modules &>/dev/null;
	git pull --rebase &&
	npm install &&
	npm test &&
	npm version ${1:-patch} &&

tsiege

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!






\