This past weekend I was fortunate to attend Rails Girls in SF, and help introduce Rails and the associated tech to around 40 women. After answering a number of common questions many times about the command line, I decided to take the opportunity to make some videos explaining some basic concepts.
Last week we did a whole lot of Ruby View coding, using HTML and ERB to build websites. This week we’re going to focus on routing in the lecture, and then use routing to build a rails site that uses views and models together. You can start off by watching the Recap of Week 3 and then taking the week 3 quiz before viewing the week 3 solutions.
In week one we learned about storing data and using databases. In week 2 we saw how we can model relationships with databases, and use those relationships with Ruby and Active Record to build models in Rails. This week we start out with a quick Recap of last week followed by a Quiz. Once you finish the quiz you can check out the Quiz Solutions.
I recently got a position as an Adjunct Professor for the University of texas, watch this video to find out how I got the job.
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.
