Sinatra Best Practices: Part One Erin Swenson-Healey · June 24th, 2013 While Sinatra’s one-file approach may work well for your one-off, smaller application – it can quickly become a mess as you add on multiple routes, route-handlers, helpers, and configuration. So what’s a programmer to do? In reading Sinatra’s documentation I’ve found a few morsels that have enabled us to split our otherwise-mon
![Sinatra Best Practices: Part One](https://cdn-ak-scissors.b.st-hatena.com/image/square/23b052feb988940a595cdf17772838fc32bbb208/height=288;version=1;width=512/https%3A%2F%2Fblog.carbonfive.com%2Fwp-content%2Fuploads%2F2013%2F06%2F23.png)