Don pointed us to Caustitech... awesome rants, sometimes *way* over the top, but generally there is a grain of truth in most of these. Since I have the "Architect" title, I really appreciated the description:

"ok, here i must admit that i've actually had this label attached to my name over the course of my career in software development. just shows how meaningless the word really is because i still have no idea what the hell it means. when i'm introduced to somebody who is the "Architect" i think to myself - "oh...somebody who couldn't code worth shit, but was in too deep to leave the tech industry." personally i'm of the persuasion that if you are calling yourself an architect you better be able to write some pretty fucking great code, or it's back to the drawing board for you, buddy. as a software developer how can you have any respect for somebody that is designing (no, architecting) a system and can't tell the difference between a for loop and a do...while loop? are you kidding me? it's been my experience that when developers need help with an implementation or integration detail, or have questions, they are going to go to you...and telling them not to bother you because you're working on something more important or that you don't have time isn't going to cut it."

This weekend I spent some time building a new framework ontop of the Avalon core... it felt really good to write some code. I must do more - it's always good to be reminded of that.