discussion doneish

final/final.out

@@ -2,4 +2,6 @@
 \BOOKMARK [1][-]{section.2}{Approach}{}% 2
 \BOOKMARK [1][-]{section.3}{Results}{}% 3
 \BOOKMARK [1][-]{section.4}{Discussion}{}% 4
-\BOOKMARK [1][-]{section.5}{Sources Cited}{}% 5
+\BOOKMARK [2][-]{subsection.4.1}{Reflection}{section.4}% 5
+\BOOKMARK [2][-]{subsection.4.2}{Future}{section.4}% 6
+\BOOKMARK [1][-]{section.5}{Sources Cited}{}% 7

final/final.tex

@@ -92,12 +92,12 @@ course staff.
 In terms of our original vision, {\tt c0db} includes almost every feature we
 planned to implement. Users can input code and either run the program straight
 through or step through execution instruction by instruction. The only
-significant feature that is not currently implemented completely is
+significant feature that is not currently implemented completely is breakpoints.
-breakpoints.  Implementing breakpoints turned out to be significantly more
+Implementing breakpoints turned out to be significantly more difficult than we
-difficult than we anticipated, and given our limited time frame, we were unable
+anticipated, and given our limited time frame, we were unable to come up with an
-to come up with an adequate solution. We are currently working with Rob
+adequate solution. We are currently working with Rob Simmons, 15-122 instructor
-Simmons, 15-122 instructor and maintainer for the {\tt C0} language standard,
+and maintainer for the {\tt C0} language standard, to extend the language to
-to extend the language to support breakpoints more easily going forward.
+support breakpoints more easily going forward.
 
 \begin{figure}[h]
   \includegraphics[width=\linewidth]{new-gantt}
@@ -111,6 +111,32 @@ and polishing. Both teams were able to recover from the lag reported in our
 progress report to complete {\tt c0db}.
 
 \section{Discussion}
+\subsection{Reflection}
+Our team learned several useful skills while working on this project, ranging
+from technical tricks to communication insights. For several of us, this project
+represents the most collaboration on a single code base. We effectively employed
+the git version control system to manage our code to lesson the work needed to
+integrate each person's features. Additionally, several members of our team had
+never worked with node.js or JavaScript extensively before this project.
+Everyone quickly picked up the new framework and started producing useful
+output.
+
+We did face some issues communicating early on, but fortunately we were able to
+learn from our problems. Communicating strictly online was not sufficient and
+resulted in a lack of ownership and drive that put us behind schedule early on.
+We overcame our communication problems by holding brief but regular meetings
+face to face to cover what has been accomplished and what tasks come next.
+
+\subsection{Future}
+{\tt C0db} is most of what we imagined, but not all. Our overall goal, to make a
+tool useful for 15-122 students, may be realized in the fall, but we have more
+work to ensure that we present them with the best tool possible. Before the next
+semester starts we aim to complete the remaining features we originally planned
+to implement: source-level breakpoints, multi-file support, and a refined
+interface. If we can implement these three features, {\tt c0db} could see proper
+adoption by 15-122 in the fall, where it would be used by over 300 students from
+across Carnegie Mellon. If {\tt c0db} is adopted by 15-122, we would truly have
+achieved the goal for our project: create a tool to better the CMU community.
 
 \section{Sources Cited}
 

final/letter_aux

@@ -1,2 +0,0 @@
-\relax 
-\@mlabel{}{\unhbox \voidb@x \ignorespaces Mr. Thomas M. Keating \\ Assistant Teaching Professor \\ School of Computer Science \\ Pittsburgh, PA 15289}