It’s the 1980s, and this pilot fish works in an accounting division, the place he responds to firm order to seek out methods to decrease prices by submitting a request to cease printing six ineffective stock reviews. “We at all times instantly tossed them into recycling, and it could save about 1,000 pages monthly,” says fish.
The response comes again from IT: “The stock system is so poorly documented that it could value extra to close down the print run than we might save.”
Request denied.
Flash ahead two years, and fish has dumped his accounting profession to turn out to be a programmer. His first task after transferring into the IT division: growing the measurement of a key discipline in the mainframe stock system.
That, in flip, means code must be modified in each inventory-related program. And ultimately fish finds himself gazing the report program that spews out these ineffective 1,000 pages.
Twenty minutes later, fish has recognized which six strains of Cobol code he must remark out in order to cease printing the six ineffective reviews.
“A fast name to my outdated boss confirmed he can be delighted to cease receiving the reviews,” fish says. “So I commented the report code and completed the key discipline modifications.
“In lower than 30 minutes we saved 1,000 pages monthly — two years after the request was denied.”
Copyright © 2020 IDG Communications, Inc.
