blog.philcrissman.com

UML is usually seen as a very corporate (i.e., boring) tool. It implies planning, best practices, and all those other things.

Hacking is usually described as a paradigm of just sitting down and starting to code, and altering your architecture along the way as you need to.

I think that’s fine, possibly even beneficial, for small projects, or projects worked on my one individual. But as soon as you decided to get a team working on a project… you need some way to represent parts of the application so people know how it works. Yes, we could just invent a new ad hoc representation scheme every time we need to do this… or we could just use UML.

“You should use iterative development only on projects you want to succeed.”

- Martin Fowler (UML Distilled, 3rd Edition).

NOTE: I’ve had a penchant for just posting quotations, recently. This is mainly because I’ve been swamped with work, but part of that work has included reading or re-reading a lot of software development classics, hence the quotations. For what it’s worth, I’ll try to write something of my own some time soon.