How to Be an Architect, Graphically Speaking

As I mentioned in my Ann Arbor Day of .NET 2008 recap, I was given a marker and was told to write down what people were saying during Brian Prince‘s “How to Be an Architect” talk. Is that really a good idea? We’ll let you decide…

First of all, an architect is…

NOT the Office Space guy

One of the things that Brian mentioned was ArcReady:

Arc Ready

He mentioned that architects have one foot in the technology arena and one foot in the business aspect of things:

Feet in two spots - technology and business

He mentioned that they should not be architects of the ivory tower or that the tower would burn:

Burning ivory tower

He mentioned something about stalking out business on a golf course:

The celery stalks at midnight...

But he said that although architects should still write code, it shouldn’t be put into production.

Leave it to the code monkeys!

There also was some recommended reading:

Architects read.

The whiteboard in the end looked like this:

Sarah + marker + whiteboard = ...

The end.

Side note: Have no fear. I’m not quitting my day job and going into whiteboard note taking. And by my drawings, I hope you guys realize that I’m a developer but nowhere near a designer.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.