WICSA 2005:Keynote Discussion

Some notes about the keynote. These notes do not cover the complete keynote and are not necessarily in chronological order:

Working on Handbook of Software Architecture by travelling to 100+ organisations and looking at their architecture. Will hopefully be ready in 2-3 years.
"Old code does not die, you have to kill it."
Software reading should be a course taught to students, how else can you learn good programming other then to learn from good examples
Architects should code themselves. This point was also discussed in the working session on Education and the BoF meeting What Do Software Architects Actually Do?
International Association of Software Architects
Worldwide Institute of Software Architects
The Computer History Museum is now also working on a collection of software. One of the contributions is the original code to MacPaint, which is a beautiful piece of code
Most architectures are described on a very high level in PowerPoint presentations and at a very low level in the code, but often there is nothing in between.
Truck memory: number of trucks required to wipe out the architectural knowledge of a project. If this number is one that is very bad.
In order to collect more architectural data a collaborative development environment should be created to do this in a non-intrusive way.