Computerworld - ... can lead to blurry vision. So asserts Dr. Jeffrey Anshel, who has practiced optometry for 30 years -- specializing for the past 15 in the eye problems of computer users through his practice, Corporate Vision Consulting, in Carlsbad, Calif. Anshel observes that conventional ergonomic wisdom has us sit up straight at our desks. But ergonomics experts "straighten our posture by pulling up our eyes," he says. Not only is that awkward and uncomfortable, but it's wrong for reading, according to Anshel. "We should be looking down when we're reading," he contends, saying that people sitting in front of computers should also have a slightly lowered posture.
But even with such modifications, IT professionals, who topped a 2005 MetaFacts Inc. survey as the workers who spend the most time in front of computer screens, are fighting against nature just doing their jobs. Human eyes evolved to see long distances, not to do close-up work, Anshel explains. What few near-range tasks they are adapted for should be done on a horizontal surface, such as a table or workbench -- not the vertical plane of a computer display. Eye problems can be serious and include double vision or color distortion, not to mention the more common problems of blurred vision and headaches, says Anshel. So keep an eye on your posture. Slouch a little.
... yields lessons. Ida Salazar, vice president of information and communication technology and special projects at AAA Oregon/Idaho, is rightly proud of leading the rollout last winter of VoIP services as part of the regional travel service firm's new business continuity plan. In a mere 119 days, the Portland, Ore.-based affiliate of the national AAA automobile association chucked out 16 aging PBX systems and installed VoIP technology in 22 locations for 500 call center employees, who handle a total of 4 million calls per year. Salazar says that AAA Oregon/Idaho will see a full return on the project within three years just in the savings from remote workers no longer using internal toll-free numbers to connect with colleagues. Still, Salazar says that in hindsight, she would have done a couple of things differently. For example, she'd request funding upfront for network testing tools to use during and after the installation. Also, she'd make sure users were satisfied with service and performance levels before letting the VoIP team move on. One location had intermittent performance problems that weren't fully addressed before the project team went to the next site,
Free Insider GuideCopyright © 1994 - 2012 Computerworld Inc. All rights reserved. Reproduction in whole or in part in any form or medium without express written permission of Computerworld Inc. is prohibited. Computerworld and Computerworld.com and the respective logos are trademarks of International Data Group Inc.
