Readers Respond: The Knowledge Trek | eWeek

Readers Respond: The Knowledge Trek

Written By
eWEEK EDITORS
eWEEK EDITORS
Sep 19, 2005
1 minute read
eWeek content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More

I agree with Peter Coffees philosophy that “fixing problems” needs to become a routine, managed process, rather than a crisis event (Peter Coffees Epicenters, “The Knowledge Trek,” Aug. 8).

But … its not always that easy. What do you roll back when an application is failing for one set of users or performing badly on one server?

How can you roll back software that passed QA but is failing in production, yet is critical to some business objective? I wouldnt want to be the person telling the line-of-business vice president that its “OK” because we were able to roll back the release that underpins his new business product or service but that we have no idea what caused the problem.

Lori D. Wizdo
Vice President, Marketing
Identify Software
New York

eWeek Logo

eWeek has the latest technology news and analysis, buying guides, and product reviews for IT professionals and technology buyers. The site's focus is on innovative solutions and covering in-depth technical content. eWeek stays on the cutting edge of technology news and IT trends through interviews and expert analysis. Gain insight from top innovators and thought leaders in the fields of IT, business, enterprise software, startups, and more.

Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved

Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.