diff --git a/icfp-2016/experience.scrbl b/icfp-2016/experience.scrbl
index 5f6c344..253d8fb 100644
--- a/icfp-2016/experience.scrbl
+++ b/icfp-2016/experience.scrbl
@@ -1,32 +1,39 @@
 #lang scribble/sigplan
 @require["common.rkt"]
 
-@; TODO experiment is BOGUS because it doesn't measure overhead of define/let
-@; Make those automatic and try again!
-
 @title[#:tag "sec:experience"]{Experience}
 
 Our initial experience programming with the library has been positive.
 By far the most useful application is to @racket[regexp-match], as
  Typed Racket's default requires either a type cast or guards on each
  matched group.
-The bugs reported by @racket[printf] and others are also useful, though
- the real-time difference between catching a @racket[printf] bug during compilation
- versus finding the same bug at run-time is small, maybe 1-3 seconds.
-We have also observed performance improvements on microbenchmarks involving
- maps over large vectors, though we have yet to find the same benefits in real
- code.
+The bugs reported by @racket[printf] and others have also proven useful
+ in development.
 
-In total, we have applied the library to 10,000 lines of Typed Racket code
+Regarding the optimized vector operations mentioned at the end of @Secref{sec:vector},
+ we have observed performance improvements on microbenchmarks but have yet
+ to find real programs where the same benefits apply.
+In future work, we hope to improve the vector library to include matrix arithmetic
+ and try similar experiments on numeric code.
+
+Thus far, we have applied the library to 10,000 lines of Typed Racket code
  taken from 7 small projects.
-Including the library is a 1-line change, but the programmer needs to remove
- now-redundant type annotations and casts manually.
-Compiling with our library adds no statistically significant overhead, but
- tends to produce slightly larger bytecode files (at most 2% larger).
-Running times are slightly worse for the added casts; in the worst case
- we saw 2-second slowdown.
-This could be improved by tighter integration with the type checker.
+In total, we had to modify 6 lines to replace
+ unrestricted mutation--which could violate our library's assumptions---with
+ reference cells.@note{None of the surveyed code used the database library;
+  we have only tested that interface in scripts.}
+This gives us confidence that opting-in to our library truly is a 1-line
+ effort.
+Removing type annotations and casts made redundant by our library is, however,
+ still a manual task.
 
+Compiling with our library adds no statistically significant overhead, but
+ tends to produce slightly larger bytecode files due to the inserted
+ annotations (at most 2% larger).
+Running times we observed were slightly degraded by the added casts;
+ in the worst case we saw a 2-second slowdown.
+This could be improved by a closer integration with the type checker to
+ remove casts guaranteed to succeed.
 
 @;@figure["fig:experience"
 @;  "Experience Report"