6. http://www.visibleworkings.com/archeology/ : 18:16

Programmers are often given a large system they've not seen before, built by
people they don't know, touched by many people since, documented sketchily if
at all. They're told to improve it. Their task might be to fix a bug, add a
feature, or complete a refactoring. They are under time pressure, so they
need to minimize the total time spent learning and the time spent improving.

In this workshop, we will share techniques and approaches for understanding
enough about a lot of code in not much time. We are concerned not just with
speed, but also with confidence: how can you know you've made an improvement,
not made the system worse?

I'd love to hear about any questions, comments, suggestions or links that you might have. Your comments will not be posted on this website immediately, but will be e-mailed to me first. You can use this form to get in touch with me, or e-mail me at [email protected] .

Page: 2003.02.26

Updated: 2004-11-2106:44:1306:44:13-0500

NOTE: ANTI-SPAM MEASURE NOW IN PLACE. Please answer the following question with the right number in order to send me your comment.