(no subject)

[learnedax]

It's a little strange being your customer's customer. My company makes the software that Comcast, among others, uses to track, manage, and correlate data on their broadband systems. That includes technical support usage. I am a Comcast customer. So, coming home on Sunday exhausted from the Novice Schola, and finding our network nonfunctional, I called them up. It slowly dawned on me that the quick response when my tech support guy pulled up my information was probably from the optimizations I did in June, and when he said "let me check if there are any other outages in your area" I was tempted to tell him which link to click on. Fortunately our connection to the internet fixed itself before we got very far, but my perspective still underwent about 180 degrees of rotation.

Comments

[mr-teem.livejournal.com]

I had that bizzareness a while back when I was having a printer vs. application problem on a printer that I owned that I had also worked on a couple years before that point.

These days, in just about any technical support situation, I find myself wanting to dump all of the relevant information (that is, all the information that I would expect on the receiving end) on the hapless first-level support person but get impatient as he... slowly... goes... through... his... script... and... tells... me... he's... sorry... I'm... having... a... problem... now... what... was... the... version... of... the... operating... system...?

[jducoeur]

First time I hit that was in my first post-college job -- I was writing the assemblers for many of the chips in GM's cars. (The chips came from Delco Electronics, and we contracted to do all their assemblers and compilers; I wound up in charge of the assembler project, which was fairly routine by then.) Nothing quite like driving a vehicle and knowing that, in some respect, it was built on your code...