I had a bunch of third-generation copies of cassettes (yes, *cassettes*, dammit!) of Blue Oyster Cult albums back in high school. Never could figure out the damned lyrics. They *sounded* like "mistress of the salmon salt", and "the queenly flux, eternal light", but they couldn't be. Those phrases and most of the others I thought I heard made no sense. But try as I might I couldn't twist the sounds into anything coherent.
Then they invented the Internet, and I could look up the lyrics online.
Fuck.
Someone who wants to be offended can find reason to with anything.
It sounds to me like the group who should *really* be offended are the computer engineers for being so badly misrepresented. Oh, and Barbie fans because it makes Barbie (not women in general, just this particular woman) look like a freaking idiot. (Going on the descriptions here; of course I haven't read the book. Who needs actual facts when we're surrounded by all this juicy hearsay and speculation?)
And yes, "genderally" is a perfectly cromulent word.
And say, exactly, "Hi, I have a business account. I can't email my customers who use Yahoo, Hotmail, and Gmail, apparently because those providers are blocking mail originating within Comcast's IP space. This needs to be fixed or your business account is worthless to me and I'll consider it a breach of contract." Work with them. The answer might be to move you to a different block of IP addresses. Or, it might be to forward mail through their servers. There is undoubtedly a solution.
Also, talk to Yahoo, Hotmail, and Gmail about being blocked. Maybe they can tell you what criteria you're hitting. It may not be Comcast's fault. (I know it seems incredible, but it is a possibility. Really.)
Lastly, if you can't get satisfaction from Comcast but there really is no alternative ISP that works for you, you can purchase email service from hundreds or thousands of different providers out there. Get an account somewhere else and set up your server to forward through theirs.
"You are not looking for me to write a list API, you're looking for me to write much higher level code. If the environment you are using don't provide a list API, you are in trouble."
Speaking as someone who often poses that sort of question in an interview, yes, I know. I sometimes even preface that portion with, "I know that no one should ever again have to write their own implementation of this, but..." No, in the job you're not going to be asked to write elementary data structure code. It's just a tractable problem which can be done in the amount of time available, and makes a good starting point from which to discuss code complexity, time/space tradeoffs, and similar subjects which you *will* need to know in order to do this job.
And you would be amazed at the number of candidates who can't manage even the simple stuff. No, I don't need someone who can write yet another linked-list traversal. I need someone who can do much more difficult things! If they can't even do the sophomore-level stuff then there's no need for either of us to waste any more time. (Seriously, I've been to on-campus career fairs where by the end of the day I just want to tell people, "Pick a programming language. Any language. Write 'Hello, world'." Because I've come across a number of soon-to-graduate CS majors who couldn't even do *that*. I am not exaggerating.)
This research brought to you by the letter "Duh!" and a grant from the Really Freaking Obvious foundation.
I suppose it's good to have a study to back up the obvious. It's just that, according to the study, the people most in need of convincing are exactly the same people who are going to most vigorously deny the validity of the study.
Remember, UNIX spelled backwards is XINU. -- Mt.