Having used my initial post to describe what my blog is about, I now find myself thinking of issues I don't plan to discuss. To get this off my chest, I'll briefly discuss here what I don't plan to discuss further in the future.
I can think of at least two topics I won't be spending much time on:
Emerging technologies - While it's interesting to talk about where technology is going, that insight is difficult to apply to the applications we're developing in the present. I'll be focusing on development using the commercial-quality products we have today and techniques that can be applied now. Not too surprisingly, given my employment, the products I'll focus on will be WebSphere Application Server and WebSphere Studio Application Developer. For a discussion of the future, please visit my fellow blogger James Snell.
Methodologies - As long as I've been developing software (fourteen years or so professionally), there have been competing mega-processes for software development. They tend to be about 87 steps long and can require an army of consultants just to handle the paperwork. Making 85 of the steps optional doesn't make using the process any easier; then you don't know which steps to keep and which to skip. If you find that applying a methodology is helpful to you and your team, then more power to you. But I've seen plenty of teams get in trouble either because they get bogged down with following all of the methodology's steps or because they dutifully adhered to some methodology's dictates without truly making their development process better. "How can our application not work? We followed the methodology precisely." It's up to you to monitor how your project's doing; keep what works and change what doesn't.