Contact Tampa Bay IASA Chapter for event and ticket information.
Thursday, July 31, 2008 from 6:30 PM - 8:30 PM (ET)
"Fix the Architecture" - Open Discussion
We have a great group of members with a variety of experience, so bring your architecture problems and leverage those experiences and creativity to help solve them. This is an open discussion format and depending on how many people we have and how many problems we may split up into small groups or try to solve problems one at a time.
If you have a question/topic to discuss please let me know by Monday, July 21 or when you register for the meeting. After the 21st, I will make the topics submitted available as a survey on SruveyMonkey so everyone can vote and be prepared for the discussions.
Please be aware that the outside doors lock and the elevators need a security key after 7:00 PM.
Don't forget to sign up for our free newsletter!
Registration opens on June 26, 2008.
The Tampa Bay chapter of the International Association of Software Architects (IASA) is dedicated to building a community of professionals interested in topics related to software architecture, and welcomes anyone who is actively working as a software architect or has an interest in becoming one.
We hope to provide a mechanism for software architects to network with each other, provide a technical outlet and information source to help keep up with the latest trends and technologies, and also help foster new speakers. We are mostly Microsoft focused, but we try to keep the topics as product-agnostic as possible and always keep the focus on architecture related topics.
 |
View other Tampa Bay IASA Chapter events |
 |
Contact the Host |
 |
Subscribe to receive notifications of future events by this host |
News & Updates
SurveyMonkey won't let me share the actual results page on a free account, but here are the results:
|
Troubleshooting performance issues. Your outlined architecture should scale and yet performance isn't within the agree'd upon level of service. What techniques should round out your organizational "protocol" for dealing with performance issues? |
66.7% (8) |
| Inversion of Control: Dependency Injection vs. Dependency Lookup; Contracts: Interfaces vs. Abstract Classes. | 76.9% (10) |
As you can see, both questions were very close so we will try to cover both of them.
Topic submission has closed. Please vote on your favorite meeting topics.
Email
Facebook
Twitter
LinkedIn
MySpace
Digg
del.icio.us
Reddit