I work in a small-to-medium sized business (over $25 million in revenues) as their “E-Commerce Manager”. In the normal course of my job I play many different “roles” from project manager and systems architect to software developer and tester depending upon our current project load and business strategy. I’m sure many of you reading this post are in exactly the same situation and “wear many different hats” depending upon the circumstances. This is especially true for people working in small-to-medium sized businesses (Microsoft’s target market for future growth) where staffing is lean and people handle more than one job function.
Why is it then that those of us who spent thousands on our MSDN Universal Subscriptions, have to “choose” between one of three different flavors (for Software Architects, for Software Developers or for Software Testers) of the new Visual Studio Team Edition? As you can imagine, each different flavor of the new Visual Studio Team Edition includes some very cool new tools designed for the specific “role” the edition is targeting.
What happens if your week is like mine?
Monday: Write up project plan and layout overal architecture for new e-commerce web application.
Tuesday: Finish BizTalk orchestration for outbound invoices to customer XYZ.
Wednesday: Review SQL developer’s new stored procedure code and logic.
Thursday: Run load tests on new public web site redesign.
Friday: Debug C# code in new currency translation web service.
As always, your comments are welcome and appreciated!