This is funny. At one client, my team would yell, "The Architect!" in a very sarcastic manner to remind me I was just a developer with a few years on them. I ag

This is funny. At one client, my team would yell, "The Architect!" in a very sarcastic manner to remind me I was just a developer with a few years on them. I agree, the title can be misused or offer an inflated sense of self for some. A reminder though... I was considered a .NET Architect from about 2004 to 2009. I'm an independent contractor, so I'm always changing clients. In 2009/2010 I would get calls and the recruiters would talk to me about senior developer roles. I would complain, "I'm really an architect," and they would say, "Not anymore. You don't have any front-end architecture experience and your JavaScript background is weak." Lesson learned. You may be an architect for a moment, but to maintain that title, you have to continue to learn and grow. If you don't, you may find out you're just a legacy programmer. I'm sure that can be very humbling.