The role of architect

Thanks to a pointer from Kent Beck, I’ve just read Alan Keefer’s post, Taking Responsibility.  This is probably the best description I’ve ever read of the role that a software or system architect should take.

And it’s very different from the role I’ve normally seen them take.  Most software architects got the title because they were very good software developers.  I’ve seen far to many who assume that they should now do the “highest level” of the work they’ve been doing, that of the system level design, and leave the more mundane work to those who are still software developers.  In other words, they’re considering their promotion from the point of responsibilities they’re shedding rather than those that they’re taking on. (Continued)

If you don’t automate acceptance tests?

Amr Elssamadisy reports on InfoQ that automated acceptance tests are “only used by a small minority of the community.”  Is this true?  If you and your team don’t use automated acceptance tests, please let me know how you handle regression tests as the application grows larger.  You can leave a comment here or, if you’d rather not say it in public, email me directly. (Continued)