I liked The Demolished Man better myself, but it's a slower story - The Stars, My Destination has a lot more action in it, and of course the main character is the hero, not the villian...
But in truth, I'd just have a well-stocked bookshelf, and let children figure it out for themselves.
The queueing theory I've studied shows that the congestive threshold varies with queue length and interface speed. Low-speed ( 2Mbps) links are very vulnerable to serialization effects, and begin to exhibit congestive behaviors at around 50% usage (depending on the accuracy of measurement). As the interface gets larger, serialization delay becomes less relevant, and the congestive effects start to change.
Certain techniques are better than others at dealing with specific types of traffic flows - for instance, WRED is worthless for UDP, but invaluable for TCP. The Bell CA engineers might be faced with a user population which is changing their patterns faster than they can deal with it.
I am a network engineer. 90% is a really high threshold for calling something congested. Also, 15 minute averages are better than a lot of measurements I've seen, but are far from perfect - lots of "microburst" type activity can cause a noticeable loss in performance over a much shorter period than that.
Bittorrent-type flow patterns do tend to cause microburst issues - it might be that Bell CA needs to implement some more fine-grained measurements to see whether the thresholds are still the right ones for them.
I used to think that I could translate most dialects of bullshit into english but this threw me off guard. The most reasonable explanation is that Chris Anderson is a tool and doesn't know what he is talking about.
You're overgeneralizing: the idea that from a bad thing can come some suprisingly positive benefits is hardly a fallacy, and isn't the broken window fallacy at all.
Broken window fallacy: "wanton destruction creates jobs / is good for the economy"
Correct statement: "wanton destruction causes a wealth transfer"
In this case, the rising cost of shipping goods from place to place incentivizes industry to do less of that. That has some side benefits for some US workers (although it has some downsides for some other US industries). People who make steel benefit, but people who make cars from that steel suffer from rising ingredient prices.
This isn't a broken window fallacy: it's simply a change in the cost of doing certain types of business. There isn't an incentive to bring, for instance, tech support from Bangalore to Pittsburgh.
Bell labs in its heyday was a couple thousand people. Ma Bell as a whole was nearly a million. I somehow think that most people's idea of what "work for the phone company" means is more like the guy who installs phones or the one who runs a switchboard...
Besides, alongside the Bell Labs reputation for brilliance was their reputation as the alpha geeks of their day...
The insurance companies maintain profitability by selecting price points that set them ahead, denying claims whenever they can get away with it, squeezing patients and doctors, and raising premiums at rates which vastly exceed inflation.
Then again, if most folks look at computers as an appliance, who wants to be an appliance repairman? Seriously - how many folks wanted to work for the phone company in the 60s and 70s?
DARPA has folks around the country in various offices, much as the other Federal agencies do. However, more significantly, DC is hardly a dump - it's got good parts and bad parts, but I'd put it up against any other comparably-sized city (~500K) and I think it would do well in the comparison.
To be fair, "reinventing government" which basically translates to "hire contractors to do what government employees used to do" was a significant policy program of then Vice-President Al Gore. This approach has certainly continued under the current administration, and it may be causing a problem in this area, but it isn't just a Republican problem.
Was that 93 seconds to a meaningful breach, or to get some information which could be brute-forced offline?
One of the security audits I watched a couple of years ago was a thing of beauty: my coworker took the laptop he was assigned, booted it from a linux CD, and proceeded to brute-force the administrator password, and from there set up an arp-poisoning M-it-M attack such that after about two days he completely owned the network. Brute-forcing the laptop did take better than a day, but that really isn't all that long...
My response to watching this? "remind me not to piss you off..."
Multicast is great if you have several receivers who want to receive the exact same source, but is quite limited in other contexts. Also, there are a bunch of screwball phomena which occur when translating IP multicast into link-layer multicasts (like, Cisco switches don't forward multicast between each other unless you disable igmp snooping, which turns it all into broadcast, and takes away any possible benefit from it being multicast...)
I liked The Demolished Man better myself, but it's a slower story - The Stars, My Destination has a lot more action in it, and of course the main character is the hero, not the villian...
But in truth, I'd just have a well-stocked bookshelf, and let children figure it out for themselves.
High explosives can be pretty convincing.
This basically shows that all security, at some point, boils down to heavily armed people.
The queueing theory I've studied shows that the congestive threshold varies with queue length and interface speed. Low-speed ( 2Mbps) links are very vulnerable to serialization effects, and begin to exhibit congestive behaviors at around 50% usage (depending on the accuracy of measurement). As the interface gets larger, serialization delay becomes less relevant, and the congestive effects start to change.
Certain techniques are better than others at dealing with specific types of traffic flows - for instance, WRED is worthless for UDP, but invaluable for TCP. The Bell CA engineers might be faced with a user population which is changing their patterns faster than they can deal with it.
I am a network engineer. 90% is a really high threshold for calling something congested. Also, 15 minute averages are better than a lot of measurements I've seen, but are far from perfect - lots of "microburst" type activity can cause a noticeable loss in performance over a much shorter period than that.
Bittorrent-type flow patterns do tend to cause microburst issues - it might be that Bell CA needs to implement some more fine-grained measurements to see whether the thresholds are still the right ones for them.
I've always thought that "Microsoft Works" was an amusing name for a product.
you, sir, are the wind beneath my wings.
You're overgeneralizing: the idea that from a bad thing can come some suprisingly positive benefits is hardly a fallacy, and isn't the broken window fallacy at all.
Broken window fallacy: "wanton destruction creates jobs / is good for the economy"
Correct statement: "wanton destruction causes a wealth transfer"
In this case, the rising cost of shipping goods from place to place incentivizes industry to do less of that. That has some side benefits for some US workers (although it has some downsides for some other US industries). People who make steel benefit, but people who make cars from that steel suffer from rising ingredient prices.
This isn't a broken window fallacy: it's simply a change in the cost of doing certain types of business. There isn't an incentive to bring, for instance, tech support from Bangalore to Pittsburgh.
It takes a certain kind of patience to put up with the boredom... almost like waiting for a windows reboot...
Bell labs in its heyday was a couple thousand people. Ma Bell as a whole was nearly a million. I somehow think that most people's idea of what "work for the phone company" means is more like the guy who installs phones or the one who runs a switchboard...
Besides, alongside the Bell Labs reputation for brilliance was their reputation as the alpha geeks of their day...
The insurance companies maintain profitability by selecting price points that set them ahead, denying claims whenever they can get away with it, squeezing patients and doctors, and raising premiums at rates which vastly exceed inflation.
There, fixed that for you.
Then again, if most folks look at computers as an appliance, who wants to be an appliance repairman? Seriously - how many folks wanted to work for the phone company in the 60s and 70s?
Okay, but do species multitask?
well said.
I wish more people would make their decision about voting like you are - it's enough to disagree without demonizing the opposition.
Thank you.
awesome.
Personally, I've noticed that my sinuses are worse when congress is in session: I must be allergic to their hot air...
DARPA has folks around the country in various offices, much as the other Federal agencies do. However, more significantly, DC is hardly a dump - it's got good parts and bad parts, but I'd put it up against any other comparably-sized city (~500K) and I think it would do well in the comparison.
The weather does suck though.
To be fair, "reinventing government" which basically translates to "hire contractors to do what government employees used to do" was a significant policy program of then Vice-President Al Gore. This approach has certainly continued under the current administration, and it may be causing a problem in this area, but it isn't just a Republican problem.
Maybe not as dumb as you say - that's a really cogent analysis of the OPs approach.
I tend to be relatively pro-military, but I understand that a lot of very sharp people disagree with me.
Was that 93 seconds to a meaningful breach, or to get some information which could be brute-forced offline?
One of the security audits I watched a couple of years ago was a thing of beauty: my coworker took the laptop he was assigned, booted it from a linux CD, and proceeded to brute-force the administrator password, and from there set up an arp-poisoning M-it-M attack such that after about two days he completely owned the network. Brute-forcing the laptop did take better than a day, but that really isn't all that long...
My response to watching this? "remind me not to piss you off..."
Multicast is great if you have several receivers who want to receive the exact same source, but is quite limited in other contexts. Also, there are a bunch of screwball phomena which occur when translating IP multicast into link-layer multicasts (like, Cisco switches don't forward multicast between each other unless you disable igmp snooping, which turns it all into broadcast, and takes away any possible benefit from it being multicast...)
This reminds me of Niven & Pournelle's Mote in God's Eye, where the moties did actually use a coffee maker as a means of infiltration...
It's a planet devoted to fighting crime, and supporting truth, justice, and the American way.
I keep a small public wireless network running in my spare time, and we all agreed that fully open access was the best way to limit our liability.
I think the category of "busybody puritan" can apply to both liberals and conservatives. It's just that what they consider sinful is different.