[CS106B, "Programming Abstractions,"](http://web.stanford.edu/class/cs106b/index.shtml) is the second term of Stanford's introductory programming sequence, taught in C++. 
  It follows upon [CS106A, "Programming Methodology,"](http://web.stanford.edu/class/cs106a/) which covers the basics of programming itself (functions, control structures, classes, etc.).
  106B is about basic data structures and algorithms, and how they can be encapsulated as abstract data types.
  
  This guide is based on the class as it was taught in 2004, the year I took it. Things may have changed since then. 
  
  You can find lecture videos for the 2008 version of the course [here](http://web.stanford.edu/class/cs106b/lecture-videos.shtml). 
  
  ## Week 1: C++ language
   
   The first week or so of the course covers aspects of the C++ language which are needed for the course -- mostly by highlighting the differences from Java, the language taught in 106A. The main new concept is [pointers](c_pointers), but the language also has different syntax for things like classes and input/output.
   
   If you haven't programmed before, check out our [beginning programming roadmap](http://www.metacademy.org/roadmaps/rgrosse/basic_programming), which covers comparable material to CS106A.
   
  ## Weeks 2-3: recursion
   
  The next two weeks focus on [recursion](recursion_programming), a programming technique where a function calls itself. Some computations, such as the factorial function or the solution to the [Tower of Hanoi](http://en.wikipedia.org/wiki/Factorial) puzzle, have a natural recursive structure. [Trees](tree_data_structure), an important data structure, are implemented most elegantly using recursive functions.
   
-  A lot of programming tasks can be formulated as _search problems_, where you want to find an object (e.g. an arrangement of queens on a chess board) which satisfies certain constraints (e.g. no queen can attack any other queen). (Or, sometimes, we want to find all such objects.) [Recursive backtracking](http://en.wikipedia.org/wiki/Backtracking) is a kind of brute-force search algorithm which tries to build solutions one component at a time, backtracking whenever the partial solution violates one of the constraints. One of the early assignments in the course is to use backtracking to find all of the words in a [Boggle](http://en.wikipedia.org/wiki/Boggle) board. 
+  A lot of programming tasks can be formulated as _search problems_, where you want to find an object (e.g. an arrangement of queens on a chess board) which satisfies certain constraints (e.g. no queen can attack any other queen). (Or, sometimes, we want to find all such objects.) [Recursive backtracking](http://en.wikipedia.org/wiki/Backtracking) is a kind of [brute-force search](http://en.wikipedia.org/wiki/Brute-force_search) algorithm which tries to build solutions one component at a time, backtracking whenever the partial solution violates one of the constraints. One of the early assignments in the course is to use backtracking to find all of the words in a [Boggle](http://en.wikipedia.org/wiki/Boggle) board. 
+ 
+ ## Weeks 4-9: data structures
+ 
+ Finally, the heart of the course is about data structures and their implementation. There are two ways of looking at data structures:
+ 
+ * [abstract data types](abstract_data_types), which define the abstract operations the data structure must support, and the semantics of those operations, and 
+ * the actual implementation of the data structure
+ 
+ Abstract data types are an important example of the principle of [abstraction](http://en.wikipedia.org/wiki/Abstraction_(computer_science)), the idea that a system should hide the details of its implementation, so that the client can think about the problem at a higher level. Abstraction makes it easier to build complex pieces of software, and also makes it easier to modify the underlying implementation of the data structure, should one come up with a more efficient approach.
   
-  
+ This part of the course starts by talking about two abstract data types: [stacks](stack) and [queues](queue). A stack is a "last-in-first-out" (LIFO) container, where one can "push" an item onto the stack, or "pop" the most recently inserted item, but one does not have access to any of the other elements in the stack. A queue is analogous, except that it is a "first-in-first-out" (FIFO) data structure, where one retrieves the elements in the order in which they were added.
+ 
+ 
+