Description
Course info
Rating
(30)
Level
Intermediate
Updated
Mar 16, 2012
Duration
1h 30m
Description

Jim Weirich is the author of the ubiquitous Rake build tool for Ruby. He's the Chief Scientist at EdgeCase and is a popular speaker and teacher. Given Jim's proven skills in designing APIs for programmers, we wanted to see him design an API from scratch in real time. We gave him the task of building a library that enforces HTML form security. The library protects against unauthorized data model modification by users in less-privileged roles.

About the author
About the author

Jim Weirich (November 18, 1956 – February 19, 2014) was a well-known developer, speaker, teacher, and contributor to the Ruby community.

About the author

Geoffrey founded PeepCode and has created numerous courses on Ruby, JavaScript and Shell.

More from the author
Play by Play: React and Falcor with Brian Holt
Intermediate
1h 51m
Oct 15, 2015
More courses by Geoffrey Grosenbach
Section Introduction Transcripts
Section Introduction Transcripts

Introduction
[Autogenerated] It's people code. Jim Wire IQ is the chief scientist at EJ Case. He was one of the first English speaking adopters of Ruby is the author of Rake. A Build Tool, found in basically every Ruby project. He's also authored the Builder Library for Generating XML and is a popular speaker and teacher. Given Jim skills with designing AP eyes for programmers, we wanted to give him a project that would require him to design an A P I from scratch. And he did. You'll see him work through several designs to meet the requirements within the boundaries of what's possible in Ruby. Here's the task we gave him design. A form validator object that will restrict right access to a data model based on a user's role. Imagine a mystery bookshop that picks a book for subscribers to read every month. Subscribers can change their name, password or shipping information. The store owner can pick the book and price, but subscribers cannot change the name of the book or its price. This is Pete code play by play, and as such, we won't pause to explain much. You'll see an expert at work using the tools and techniques that he uses when building his own projects, look at how he uses his editor, how he writes tests and how he uses the Ruby language.