I liked the bit about her making a point of mentioning she drank a significant amount of alcohol after the incident, and that she normally doesn't do this, but hey, I was stressed out.
For those of you who've never had to deal with things like domestic abuse, that's classical weasel talk for "I was drunk as a skunk and misbehaved as a result, but I won't admit it". It was no doubt prompted by the police smelling her breath or seeing an empty bottle, and asking uncomfortable questions as a result.
We'll never know what really happened, but I'm going with "abrasive drunk woman tears techie a new one" here. Although I can understand someone losing their cool after such a long and fruitless struggle to get their connection fixed.
Consumers buy overpriced A-brand products. A-brand companies spend part of that money on TV advertising. The TV advertising money goes to the IOC for the broadcasting rights.
It's so easy to underestimate the actual cost of a text message. Screaming "it's only 160 bytes, this is stupid" is making you look rather stupid.
A message that is sent also needs to be received. So all the network traffic is double. Once to send, once to receive. And the radio network overhead is much more than just those 160 bytes in the message.
And then you have all the infrastructure necessary to handle the messages. It's not point-to-point, it's store and forward. A network operator needs to invest quite a bit of money in the systems that handle the text messages, with all their interesting features, the billing, etc.
Of course texting is still ridiculously expensive, I'm not going to argue that. But using baseless numbers and ignoring the behind-the-scenes infrastructure to "prove" a 17000x markup on text messages is nothing short of moronic. And so is saying that texting is equivalent to paying $24000 for an MP3.
You don't. Twice a year some good soul with good intentions comes along who observes the chaos that is your IT/Enterprise infrastructure. 'We will track all our assets in one beautiful database!' they say. 'We will finally know what is going on in our network' they say.
A project is started, a gaggle of consultants make a boatload of money, and introduce a system that is uncomfortable to use and barely meets the stated requirements. Everybody is ordered to use the system, but nobody is clearly responsible for keeping it up-to-date and nobody bothers to check on the accuracy later on.
After 6 months the system is in total disarray, but because nobody repeals the decision that it is the Official System [TM] and because it cost so much to build, it's there to stay along the other Official Systems [TM] that nobody uses. That's when the idea for the next Official System [TM] pops up.
Sounds negative? You were talking about Enterprise systems, right? This is how it works in every big company. Don't fool yourself into thinking it can change. Enterprises don't change. They slowly morph around problems to avoid them, not to solve them.
The solution? Do it locally. Figure out a convenient way to track the IP address subnet assignments in your network, and use it to keep track of your address space. Use an Excel sheet for all I care to keep track of firewall rules. Use domain-specific tools, and use them only for that domain. Avoid the temptation to create the Universal Solution To All Problems because it won't work. Down that path lies agony and depression, not only for you, but for everybody else.
Oh, and to be a Right Honorable Elitist Bastard Smartypants, it's a misquote. The original said: "... is probably the day..."
-- Someone smarter than Soul-Burn666
Way back when (5+ years ago) the hostname "ls" actually resolved to an A record. Then you could "ping ls". Although usually you had to write "ls." because lots of software thought it was in the local domain:-)
Sadly, ls. doesn't have an A record anymore. But there's no technical reason why another TLD could't have A records...
Slashdot Mirror
Of course, any product that has had @ in the name at any point in the last, oh, decade or so can not by any means be taken seriously.
I liked the bit about her making a point of mentioning she drank a significant amount of alcohol after the incident, and that she normally doesn't do this, but hey, I was stressed out.
For those of you who've never had to deal with things like domestic abuse, that's classical weasel talk for "I was drunk as a skunk and misbehaved as a result, but I won't admit it". It was no doubt prompted by the police smelling her breath or seeing an empty bottle, and asking uncomfortable questions as a result.
We'll never know what really happened, but I'm going with "abrasive drunk woman tears techie a new one" here. Although I can understand someone losing their cool after such a long and fruitless struggle to get their connection fixed.
Consumers buy overpriced A-brand products. A-brand companies spend part of that money on TV advertising. The TV advertising money goes to the IOC for the broadcasting rights.
Wow. That was an easy one.
A message that is sent also needs to be received. So all the network traffic is double. Once to send, once to receive. And the radio network overhead is much more than just those 160 bytes in the message.
And then you have all the infrastructure necessary to handle the messages. It's not point-to-point, it's store and forward. A network operator needs to invest quite a bit of money in the systems that handle the text messages, with all their interesting features, the billing, etc.
Of course texting is still ridiculously expensive, I'm not going to argue that. But using baseless numbers and ignoring the behind-the-scenes infrastructure to "prove" a 17000x markup on text messages is nothing short of moronic. And so is saying that texting is equivalent to paying $24000 for an MP3.
If there's an upside here, I'm not seeing it.
A project is started, a gaggle of consultants make a boatload of money, and introduce a system that is uncomfortable to use and barely meets the stated requirements. Everybody is ordered to use the system, but nobody is clearly responsible for keeping it up-to-date and nobody bothers to check on the accuracy later on.
After 6 months the system is in total disarray, but because nobody repeals the decision that it is the Official System [TM] and because it cost so much to build, it's there to stay along the other Official Systems [TM] that nobody uses. That's when the idea for the next Official System [TM] pops up.
Sounds negative? You were talking about Enterprise systems, right? This is how it works in every big company. Don't fool yourself into thinking it can change. Enterprises don't change. They slowly morph around problems to avoid them, not to solve them.
The solution? Do it locally. Figure out a convenient way to track the IP address subnet assignments in your network, and use it to keep track of your address space. Use an Excel sheet for all I care to keep track of firewall rules. Use domain-specific tools, and use them only for that domain. Avoid the temptation to create the Universal Solution To All Problems because it won't work. Down that path lies agony and depression, not only for you, but for everybody else.
No, I'm not bitter, why do you ask?
Really? Why?
Oh, and to be a Right Honorable Elitist Bastard Smartypants, it's a misquote. The original said: "... is probably the day..."
--
Someone smarter than Soul-Burn666
Way back when (5+ years ago) the hostname "ls" actually resolved to an A record. Then you could "ping ls". Although usually you had to write "ls." because lots of software thought it was in the local domain :-)
Sadly, ls. doesn't have an A record anymore. But there's no technical reason why another TLD could't have A records...