ahoward · January 2, 2016 09:49 · Jan 6, 2014 · Jan 6, 2014 · Jan 6, 2014 · Jan 6, 2014
diff --git a/a.md b/a.md
@@ -1,6 +1,6 @@
-recently our team had an exchange about lazy evaluation of ORM queries in ruby ( https://gist.github.com/ahoward/8285529 ) - this prompted me to think about how deep rails has really become and just how hard good MVC organization for the web really is.   back in the data it took a special kind of developer to understand how to not kill a db when it was used in a web app - now it's pretty easy and, while this seems good on the outside, in the inside i think today's developers understand less and less about why web programming is really the hardest there is.
+recently our team had an exchange about lazy evaluation of ORM queries in ruby ( https://gist.github.com/ahoward/8285529 ) - this prompted me to think about how deep rails has really become and just how hard good MVC organization for the web really is.   back in the day it took a special kind of developer to understand how to not kill a db when it was used in a web app - now it's pretty easy and, while this seems good on the outside, in the inside i think today's developers understand less and less about why web programming is really the hardest kind there is.
 
-that's the motivation for today's quiz.  to take it *fork* and keep your answer under 100 LOC *total*
+that's the motivation for today's quiz.  to take it *fork* and keep your answer under 142 LOC *total*
 
 
 given a model, *Post*, write code which will

diff --git a/z-quiz.md → a.md b/z-quiz.md → a.md
diff --git a/quiz.md → z-quiz.md b/quiz.md → z-quiz.md
diff --git a/quiz.md b/quiz.md
@@ -0,0 +1,20 @@
+recently our team had an exchange about lazy evaluation of ORM queries in ruby ( https://gist.github.com/ahoward/8285529 ) - this prompted me to think about how deep rails has really become and just how hard good MVC organization for the web really is.   back in the data it took a special kind of developer to understand how to not kill a db when it was used in a web app - now it's pretty easy and, while this seems good on the outside, in the inside i think today's developers understand less and less about why web programming is really the hardest there is.
+
+that's the motivation for today's quiz.  to take it *fork* and keep your answer under 100 LOC *total*
+
+
+given a model, *Post*, write code which will
+
+- load the 2nd set of 5 results (page 2 of 5 each)
+- access them in the view
+
+sounds easy right?  now here are the requirements:
+
+- do NOT load any more objects from the db than required - not a single one.
+- no database activity must occur if the view doesn't require it, none.
+- you may not rely on cache helpers, rails, imaginary, or otherwise
+- you many not rely on magic ORB behavior such as lazy evaluation
+
+this is obviously a web developer 101 task - so think about the difficulty in
+the context of your next framework evaluation (aka when you think writing an
+api for backboone seems 'easy')
diff --git a/view.html.erb b/view.html.erb
@@ -1,4 +1,3 @@
-
 <!-- go -->
 
 <%= @posts %>

diff --git a/view.html.erb b/view.html.erb
@@ -1,4 +1,6 @@
 
+<!-- go -->
+
 <%= @posts %>
 
 <ul>

diff --git a/controller.rb b/controller.rb
@@ -0,0 +1,5 @@
+class PostsController
+
+ # go
+
+end
diff --git a/model.rb b/model.rb
@@ -0,0 +1,6 @@
+class Post
+
+ # go
+
+end
+
diff --git a/view.html.erb b/view.html.erb
@@ -0,0 +1,6 @@
+
+<%= @posts %>
+
+<ul>
+  <li> ... </li>
+</ul>
No results found