The one absolutely solid place to store your capital today — if you know how to do it –  is in software developers’ wallets.

Source: http://www.forbes.com/sites/venkateshrao/2011/12/05/the-rise-of-developeronomics/
and you might also read: http://blog.8thlight.com/angelique-martin/2012/01/19/8-thing-you-ought-to-know.html

$ git branch -D branchname

But how to delete this branch in your remotes?

From Pro Git by Scott Chacon, we have:

Deleting Remote Branches

Suppose you’re done with a remote branch — say, you and your collaborators are finished with a feature and have merged it into your remote’s master branch (or whatever branch your stable codeline is in). You can delete a remote branch using the rather obtuse syntax git push [remotename] :[branch]. If you want to delete your serverfix branch from the server, you run the following:

$ git push origin :serverfix
To git@github.com:schacon/simplegit.git
 - [deleted]         serverfix

Boom. No more branch on your server. You may want to dog-ear this page, because you’ll need that command, and you’ll likely forget the syntax. A way to remember this command is by recalling the git push [remotename] [localbranch]:[remotebranch] syntax that we went over a bit earlier. If you leave off the [localbranch] portion, then you’re basically saying, “Take nothing on my side and make it be [remotebranch].”

That’s it!

Source: http://progit.org/book/ch3-5.html

At times we are too smart for our own good. We attempt add value to situations by adding unnecessary complexity. This can be a great way to demonstrate our intelligence, but it’s rarely the best solution to the problem.

Complicating a Situation Doesn’t Usually Make it Better

When things seem to be getting too complicated, cut through the fog by bringing things back to the most basic functionality and obvious facts.

~ and this: ~

Today’s Solution vs. the Best Solution (Startup Daily #270)

When solving problems or making changes, people often attempt to create the most sustainable solution possible. But nothing is permanent. Finding and implementing a permanent solution is not always a good use of resources.

Don’t Be Afraid to Use Quick, Temporary Solutions

Both the problem and the solution are likely to evolve over time. Solving the problem quickly is often more important than creating a sustainable solution.

“Do or do not, there is no try.” (Yoda)

Master, in this case, wrong you are!

There is a try, try is the opposite of hiding.

Check this interview with Seth Godin.

source: http://mashable.com/2011/12/07/seth-godin-video/

source: “Triumph of the Nerds: The Rise of Accidental Empires” documentary.

~ Albert Einstein.

So, no more, no less. Turn the page to continue…

(…)

Totally worth see it.

http://continuous-delivery.thoughtworks.com/events/introduction-continuous-delivery

Edit your Gemfile and change the line:

gem 'sqlite3'

To this:

group :production do
  gem 'pg'
end
group :development, :test do
  gem 'sqlite3'
end

And re-install your dependencies on your local development machine by running:

$ bundle install --without production

via http://devcenter.heroku.com/articles/how-do-i-use-sqlite3-for-development

• terminal = tty = text input/output environment
• console = physical terminal
• shell = command line interpreter

via What is the exact difference between a ‘terminal’, a ‘shell’, a ‘tty’ and a ‘console’? – Unix and Linux – Stack Exchange.