#24648
The purpose of this collaboration is to collect on one portal page many of the current theories of software development, so that a technical communicator working with developers can at least be a bit familiar with these. It is by no means a thorough explanation of all the contemporary methodologies, both organic and imposed. But it should give readers some tips about what they are and where they can find more information.
Albing, Bill. KeyContent.org (2004). Articles>Software>Programming
#24645
Then is Now, Small is Big: Transforming Trends
This article is not really about the future; it is about the present, because the future is already upon us.
Albing, Bill. KeyContent.org (2004). Articles>TC
#28962
Do you ever think about how much time you spend tackling process issues and tools issues? The tools, as advanced and automated as they are, will not fix all our problems. But we have to work with what we have, and automate as much of the production and maintenance of our content as possible.
Albing, Bill. Carolina Communique (2006). Resources>Software>Tools>XML
#24647
Transforming Communication: The Dynamic Nature of Key Content 
Technical communication is a profession and a discipline in its own right and that it must determine whether it will be part of the game or give the reigns of thought leadership to another group outside our profession.
Albing, Bill. KeyContent.org (2004). Articles>Content Management
#24646
Trends in Transforming Communication: Response to STC Editorial
In stark contrast to the suggestion that software products are easier to use these days, I would have to say that in general they are _not_ any easier to use, _especially_ Microsoft products. While they have more features and deliver more performance, I would be careful about making a blanket statement about ease of use, especially when we know the resources to create usable products in most of the industry has been shrinking.
Albing, Bill. KeyContent.org (2004). Articles>Usability>Software
#27999
Using a Wiki as an Organizational Portal
We explain why we chose a wiki-based content management system (CMS) as the basis for the portal for KeyContent.org. We compare various tools and discuss other sites that have implemented similar software for collaborative solutions.
Albing, Bill and Rick Sapir. KeyContent.org (2006). Presentations>Technology>Organizations>Wikis
#29197
Wiki-fying Docs: Is Using Customer-Accessible Wikis for End-User Documentation Gaining Momentum?
While the effort to provide more interactivity and power to the end-user seems to suggest that we open up a wiki to allow them to add and edit content, the basic idea of a set of edited documentation is now challenged with a social network of participating customers, all of whom may now edit, add, and delete content. How social can you go? This article is an attempt to look at the process of evaluating the use of a wiki for end-user documentation, if such a thing can exist. Are the two types of customer content--wikis and end-user documentation--mutually exclusive?
Albing, Bill. KeyContent.org (2007). Articles>Documentation>Wikis>Social Networking
#28168
There is much left to be done with words. I think the trend toward more graphical interfaces will continue, but so will the complexity of the technology we develop. So there will always be a need for communication experts to figure out the best wording for the details involved in that technology. Finding the best way to articulate ideas and communicate information for making decisions will continue to be our bread and butter. We will see who has the last word.
Albing, Bill. Carolina Communique (2005). Articles>Writing>Technical Writing
