deividy

well, I think if you start with this kind of bureaucracy, you're doing it wrong. It's not funny. Also, if your app is down, clients calling and you need to fix it fast. If I need to remember this rules to fix this, people will kill me, or I will kill myself :p

I fix about 2~4 issues by day, 20~40 commits by day. If I do write a blog post for every commit my productivity will down by 70% at least.

"It should start with a capital letter, then move to lowercase, and necessarily will start with a verb.", are you seriously?

I figure that so few people read commit messages that in most part of time this is kind of useless. Specially in an early stage of a project. Things will change as faster as I can type a message such as this.

Code is simple. Humans overthink. I would prefer a commit message such as: "Fix invalid byte sequence in US-ASCII when running bundle exec rspec." than a dev that keep stucked trying to write a cool message and never fix the issue.

use `set -o vi` to use vim binding, if you don't like emacs :)

Am I the only dev in the world that loves async?

Oh, now that you mentioned it, I'll use XML, It's very cool and compatible with new technologies, like a new thing of Microsoft called C#.