Opening segment was absolutely fantastic... entertaining, engaging, informative, and intriguing!

In today's world of over hyped technologies and tools, it's easy to get caught up in the excitement and come to realize that in just a short amount of time you have a highly coupled, and overly complex architecture on your hands.  This session was aimed at addressing some of these issues.

However, after the introduction... the presentation took a somewhat dry look at architecture... mainly focused on common sense approaches towards software development and solutions architecture.

As a solutions architect it our responsibility to understand the problem domain, understand the abilities of the team, understand the tools available to us, and possess the ability to analyze and make decisions based our on goals and resources at hand.

As a solution architect, you need to think about the following while developing all of your solutions:

• Communication, messaging
• Presentation, interaction
• State management
• Computational/Data Processing
• Resource management (solution/system resources)
• Tools

Reflections:

Inetium has several very good solution architects and we need to take full advantage of these people.  For many of these individuals their time is spent on non-architectural related tasks, and we often find ourselves with our heads down with busy work.

Qoute from the presentation: "Don't get caught up in the coolest trap", very reminscent of Kicking the addiction.