Skip to main content

Loose Manhole cover II

PG County gets a silver medal for service.

I made a complaint to PG county about a loose manhole cover near our house on Jan 7th. On Jan 9th 3:13pm a gentleman called Wilkerson left a message on our phone system saying that he took a look at the manhole cover and its not part of the PG County drainage system, but belongs to Bell, so I'll have to call them. He also recalls coming over last year to take a look at the same manhole cover. I made a complaint via their web system last year! So they did come. They do exist!

So why am I being such a hard ass and giving them only a Silver medal? Well, Mr. Wilkerson was prompt, he looked into it, and he told me what he found, and how to proceed. To get the gold, PG County should have picked up the phone on my tax paying behalf and chewed out Bell (AT&T? or what ever they are calling themselves nowadays to hide from anti-trust).

Hmm, as a government employee I would have kinda enjoyed harassing a private company because they were giving bad service to a government sector client i.e. everyday Joe.

Anyhoo, Silver medal to PG County for
  1. Easy to find service
  2. Prompt taking of complaint
  3. Prompt response and investigation of complaint
  4. (BUT) Not going that extra mile to fully resolve complaint
Ok, now to track down bell.
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.
24 comments
Read more

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...
Post a Comment
Read more