⌘T | go to file |
⌘⌃P | go to project |
⌘R | go to methods |
⌃G | go to line |
⌘KB | toggle side bar |
⌘⇧P | command prompt |
When developing websites for small to medium clients, often a decent CMS is needed to get basic CRUD functionality and authentication off the ground quickly.
I've done a little bit of research into some of the most popular CMS platforms. Here are my quick thoughts.
- Website: http://www.browsercms.org/
Deploying to Heroku | |
================== | |
group :production do | |
gem 'rails_12factor' | |
end | |
# Enable the asset pipeline | |
config.assets.enabled = true | |
config.assets.initialize_on_precompile = false |
Repost from: http://opensoul.org/2011/11/30/haml-the-unforgivable-sin/
I used HAML on several client projects and I hated it every time. There are certainly some things that are nice about it, but overall it is a net loss.
##For abstraction’s sake Abstractions are a beautiful thing. The goal of an abstraction is to reduce or factor out irrelevant details. Removing details focuses you on the problem at hand and not the underlying implementation.
du -sh *
{ | |
/* Map # to § key*/ | |
"§" = ("insertText:", "#"); | |
} |
Many programming languages, including Ruby, have native boolean (true and false) data types. In Ruby they're called true
and false
. In Python, for example, they're written as True
and False
. But oftentimes we want to use a non-boolean value (integers, strings, arrays, etc.) in a boolean context (if statement, &&, ||, etc.).
This outlines how this works in Ruby, with some basic examples from Python and JavaScript, too. The idea is much more general than any of these specific languages, though. It's really a question of how the people designing a programming language wants booleans and conditionals to work.
If you want to use or share this material, please see the license file, below.
Keypress | Action |
---|---|
cmd + s | save changes in current file - DO IT OFTEN!!! |
cmd + q | close Sublime |
cmd + w | close one file at a time |
cmd + alt + arrow | switch between files |
cmd + numbers | also switch between specific files |
cmd + f | search in you current file |
cmd + shift + f | search the entire project |
cmd + d | go to next searched word in file |