anchor.diff:  
   public final class Traversals {
     public static Map<String,List<Vertex>> groupAround(GraphTraversalSource g, long vertexId) {
  -    return g.V(vertexId).outE().group().by(label).by(inV()).next()
  +    return g.V(vertexId).outE().
  +             group().
  +               by(label).
  +               by(inV()).next()
     }
   }
   ----
  
positive.code: 
  [gremlin-groovy,modern]
  ----
  g.V(1).outE().group().by(label).by(inV()).next()
  ----
  
  In this case, the line of execution does not return a `Traversal`.  It returns the first item in the `Traversal` with
  
negative.code:                   max().next()
  ----
  
  You store that result in a variable called "firstYear", as you will need that later to help filter results in the
  traversal that ultimately gets the data. In this way, all "person" vertices can be compared from the same start time.
  It is often helpful to store results from traversals if you intend to work with that data later and the traversal
  itself is expensive to execute. It is only important to keep in mind that you will be limited by the memory available
  to the console.
  
  TIP: You can change the amount of memory allotted to the console by altering its `-Xmx` setting in `bin/gremlin.sh`.
  This setting controls the maximum size of the JVM memory allocation pool. To set this value to 1024 megabytes, you
  