Developer Disaster Drawer @raul-b-blog - Tumblr Blog

The only "intuitive" interface is the nipple. After that it's all learned

Bruce Ediger

ZSH

Aren't you using zsh yet? C'mon, the last version was released last July 27! Just type:

brew install zsh && curl -L https://github.com/robbyrussell/oh-my-zsh/raw/master/tools/install.sh | sh

More info.

Slides which explain perfectly what you could do with Heroku (everything) More info at http://blog.heroku.com/archives/2012/7/17/buildpacks/

#heroku #slides #hone02 #buildpacks

Require.js will show you how wrong is your javascript

Add http://requirejs.org/ to your project and it'll expose what you're doing wrong with your javascript. For example, a circular dependency is just a signal that you should change something. If you're interested on another post with an example of an application using requirejs with Backbone (bootstrapping your app) let me know and I'll write it.

#javascript #js #requirejs #require #backbone

dropshadows

Pretty git log

TJ Holowaychuk featured a pretty git log alias, taking advantage of git log --pretty. I am now rocking:

alias glog="git log --format='%Cgreen%h%Creset %C(cyan)%an%Creset - %s' --graph"

Breakpoints in JS

I just realized that there're many people out there wasting their time adding breakpoints in their js console. Why, instead of going to the specific js file and add a breakpoint with your JS console on your browser, don't you add this to your code?. Do it and you're done:

debugger;

#js #debug #breakpoint #web #console

Good talk about the Ember.js principles

#ember.js #mvc #javascript #js

Views module using Mustache with Sinatra

If you're using modules in your Sinatra app and you're using Mustache, bear in mind that you should specify the new namespace like this:

require 'mustache/sinatra' class Hurl < Sinatra::Base register Mustache::Sinatra set :mustache, { # Should be the path to your .mustache template files. :templates => "path/to/mustache/templates", # Should be the path to your .rb Mustache view files. :views => "path/to/mustache/views", # This tells Mustache where to look for the Views module, # under which your View classes should live. By default it's # the class of your app - in this case `Hurl`. That is, for an :index # view Mustache will expect Hurl::Views::Index by default. # If our Sinatra::Base subclass was instead Hurl::App, # we'd want to do `set :namespace, Hurl::App` :namespace => Hurl } get '/stats' do mustache :stats end end

If not, Sinatra won't find your (mustache) views. More info

#sinatra #mustache #namespace #views

Tell it to someone

Work remotely sometimes could be annoying, especially when you have a trouble with something and you can't share it quickly. This works to me: 1. Record a screencast (I use http://www.techsmith.com/jing.html) and explain your problem to "another person". 2. Watch the screencast. If you explained your problem wrong, repeat the step 1!! The 98% of cases I just found a solution by myself. With the other 2%... I share the screencast that I already recorded, :D.

#work #screencast #remotely #help

robotmay-blog

Low level caching is very easy to get started with in Rails 3, but it seems to be missing from the official guides. I personally use it all the time to help reduce the number of queries or API calls I’m making. Heroku has a pretty good explanation which, if you’re so far unfamiliar with...

Use SublimeText from command line

Create a symbolic link doing:

$ ln -s "/Applications/Sublime Text 2.app/Contents/SharedSupport/bin/subl" ~/bin/subl

Run

subl --help

#sublime #command #line #cli #text #editor #terminal

declarationofprocess

As a creative person, you’ve been given the ability to build things from nothing by way of hard work over long periods of time. Creation is a deeply personal and rewarding activity, which means that your Work should also be deeply personal and rewarding. If it’s not, then something is amiss.

Ben Pieratt (via declarationofprocess)