ef4

// "route" and "resource" are almost interchangeable. Both of these work fine:

this.route('people', function(){
  this.route('person', {path: '/:person_id'})
})

this.route('people', function(){
  this.resource('person', {path: '/:person_id'})
})

bjorgvino

Remove osxfuse if installed via homebrew:
> brew uninstall osxfuse

Install osxfuse binary and choose to install the MacFUSE compatibility layer:
http://sourceforge.net/projects/osxfuse/files/latest/download?source=files

Reboot (optional but recommended by osxfuse)

Install ntfs-3g via homebrew:
> brew update && brew install ntfs-3g

Andrew-Max

App.LibraryRoute = App.ApplicationRoute.extend({
  activate: function () {
    //no longer enter
    this._super();
    only called once on entering a route. 
  },

  beforeModel: function () {
    // any state you want in place before the model is initialized, this is called before any model promises are resolved
    // also could be used to conditionally prevent access to a route by throwing transition.abort

kristianmandrup

Converting libraries to Ember CLI addons

In this guide we will cover two main cases:

• Ember specific library
• vendor library

Ember library

The Ember library will assume that Ember has already ben loaded (higher in the loading order) and thus will assume it has access to the Ember API.

addyosmani

CSS Layout Debugger

A tweet-sized debugger for visualizing your CSS layouts. Outlines every DOM element on your page a random (valid) CSS hex color.

One-line version to paste in your DevTools

Use $$ if your browser aliases it:

~ 108 byte version

LeCoupa

#!/bin/bash
#####################################################
# Name: Bash CheatSheet for Mac OSX
# 
# A little overlook of the Bash basics
#
# Usage:
#
# Author: J. Le Coupanec
# Date: 2014/11/04

mathisonian

The final result: require() any module on npm in your browser console with browserify

This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.

Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5

inspiration

selfboot

#! /usr/bin/env python
# -*- coding: utf-8 -*-


class Trie_tree():
    def __init__(self):
        # node = [father, child, keep_char, is_word]
        self._root = [None, [], None, False]

    def insert(self, word):

yocontra

Stealing WiFi

/etc/hosts

This will let you access any google owned site. This includes: youtube, google cache, google translate, google search, gmail, google news, etc.

• Install the HTTPS Everywhere extension
• Add these rules to your /etc/hosts file

ohizkiya

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

Table of Contents

1. Understand the Chrome Architecture
2. Understand the Tabs-Extension Relationship
3. Picking the right interface for the job