Last week we talked about why and how we can use databases to store information. This week we’re going to be focusing on how to use databases to model real world relationships and then use those relationships in Rails.
It’s that time of year again, I’m teaching a course at the University of Texas, though this time i’m officially an Adjunct Professor!! That means not only are students learning all about Rails, they’re getting credit for it. I’ve taken the liberty to re-record some of my material and share it. Hopefully you’ll be able to follow along at home.
What happens if your passwords get breached like LinkedIn? Are your users safe? Will they trust you? Had LinkedIn taken a few more security precautions they could have greatly mitigated the security threat. Simply stretching and salting passwords would have made the break in much less valuable to the thieves.
Just got back from EuRuKo in Amsterdam, and getting ready for teaching my first class of the semester at the University of Texas when I stumbled on this gem on HN. The author makes some amazing points and digs deep into an issue that has been clawing at me since I joined Heroku. You should check out the article, even if you don’t use Heroku. IMHO all products should be built for simplicity and ease of use, and it doesn’t mean you’re building for idiots…just look at Apple products. Wish me luck on my class, I’ll try to post some materials from it as soon as I get a chance.
News flash, writing a Rails app without knowing your routes is pretty much impossible, and this just in
$ rake routes takes forever [1] to run. So how can we build a Rails site with a
minimum of time and a maximum of awesome? You can use the recently released Sextant Gem [2] to generate routes in your Rails app.
What exactly is OAuth, and how can you use it to access data on sites like Facebook? This introductory video explains the basic flow behind OAuth 2 and how OAuth Clients are implemented.
