Why developerWorks blogs?
This past week, during a developerWorks content summit, our content team enjoyed a rare few days in the same physical space. Aside from all the work sessions, we spent a brief moment patting ourselves on the back, both for our latest Jolt Product Excellence Award, and for some positive results in our latest site visitor survey report.
The survey results were quite encouraging: Our visitors responded positively to the update we implemented last fall, designed to make the developerWorks site more cohesive and intuitive. (For some details, see "A new look and a new foundation for IBM developerWorks.") Across the board, our user satisfaction scores -- already among the best in all of IBM -- improved. The team was quite pleased to see our hard work pay off. (Kudos and thanks to all involved, and particularly the extra efforts of the design, usability, infrastructure, and production edit teams as well as the broader content team.)
But we (like most of you, I'd imagine) can't afford to rest on our laurels. We're always striving to better understand our audience of developers and technical professionals so that we can deliver the stuff you seek -- what you want and what you need to be successful. We also realize that developers are a diverse group, with diverse priorities and interests. That's why developerWorks provides a diverse set of resources -- including robust sections of the site dedicated to top open standard technologies (Java, Linux, SOA & Web Services, ...), as well as top developer and technical products used by IBM customers (Rational, WebSphere, Lotus, DB2, ...). That's why we're always looking to enhance our value by adding new materials, exemplified by recent additions such as the Autonomic computing zone and Migration station. That's why we offer an array of types of resources -- articles, tips, tutorials, tech briefings, conferences, trial code, alpha technologies (via alphaWorks), white papers, trial code, and more.
Blogs are our latest addition. We hope to add quite a few more people to our ranks of bloggers in the coming weeks. Our goal here is to provide a direct line to some individuals within IBM who, whether widely recognized visionaries and thought leaders or unheralded technology experts and innovators, have worthwhile insights to share: nuggets of wisdom, timely references to useful news and technologies, helpful discussion and perspective on emerging industry trends, forward-thinking strategic views, important questions, and more. Our hope is that some of this shared knowledge will help you be informed, aware, and ultimately successful.
The collective intellectual capital within IBM may be unmatched in the industry. With the developerWorks blogs, we hope to tap into this rich resource and share some of it with you. Think of our blogs as virtual conversations with some experts and insiders who might know a bit more than your typical colleague (not in every area, of course, but in their specific areas of expertise), and who occasionally share their insights with you in their own personal voices. We realize (and our recent customer panel discussion confirms) that not every developerWorks visitor will frequent our blogs. But that's OK. The same can be said of just about any other developerWorks resource. For those of you who do come to this corner of developerWorks, we'll strive to make your visits rewarding. And we encourage you to participate, to engage in dialogue by sharing your own comments with our bloggers.