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

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more