Papers, Talks and Position Statements

CASE '87

Kent Beck and I report on our experience creating graphical versions of Smalltalk tools. We argue that in a literate programming environment interactive tools have the added responsibility of producing diagrams that aid the non-interactive reader to the same degree that the interactive part aided the original user.

OOPSLA '87

Kent Beck and I outline our adaptation of Pattern Language to object-oriented programming. This report of our first positive experience with patterns at Tektronix was presented at OOPSLA's Workshop on the Specification and Design for Object-Oriented Programming. Available in Japanese.

 

OOPSLA '88

Coauthor Roxie Rochet and I presented this vision for pattern languages as a position statement for a software engineering workshop.

 

OOPSLA '89

Kent and I introduced CRC Cards with this paper, A Laboratory for Teaching Object-Oriented Thinking. Kent wrote the first draft so, by our convention, his name went first.

 

OOPSLA '91

This workshop position statement offers WyCash's Report Writer as an example of a valuable software architecture.

 

OOPSLA '92

This Experience Report presented The WyCash Portfolio Management System, a large financial application developed in Smalltalk. It also introduced the debt metaphore for code consolidation.

 

WOOD '94

With this position statement I challenge the attendees of the Workshop on Object-Oriented Design to consider the construction of high-quality, long-lived objects. Can we design an object that is flexible enough to last 100 years?

WOOD '94 Remarks

With these remarks, now recalled from memory, I compared designing to skiing and cautioned that we make both more difficult when when we are rigid, ignore our edges, or are overcome with fear.

 

PLoP '94

This paper, The CHECKS Pattern Language of Information Integrity, is my contribution to the Pattern Languages of Programs conference. This HTML version is from the Portland Pattern Repository.

 

PNWSQC '94

This invited presentation introduced patterns, writing patterns and the recent PLoP conference.

 

OOPSLA '94

This position statement reflects on collective design, both in CRC and in development in general. It is a rather personal reflection submitted as a position to the workshop titled: How Do Teams Shape Objects? How Do Objects Shape Teams?

 

PLoPD

This introduction to Pattern Languages of Program Design explains why we started the PLoP conferences and what we expect to come of them. I was the program chair.

 

Smalltalk Solutions '96

This is an abstract for a talk titled Modeling Under Pressure: Finding and exploiting potent abstractions when you barely have time to think. The material is derived from the my Episodes pattern language.

 

Surviving Your First OO Project

This short experience report is to appear in Alistair Cockburn's "Surviving" book. I've titled the essay CRC-Card Experience Connects Developers and Customers to Essence of the Problem.

 

Smalltalk Best Practice Patterns

This foreword to Kent Beck's book of coding patterns explains why I care about such things and everyone else should also. Unfortunately it didn't make the first edition.

 

Analysis Patterns

This foreword to Martin Fowler's book joins one by Ralph Johnson. We both loved the book and consider it a landmark in the pattern movement.

 

Kent Beck: Sorted Collection

In this afterword to Kent's collected articles I describe the programming we did together at Tektronix and explain why we found productivity that eluded others.

 

OOPSLA '01: Signature Survey

This position statement was written for the workshop titled Software Archeology: Understanding Large Systems. It reports a technique I've used several times to browse large code bases using a standard web browser and a couple of cgi scripts that are tuned to the questions at hand. This document includes links to downloadable scripts.

 

XPU '02: Delivering Software

This position paper was prepared for the XP Beyond Limitations panel. I argue that xp is about delivering software and that if you aren't delivering or you aren't doing software then xp may not apply. I also suggest the organizational technology that will help even in these cases.

 

XPU '02: Acceptance Testing

In this position statement for the Agile Testing workshop I argue that acceptance testing is best viewed as document authoring and that the testing machinery as a document annotator. This work precipitated the fit.c2.com acceptance testing framework.

 

XP Pocket Guide (rtf)

Chromatic wrote a pocket guide to XP for O'Reilly. I loved it. This is the forward I wrote that said so.