{"id":5256,"date":"2016-10-18T16:17:56","date_gmt":"2016-10-18T21:17:56","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=5256"},"modified":"2016-10-18T16:17:56","modified_gmt":"2016-10-18T21:17:56","slug":"like-a-good-gardener-help-an-enterprise-keep-itself-current","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2016\/10\/18\/like-a-good-gardener-help-an-enterprise-keep-itself-current\/","title":{"rendered":"Like a Good Gardener, Help an Enterprise Keep Itself Current"},"content":{"rendered":"

\"25654050293_a6ac9c67a9_c\"<\/a>Here’s a great analogy<\/a> for technical writers from the “Stories From the Software Salt Mines” blog. Sure, you can keep adding features (in the form of text and photos) to whatever technical content you’ve been developing for months, or years.<\/p>\n

But if you haven’t been conscious of keeping it all fresh and organized appropriately, if you’ve just been adding on…and on, watch out. Or if you’ve been describing an aging system as though it’s still new, that could be a double whammy. <\/p>\n

“Software as a garden: to be able to grow more software, to be able to grow revenue with it,” the blog writer notes, “you have to keep the soil fertile and give the roots room. The problem is, gardening projects are a hard sell. These are things like refactoring older parts of the code that no longer serve efficiently, or upgrading or replacing outdated parts of the architecture, or redesigning subsystems that work fine today but can\u2019t adapt to things the company wants to do in the future. When you tell executives you need to do these things, what they hear is that they can\u2019t have new features while you do it. New features fuel growing companies.”<\/p>\n

In short, you need to be observant, that is, current, as you write. If the setting you’ve been active in has been aging (and what settings haven’t?), have you kept it current in your own awareness and thoughts, and pointed out to its owners what you’ve been observing? <\/p>\n

If you’re simply chronicling an aging, though originally awesome, system, watch out! If you don\u2019t “tend your garden,” contribute to keeping it current, sooner or later it will stop producing. And nobody should be surprised at that. <\/p>\n

Yet, notes the writer in the Software Salt Mines: “It was much the same story: the company had focused entirely on rapid new-feature delivery and not enough on ongoing design and architecture. After a decade, their soil had gone infertile and the code had become tangled. Nothing new would grow.”<\/p>\n

A good gardener helps maintain the conditions for growth. So does a good technical writer. \u2013 Doug Bedell<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Here’s a great analogy for technical writers from the “Stories From the Software Salt Mines” blog. Sure, you can keep adding features (in the form of text and photos) to whatever technical content you’ve been developing for months, or years. But if you haven’t been conscious of keeping it all fresh and organized appropriately, if […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5256","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t