Feedback

When we get into Rails this will be more enforced but there is an architectural sort of standard for how to structure URLs and what they should do that's known as REST. Though this is more enforced in Rails than in Sinatra, it's definitely not specific to Rails and is generally a good practice to follow when building web applications in any language.

The Rails guides actually has an awesome guide that goes over the conventions built into Rails but it's also a good guideline to follow when building a Sinatra (or in any web framework) application. I'd recommend giving the [Rails Routing guide](http://guides.rubyonrails.org/routing.html#resource-routing-the-rails-default) a read through and trying to build your Sinatra apps with the same structure.

> Section 2.2 of that guide has an awesome table that lays it out well

In this particular case, you can imagine that if your app has any other models that you want to be able to create, you're going to have to add another route and then you're going to run into a conflict with just using "/add". The restful way of doing this would be to make it at `/contacts/new`. This way you can always kind of figure out which routes are supposed to do what because they follow the same pattern.