Geeks With Blogs

News Opinions and articles on this blog are mine alone and do not represent my employer. All articles and blog entries are posted using a personal computer system outside of my employer network.
Sam Abraham Software Engineer/Architect: Putting Customers First
On Thursday October 28th, 2010, I had the privilege of attending and speaking at the SoFla Local PDC10 hosted by the Gold Coast and Miami .Net User Groups. While most local PDCs focused on viewing the Redmond event, South Florida kicked it up a notch by availing some of the community’s local speakers to comment and address any questions the audience might have. I greatly enjoyed covering and answering audience questions on WebMatrix, Razor Syntax, ASP.Net Web Pages Helpers, IIS Express, ASP.Net MVC 3 and NuPack. A thank you is in order to Joe and Maureen Homnick and others whose tireless work and support made this event a success.  
Throughout the day-long event, I had the opportunity to chat with many professional developers from both small and large organizations in both public and private sectors.  Tools, frameworks and architectural patterns we discussed varied based on the nature of the business, company size, budget as well as specific product requirements. I am by no means an expert, but I found myself repeating the following in most conversations:
  1. Planning is priority one. In order to put the correct technology to service, one first needs to fully analyze short as well as long term project goals.
  2. The triple constraints: scope/quality, time and budget need to be delicately balanced. Looking at cost alone will probably sacrifice either or both product quality and feature set. Focusing on quality alone however is bound to jeopardize the project as it increases the likelihood of running over budget.
  3. Need to balance all Stakeholders’ needs. A good strategy to balance all stakeholders’ needs is to work with all parties to break a project into smaller manageable pieces/functional areas (phases). Furthermore, it would be ideal if each phase creates a complete feature even if simple. This strategy would ease the following:

-Reusability. Should the plug be pulled off a project, already-completed features can always be documented for future re-use thereby resurrecting part of the time and money already spent.

-Measuring Progress. Periodic evaluation of completed features enables non-technical stakeholders to get a feel for project progress without the need for a translator to decipher geek jargon.

-Stage Gating. Despite the hard work, tools and measures applied to analyze the feasibility of a project before execution, a project might no longer be a good fit for the company at a later time. Regrouping to evaluate an implemented feature can also act as a gate to evaluate project continuity.

Putting my geek hat back on, I would like to share the following ressources I brought up at the event:
1-A great resource page for WebMatrix development can be found at:
2-You can run ASP.Net MVC 3 side-by-side with ASP.NET WebForms in the same Visual Studio solution.  Scott Guthrie wrote a nice chapter on this and made it available freely to all, so feel free to lookup. Other articles and webcasts have also addressed this situation. For instance, the following article provides a nice sample and coverage of the topic:

--Sam Abraham 

Posted on Sunday, October 31, 2010 4:23 PM , MVC2 , PMI , WebMatrix , ASP .Net MVC 3 , ASP.Net MVC 3 Beta , Razor Pages , ASP.Net Web Pages , MVC 3 | Back to top

Comments on this post: Reflections on SoFla Local PDC10

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Sam Abraham | Powered by: