You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:
/people/6
But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.
“What we’ve got here is a Failure to communicate…”
The Cincinnati startup web development community sucks.
At least that’s the feeling we walked away with after reading an article posted March 11, 2012 by Laura Baverman on Cincinnati.com’s EnterChange blog. The article holds some credible facts, but not necessarily inevitable conclusions. The end result of her observations seems a little flawed. Cincinnati can sustain not only talented coders and designers; it already does. Absolutely, lots of local talent will go elsewhere to seek employment and opportunities, but plenty have stayed because they recognize the potential right here in the Queen City.
Sure it’s risky joining a startup vs. an established corporation, but if recent history has shown us anything, at least we know the future always involves risk. We’re traditionally an exceptionally conservative city, but in times like these, risk is best placed where your heart lay. Passion and commitment are what drives business. What better way to focus