|I was supposed to have the call accounting system for a local hotel up this afternoon, but that was delayed by a slow computer. Finally, I ended up breaking the phone system enough that I had to make a visit and fix it in person. So much for getting home on time… I arrive, spend 40 minutes poking at the system and trying to figure out why the phone was plain ignoring anything I told it to do. Computer equipment that neither behaves as documented nor as logical is a real pisser. I end up having to chase after the front desk girl three times as she was out and about when her customers showed up. Finally, after an hour more of struggle with crappy software that was poorly designed, with no error readouts, I get it working. What should have been working in the first place.||I was supposed to have the call accounting system for a local hotel up this afternoon, but I know better than that. I’m happy to have budgeted more time than I needed, so they’ll be pleased when it’s up, whenever that is. I ended up breaking the phone system setting it up, but they’re a short jaunt away, less than fifty feet out of my path home. The nice girl I like works the front desk, so I get to chat her up and make light of the fact that I broke the phones — again — to break the ice and just end up enjoying myself. Even her customers are nice. Finally, after an hour, I discover an obscure piece of advice that makes the whole thing fall into place neatly. I think it solved some bugs that have been present in the system from day one as a side effect. The time wasn’t wasted even so, and I realized on the way home that it was billable.|
Pick your favorite version. I like the second one.