Coffee house murmurs are all the rage these days for workers trying to get into the zone while working independently. Last year, New York Times published How the Hum of a Coffee Shop Can Boost Creativity which explored the phenomenon.
Rails 4.1 allows us to use Spring
to run our
rake commands quickly by running your
application in the background and avoiding the rails startup time
penalty. It took me a little while to find this information, so here is my
guide to setting this up.
TL;DR - Git is a low-level library. All development and deployment environments differ, so build your own development work flow system on top of git to build your best work flow environment.
The git version control system became hugely popular once it was introduced, and along with Github, achieved a dominant role in open source to enterprise development.
Git is powerful, even complicated, but also allows a novice to start with minimal training. The more I use git, the more I start finding odd corners that I need to head to google to find out more how to use it. There are some parts of it that are just darn incomprehensible unless you understand the internals, so it becomes hard to guess where to look to find your answers.
REST promotes CRUD. CRUD is for databases, not applications.
Databases generally have four operations to a set of data: Create, Read, Update, and Delete; these four operations are known by the acronym CRUD. An SQL-based relational database (like PostgreSQL, MySQL, etc.) have 4 cooresponding statements:
- Insert -> Create
- Select -> Read
- Update -> Update
- Delete -> Delete
The CouchDB database and SOLR search engine operate natively over a REST interface. Your applications perform CRUD operations on these data stores by employing the above style of request.
Architectures based on REST, like Ruby on Rails, builds the application on table resources to perform CRUD operations. By doing this, we get a free API into the application callable from any platform capable of making HTTP/REST calls.
Many applications require users to register or enter their email addresses. As good, standards-compliant developers, we want to validate and accept these email addresses using RFC standards. We think it will help us in the future, and make our app a shining beacon of usability to be admired.