Live data from Hacker News

AT&T's Rube Golbergian Web Form

blog.joellehman.com

61–66 of 66 posts

Re: AT&T's Rube Golbergian Web Form

#61

Earlier quoted context omitted.

I don't think the parent is trying to justify the overall ridiculousness of the process, merely explaining what their rationale would be for even going down the IE-only path in the first place. I'm not sure if anyone can justify the need for ActiveX in this case.

The assumption that ATT needs to do it, is like assuming that a website needs to use cookies - it doesn't follow the money. The article implies that this process costs ATT millions, whereas logic would make the continued existence of such a practice unlikely and analysis of ATT's cost and revenue structure would indicate that it probably has the opposite effect on their bottom line. ATT's homepage for DSL customers i…

>The assumption that ATT needs to do it, is like assuming that a website needs to use cookies - it doesn't follow the money. The article implies that this process costs ATT millions, whereas logic would make the continued existence of such a practice unlikely and analysis of ATT's cost and revenue structure would indicate that it probably has the opposite effect on their bottom line.

Well, that's one way of interpreting it. Another way is to say that AT&T is a monopoly provider and therefore has no incentive to cut costs. The fact that the setup process is baroque doesn't cost AT&T anything - its not like customers have a plethora of alternatives for their broadband access. So, what AT&T optimizes for is cost of development, and I can assure you it was cheaper to develop this "solution" using half-trained consultants than it would have been to develop a well-designed setup page using experienced software engineers.

Re: AT&T's Rube Golbergian Web Form

#62
post #23

Earlier quoted context omitted.

Well, and how these reasoning justifies the need of ActiveX (the solely reason of IE8 installation) in order to fill in a web form?

I suspect that ActiveX enabled browsers allows them to further reduce support costs, e.g. installing a 32 bit version of IE8 allows the Flash driver to be installed thereby reducing calls from grandpa whose new system came with a 64 bit version of Windows 7 and therefor uses the x64 version of IE by default - not to mention that ActiveX also allows ATT to install more powerful software on the customers browser for su…

64-bit Windows actually uses the 32-bit IE by default. You have to use a special Internet Explorer (64-bit) shortcut to run the 64-bit version. I don't think that's an issue.

Re: AT&T's Rube Golbergian Web Form

#63

Earlier quoted context omitted.

This seems to be a good rule for calling any cable/phone ISP. The last time I mentioned using a Mac the support person ignored that I had already tried pinging certain gateways to check connectivity, and proceeded to condescendingly walk me through going to Applications->Utilities->Network Utility so that I could run ping from a tab there. Of course I quit after 15 min of this, tried to access again in a couple hours…

I'll add Rule 1A: Never talk net-speak with tier-1 support . "I've run some traceroutes and packets are getting lost at your router in Elmhurst. When I do get through, ping times are over 700 millseconds" "Okay, sir, what I'm going to need you do to is close your browser and restart it"

Is there no "I'm an IT professional. Please transfer me to someone that knows that I'm talking about" option for support?

Re: AT&T's Rube Golbergian Web Form

#65

Rule #1 when calling AT&T DSL support: Always, ALWAYS say you're running Windows with IE. Lie. Fake it. Whatever. If you say anything else you'll derail your support. Your goal is to get through the level 1 did-you-plug-everything-in-lets-restart-your-machine gauntlet. That, or go to the forums at dslreports.com and hope you can contact a sympathetic AT&T engineer.

This seems to be a good rule for calling any cable/phone ISP. The last time I mentioned using a Mac the support person ignored that I had already tried pinging certain gateways to check connectivity, and proceeded to condescendingly walk me through going to Applications->Utilities->Network Utility so that I could run ping from a tab there. Of course I quit after 15 min of this, tried to access again in a couple hours…

The last time I called comcast (in the middle of the night) I actually spoke to someone who used linux at home.

Quite surprising, and she was quite knowledgeable and helpful too.

Comcast also has some complex IE only registration, but if you call them and say you use linux they'll say no problem ask for the MAC of the modem and activate you on the phone.

Re: AT&T's Rube Golbergian Web Form

#66
post #59
post #21

So, you must have had IE6 or IE7? As much as I hate being forced to run any particular browser, one less machines running these old browsers is a good thing.

Typically, "upgrade your browser" techniques are welcomed in HN. Google drops support for IE6, then IE7 - smiles all around. Apps block off IE6 - "good for them". AT&T does something similar and it's met with frustration? Requiring IE* should be frowned upon. But anything that says "upgrade from IE6", in end-user land, is probably a good thing.

My frustration was because IE*, and thus some form of Windows was required. I use modern browsers, just never IE, and windows only when I must.

So I agree with your point about upgrading being a good thing, but the underlying absurdity is that something inherently platform independent (a webform) was perverted into something entirely specific to not only a particular OS, but a particular browser.

My ire with IE being updated was that I was never going to use IE ever again (by choice), whether it was 6 or 8; and so whether it was upgraded or not would not affect my browsing experience on sites other than this particular instance. So for me, it was just one additional hoop that I had to grudgingly jump through.

Post reply on HN