That's not xenophobia. There's a strong stereotype / reality of outsourcing to the cheapest country and the cheapest call center in that country. It has nothing to do with the race or location of those people.
This is what finally got my Charter working (and they later discovered the unshielded RG-59 cables buried outside my apartment). But Charter got rid of all of their social media and UMatter2Charter accounts a couple months after that. Literally discontinuing something called "UMatter2Charter" without a replacement is a bad sign.
I kept a log once - AT&T DSL and I lived 2 blocks from the CO. Turns out there were two breaks in my line between my apartment and the CO (and plants growing like crazy in the box down the block.
Just a basic uptime up/down log by time. I think from a cron job checking the status page of the modem.
I do have a client with a German accent, but I think I've gotten very good at deciphering rhyme-alikes. That's probably one of the easier accents, but I've even started to learn rhyme-alike phrases.
Looks to be a lot more to do with the complexity of the project and the number of people interacting with it on a deep level.
Click a few bugs and see if any of those appear to be related to the language chosen. They really don't. If anything, it shows how little coders understand about XSS (especially with respect to an often authentication-free CMS) and that parsing user-uploaded SVG and PDF files is full of potential difficulty.
I didn't say there are no such large projects. But Wordpress is really bad code. Or at least b2 was before it was Wordpress. phpBB is far worse. But you don't even have to understand PHP much to know what's wrong. A lot of larger projects are run by people who see nothing wrong with putting unsanitized GET variables directly into a db query.
I won't sugar coat this: PHP allows you to write security vulnerabilities into your code. But it doesn't require it.
You just have to actually understand vulnerabilities and be the one working to avoid them. I wouldn't use ANY large open-source piece of software written in PHP as an example. There is a LOT of garbage out there. But it's not hard to understand SQL injection and any of the other risks.
PHP is a web language that runs a script per page view and there is no state saved between page loads (other than a session variable that is stored to disk).
Object-oriented programming is great, but it is really a lot of overhead when you're creating and destroying the objects on every page load. I'll admit I've created a few classes in PHP, but most of the work I do simply doesn't require it.
Which is silly, considering that a printed document can look exactly like a faxed document. More than once, I've sent a PDF with a PNG signature overlaid and just said "Please print this and pretend it was a fax."
I think Google Voice's method of voicemail is going to have to become a lot more common soon. When I get a voicemail, it shows up as a transcription in Hangouts as if it were a text message. Yes, there's a play button but I don't really need it.
It's not the fault of the person leaving the message that you don't have a good workflow for voicemail.
Voicemail... Well, if voicemail worked like texting I wouldnt mind it. But no. Instead of just glancing at my phone to see the latest text on the screen I have to unlock my phone, press the voicemail button, wait for it to pick up, enter a pin number, listen to any messages that are about to be deleted (including the phone telling me when it was left and what number left it) and THEN I get to listen to my wife say "oh, never mind I found it myself".
Yeah, you need Google Voice (or something like it). The transcription of the voicemail shows up in Hangouts as if it were sent as a text. And the transcription doesn't have to be that accurate to make actually listening to the message obsolete.
But that's why you just let the call ring through to voicemail. Then it's a fancy instant message with voice. Voicemail isn't bad if you have transcription like Google Voice.
An IM is no less an interruption than a voice call.
And the theory and the experiments and the hypotheses are science. Observations are the beginning of science, but any facts that come from pure observation are not scientific facts.
And no, direct observation can't be trusted fully so the whole "observed occurrence is fact" has to be seen through the lens that no observer is perfect.
Blue is a name for a perceptual concept. That a wave of photons at a wavelength of 475 nm is blue is not a fact, but a definition/tautology. Even calling light a wave (vs. particle or wave/particle duality or whatever more accurate undrestanding we come up with in the future) is more theory than fact.
Saying that a blue thing is blue is a fact, but not a scientific fact. It's just a tautology.
I agree - but that's because I don't think that the word "fact" should exist in a scientist dictionary. Theory is science's highest honor, not fact. It's the wrong mindset for expanding knowledge to have hard set rules. I feel like this hard clinging to the word fact is just a fight against the religious and not based on anything rational.
Just think about how much our idea of something as simple as light has changed in even the last 50 years.
Science's highest honor to an idea is to call it a "theory." Even gravity is a "theory." There are no "facts" in science.
I think presenting anything as fact in a science class is dangerous. It presents science as a completed work instead of an ongoing refinement. Not really a good lesson for the future generation, either.
Slashdot Mirror
That's not xenophobia. There's a strong stereotype / reality of outsourcing to the cheapest country and the cheapest call center in that country. It has nothing to do with the race or location of those people.
This is what finally got my Charter working (and they later discovered the unshielded RG-59 cables buried outside my apartment). But Charter got rid of all of their social media and UMatter2Charter accounts a couple months after that. Literally discontinuing something called "UMatter2Charter" without a replacement is a bad sign.
I kept a log once - AT&T DSL and I lived 2 blocks from the CO. Turns out there were two breaks in my line between my apartment and the CO (and plants growing like crazy in the box down the block.
Just a basic uptime up/down log by time. I think from a cron job checking the status page of the modem.
Verizon Wireless is 50% owned by Vodafone last I knew.
Dosbox works way better than it should for this. And there's always Bochs or Qemu.
Look next to the CPU on just about any motherboard. There are caps there for power filtering specifically for the CPU.
I do have a client with a German accent, but I think I've gotten very good at deciphering rhyme-alikes. That's probably one of the easier accents, but I've even started to learn rhyme-alike phrases.
Looks to be a lot more to do with the complexity of the project and the number of people interacting with it on a deep level.
Click a few bugs and see if any of those appear to be related to the language chosen. They really don't. If anything, it shows how little coders understand about XSS (especially with respect to an often authentication-free CMS) and that parsing user-uploaded SVG and PDF files is full of potential difficulty.
I didn't say there are no such large projects. But Wordpress is really bad code. Or at least b2 was before it was Wordpress. phpBB is far worse. But you don't even have to understand PHP much to know what's wrong. A lot of larger projects are run by people who see nothing wrong with putting unsanitized GET variables directly into a db query.
I won't sugar coat this: PHP allows you to write security vulnerabilities into your code. But it doesn't require it.
You just have to actually understand vulnerabilities and be the one working to avoid them. I wouldn't use ANY large open-source piece of software written in PHP as an example. There is a LOT of garbage out there. But it's not hard to understand SQL injection and any of the other risks.
PHP is a web language that runs a script per page view and there is no state saved between page loads (other than a session variable that is stored to disk).
Object-oriented programming is great, but it is really a lot of overhead when you're creating and destroying the objects on every page load. I'll admit I've created a few classes in PHP, but most of the work I do simply doesn't require it.
That's an implementation problem, not a problem with the concept.
But just seeing cream pewter is enough to know it's a computer issue. So it's not like it doesn't provide any context.
Answering machines are devices that implement a voicemail service. Some voicemail systems are 100% software-based.
Which is silly, considering that a printed document can look exactly like a faxed document. More than once, I've sent a PDF with a PNG signature overlaid and just said "Please print this and pretend it was a fax."
I think Google Voice's method of voicemail is going to have to become a lot more common soon. When I get a voicemail, it shows up as a transcription in Hangouts as if it were a text message. Yes, there's a play button but I don't really need it.
It's not the fault of the person leaving the message that you don't have a good workflow for voicemail.
Voicemail... Well, if voicemail worked like texting I wouldnt mind it. But no. Instead of just glancing at my phone to see the latest text on the screen I have to unlock my phone, press the voicemail button, wait for it to pick up, enter a pin number, listen to any messages that are about to be deleted (including the phone telling me when it was left and what number left it) and THEN I get to listen to my wife say "oh, never mind I found it myself".
Yeah, you need Google Voice (or something like it). The transcription of the voicemail shows up in Hangouts as if it were sent as a text. And the transcription doesn't have to be that accurate to make actually listening to the message obsolete.
But that's why you just let the call ring through to voicemail. Then it's a fancy instant message with voice. Voicemail isn't bad if you have transcription like Google Voice.
An IM is no less an interruption than a voice call.
Exactly. It's "observation and", never just "observation."
And the theory and the experiments and the hypotheses are science. Observations are the beginning of science, but any facts that come from pure observation are not scientific facts.
Observations are facts, I can grant that to some degree. But observations aren't science. So science has no facts.
And no, direct observation can't be trusted fully so the whole "observed occurrence is fact" has to be seen through the lens that no observer is perfect.
Blue is a name for a perceptual concept. That a wave of photons at a wavelength of 475 nm is blue is not a fact, but a definition/tautology. Even calling light a wave (vs. particle or wave/particle duality or whatever more accurate undrestanding we come up with in the future) is more theory than fact.
Saying that a blue thing is blue is a fact, but not a scientific fact. It's just a tautology.
I agree - but that's because I don't think that the word "fact" should exist in a scientist dictionary. Theory is science's highest honor, not fact. It's the wrong mindset for expanding knowledge to have hard set rules. I feel like this hard clinging to the word fact is just a fight against the religious and not based on anything rational.
Just think about how much our idea of something as simple as light has changed in even the last 50 years.
Science's highest honor to an idea is to call it a "theory." Even gravity is a "theory." There are no "facts" in science.
I think presenting anything as fact in a science class is dangerous. It presents science as a completed work instead of an ongoing refinement. Not really a good lesson for the future generation, either.