I wanted to start a general discussion on "bootcamps" - or full day events where we focus on a single topic. Initially, I think our first bootcamp should focus on .NET basics and OOP, that way people new to the technology can get up to speed and are better prepared for some of our more advanced topics at the user group meetings.
Would anyone be interested in Lakeland .NET bootcamps? This would be different than a codecamp because we would focus on one (perhaps two) subject(s) and make people knowledgeable on that subject by the end of the day.
Possible subjects would include:
.NET and OOP Basics C# or VB .NET Language Features ASP.NET Silverlight Application Architecture 101 WCF 101 Anyone have an interest in this? I want to make sure there is enough demand before I move forward so please speak up if you are interested - or perhaps there is some other type of activity that interests you.
-Roy
You've got my notes. I'm torn on the survey, because what I'd want as an attendee is different from what I'd be able to provide as a speaker.
Architecture really depends on application scale and requirements. A "day of" that examines all the tradeoffs would just be repeating Microsoft's P&P Architecture Guidance (http://www.codeplex.com/AppArchGuide). It's too vague until you at least pick a target platform. Desktop vs Silverlight vs ASP.NET vs multiple target platforms determine half the decisions. So case studies might be the better way to go for architecture. "Here are two design patterns, with 3 implementations each, just for solving this small problem in a Silverlight app talking to WCF. We chose this one because..." and then actually getting into code is more approachable than "here are some things to think about". Tampa also has an IASA chapter that meets at the Microsoft Tampa office for some of this, but seems more "big picture" than I'd expect us to target.
I find myself more interested in advancing the profession than in any particular project, partly because I've made numerous design decisions based more on whether my coworkers could be expected to maintain the code than by what best meets user needs. So let's work on figuring out good ways to build applications, and become a local resource for learning, asking questions, and sharing horror stories (and sometimes beers) along the way.
So put me down for pretty much anything. The topic determines whether it's as speaker, volunteer, or student. :)