Continuing with this series on my plans for MSDN Magazine, I’ll address here another question that I’m getting often these days.
While a few posts ago I talked about the mindsets on which my content strategy is to be based, it’s now time to talk a bit about the concrete stuff I’m envisioning, in order to turn my editorial line into something more tangible.
The magazine today is composed by certain regular sections, known as columns, and completed with features: extra articles not tied to any of those columns in particular. In practice, as one of my partners made me notice, columns are less regular than expected as they don’t appear on every issue each, but they actually alternate their occurrences.
In that sense, the idea of reformulating the column lineup has as goal to narrow the set of columns in something that covers the whole development scope, but it also is definite, predictable.
The current alternating column lineup comprises:
Regarding the thoughts above, what the reader may expect is some merge between columns of similar kind and perhaps the removal of certain columns whose frequency is beeing remarkably low. In that sense, it is not that we’ll stop publishing that kind of stuff forever but will do it as feature articles, not as regular columns.
What you are about to read now it’s not yet consolidated as I’m still working with different stakeholders in order to arrive at by consensus and cross-validation; ensuring that no gaps will remain unclosed in this content strategy and that the overall plan is realistic. Do you want to hear my early conclusion so far? Making this kind of project plans, dear reader, doesn’t differ that much from making software project plans! Indeed, one have to align expectations coming from different parts, with a particular perspective each. As I don’t want to leave you out of this debate, I’m publishing hear my thoughts in order to get your feedback. Don’t miss the chance and get involved. Be part of the magazine you want to get.
Based on the mindsets and the blueprint sketched in the last post…
Figure 1. A typical N-tier, layered architecture.
… this is a tentative column lineup intending to cover all those aspects that must be present in professional application development. Let’s see:
So, I listed ten tentative columns. These are still preliminar and the idea of publishing there was to satisfy the anxiety about what plans I'm envisioning. It will require some reviews, reworks in order to be confirmed. That should happen in the next few weeks.
And, before finishing, what about the featured articles? What will they be on? In principle, they are intended to be based on the monthly theme (I’ll offer a post on upcoming themes soon). That may not be the case for every featured article but, if not, will be just the exception and probably because some of the columns will be also based on the monthly theme. I’ll cover all these in further detail soon.
Diego Dagum Editor Director MSDN Magazine