After seeing this happen at my company, I recommend jumping in with both feet or leaving the company. The schmucks have already won, and are firmly in control. If you stay, you'll do a lot better playing the game their way.
Although TFA doesn't say so explicitly, I think it's talking about the race to get the best targeted advertising analytics in place for global applications like eBay, FB etc. These applications don't have the same database requirements as traditional business apps. It makes sense to talk about new ways of doing things for them, but TFA's author and a lot of other people make the mistake of thinking or implying that these new techniques will apply directly to traditional business apps as well. Sorry, not.
----------
Happy New Year, may it suck less for ya than the last one.
Airport checkin lines say you're wrong. The majority of the people in line don't have any issues and just need to check in. But as soon as the number of people with issues == the number of airline desk clerks, the whole line is stalled, and average wait times go way up. Your single-line-queue logic requires all transaction times to be roughly the same to work, I believe.
I used to whine loudly that they needed special lines at airports for people without issues. And thanks to automated checkin kiosks and online checkin, we now have them. As a rule, the kiosks and online checkin only work for people without issues, so they effectively segregate traffic into that which is easy to process and that which is harder.
Not always. It's quite useful if your group is doing potentially destabilizing new work and you still need to keep up with bug fixes in a release branch. What's the alternative, a gazillion "#ifdef MY_NEW_FEATURE"s, twiddled makefiles, etc?
And what is a company with multiple shipping releases of the same code supposed to do? Good merge tools with good engineers using them are their only hope. When a bug is discovered in 5.0 and it needs to be fixed in 5.1, 5.2 and 6.0 three merges are necessary, no matter what SCM tool you're using.
> the point is to free up humans from doing the boring, silly tasks...
Unfortunately, there is a large population of humans who have no skills beyond what are characterized here as boring, silly tasks, nor much inclination to step up and learn how to be more productive. And regardless of whether they deserve to be employed or not, making them unemployed doesn't help the the population as a whole.
So my applause goes more often to technology that helps people work smarter, not as often to that which outright replaces them.
Yeah. I paid $400 for my iPhone. Mostly I use it as a phone, a news reader and a GPS. I want it to "just work".
Going on half the time, it doesn't.
Whether this is ATT's fault or Apple's I don't know, but it sure does seem like Steve has a good bit more of that great integration work of his left to do, I mean, I get the value to Apple of preemptive dissing on the competition, but I'd still like to hear what Apple's plan is to make my iPhone "just work."
Medical people tend to understand statistics, to reuse an old saw, the way a drunk understands a lightpole--using it more for support than illumination.
As most/all/.ers know, for a statistical inference to be valid, the underlying dataset must be completely random. Not just sort of random, not just I'm pretty sure it's random, not just that's the best I could do random, not just they-said-it-was random. It must be completely random. Most of the time included random variables must also be completely independent (unless you're doing covariance studies, but let's not go there).
Thing is, complete randomness and independence of variables within a human dataset is probably impossible, even in the big ones sponsored by NIH, the Census Bureau and so on.
If that is so, then doing "statistical studies" on human datasets--which AFAIK is what the majority of medical studies attempt to do--is about as scientific as creationism.
First one wonders why there would have to be only one of these things? And then, oh right, the geosynchronous orbit is filling up. And then, what happens when this "collector of electrons" touches another satellite? Bzzzzzt?
The article did say that they had barely considered any of the engineering ramifications. You gotta love science. "One gets such wholesale return of conjecture out of a trifling investment of fact." -- Mark Twain.
Locating near any power plant, whether it be coal or hydro, will get you huge discounts in power costs, because the utility doesn't have to support a grid to get it to you, and your demand load is pretty predictable.
Any northern climate will do better in terms of natural air cooling, but Buffalo is a poor choice on that front, because all the weather sweeping in over the Great Lakes makes the air quite humid. You want dry cold air for maximum cooling effectiveness.
Like most legal departments of successful large corporations, the legal department of Microsoft does what is in its own interests more reliably than it does what is in the best interests of its corporate master. When there is money to be made from trolling, it will troll unless swatted down by the corporate overlords. Who are often too busy to notice, because they're making about 1,000 times as much money selling products as their legal department ever could make from trolling. We're talking Microsoft here: a product (legal trolling) that doesn't gross a billion a year is almost beneath notice.
I wonder what the storage system is? Just disks in the servers?
Anytime folks putting together a system fail to mention the storage end of the solution, you can be pretty sure that that much, at least, is done badly.
The article states "the beta gave the general public their first taste of an operating system that would go on to win popular acclaim and attract scores of Windows users to the Macintosh." One score being 20, I guess that means maybe a couple hundred Windows users switched over?
I found it odd too, though they seem to be reviewing boxes that do dedup on live data, as opposed to backup streams. Appliances like the NS-series claim dedup percentages of 95%+, but they accomplish this seeming miracle when slowly changing datasets are backed up over and over (even differential backup systems usually do a full backup fairly regularly).
Slashdot Mirror
After seeing this happen at my company, I recommend jumping in with both feet or leaving the company. The schmucks have already won, and are firmly in control. If you stay, you'll do a lot better playing the game their way.
I finally got rid of my Grandpa's wire recorder the last time I moved.
I'd like to see some experience from someone small who's tried to support OOXML as standardized by ISO. All this polemic is just that.
The sad thing is that this flow of crap has easily identified causes, but no easily identified remedies.
--------
Happy New Year and Good Riddance Old Year
Although TFA doesn't say so explicitly, I think it's talking about the race to get the best targeted advertising analytics in place for global applications like eBay, FB etc. These applications don't have the same database requirements as traditional business apps. It makes sense to talk about new ways of doing things for them, but TFA's author and a lot of other people make the mistake of thinking or implying that these new techniques will apply directly to traditional business apps as well. Sorry, not.
----------
Happy New Year, may it suck less for ya than the last one.
Or worse, they are elderly, and paying cash, and see value in giving exact change.
Airport checkin lines say you're wrong. The majority of the people in line don't have any issues and just need to check in. But as soon as the number of people with issues == the number of airline desk clerks, the whole line is stalled, and average wait times go way up. Your single-line-queue logic requires all transaction times to be roughly the same to work, I believe.
I used to whine loudly that they needed special lines at airports for people without issues. And thanks to automated checkin kiosks and online checkin, we now have them. As a rule, the kiosks and online checkin only work for people without issues, so they effectively segregate traffic into that which is easy to process and that which is harder.
Not always. It's quite useful if your group is doing potentially destabilizing new work and you still need to keep up with bug fixes in a release branch. What's the alternative, a gazillion "#ifdef MY_NEW_FEATURE"s, twiddled makefiles, etc?
And what is a company with multiple shipping releases of the same code supposed to do? Good merge tools with good engineers using them are their only hope. When a bug is discovered in 5.0 and it needs to be fixed in 5.1, 5.2 and 6.0 three merges are necessary, no matter what SCM tool you're using.
I can see it coming....
http://assbook.spruz.com/
> the point is to free up humans from doing the boring, silly tasks...
Unfortunately, there is a large population of humans who have no skills beyond what are characterized here as boring, silly tasks, nor much inclination to step up and learn how to be more productive. And regardless of whether they deserve to be employed or not, making them unemployed doesn't help the the population as a whole.
So my applause goes more often to technology that helps people work smarter, not as often to that which outright replaces them.
Presumably it's for use mostly in other countries. Which means they'd better have 220v converters, or switching power supplies.
Yeah. I paid $400 for my iPhone. Mostly I use it as a phone, a news reader and a GPS. I want it to "just work".
Going on half the time, it doesn't.
Whether this is ATT's fault or Apple's I don't know, but it sure does seem like Steve has a good bit more of that great integration work of his left to do, I mean, I get the value to Apple of preemptive dissing on the competition, but I'd still like to hear what Apple's plan is to make my iPhone "just work."
Medical people tend to understand statistics, to reuse an old saw, the way a drunk understands a lightpole--using it more for support than illumination.
/.ers know, for a statistical inference to be valid, the underlying dataset must be completely random. Not just sort of random, not just I'm pretty sure it's random, not just that's the best I could do random, not just they-said-it-was random. It must be completely random. Most of the time included random variables must also be completely independent (unless you're doing covariance studies, but let's not go there).
As most/all
Thing is, complete randomness and independence of variables within a human dataset is probably impossible, even in the big ones sponsored by NIH, the Census Bureau and so on. If that is so, then doing "statistical studies" on human datasets--which AFAIK is what the majority of medical studies attempt to do--is about as scientific as creationism.
Vaccinations are voluntary, at least in the free world. They don't shut the door to the hospital if you haven't had one.
[Please don't start about health insurance now, that's not mentioned in the article.]
First one wonders why there would have to be only one of these things? And then, oh right, the geosynchronous orbit is filling up. And then, what happens when this "collector of electrons" touches another satellite? Bzzzzzt?
The article did say that they had barely considered any of the engineering ramifications. You gotta love science. "One gets such wholesale return of conjecture out of a trifling investment of fact." -- Mark Twain.
> What would be nice is if the GUI could automatically create a shell script doing the change.
It IS nice: AIX has been doing this for 2 decades in "SMIT".
And BTW, GUIs that allow changing settings on multiple boxes at once have been around for a long time too--SMOP.
00-ca-fe-ba-be-00 is in Moscow, on the other hand. What does that say about Java?
Locating near any power plant, whether it be coal or hydro, will get you huge discounts in power costs, because the utility doesn't have to support a grid to get it to you, and your demand load is pretty predictable.
Any northern climate will do better in terms of natural air cooling, but Buffalo is a poor choice on that front, because all the weather sweeping in over the Great Lakes makes the air quite humid. You want dry cold air for maximum cooling effectiveness.
Like most legal departments of successful large corporations, the legal department of Microsoft does what is in its own interests more reliably than it does what is in the best interests of its corporate master. When there is money to be made from trolling, it will troll unless swatted down by the corporate overlords. Who are often too busy to notice, because they're making about 1,000 times as much money selling products as their legal department ever could make from trolling. We're talking Microsoft here: a product (legal trolling) that doesn't gross a billion a year is almost beneath notice.
When Xerxes tells you to come up with a star map, you do it. If you're clever, you come up with one that's pleasing to him, but only you can read.
Great tip. Thanks!
Where are all the posts, after parent, reminding us that the USB memory stick trick doesn't work on Linux? (or Apple)?
/.ers generally have more substantive things to say.
* Regarding title: real
I wonder what the storage system is? Just disks in the servers?
Anytime folks putting together a system fail to mention the storage end of the solution, you can be pretty sure that that much, at least, is done badly.
The article states "the beta gave the general public their first taste of an operating system that would go on to win popular acclaim and attract scores of Windows users to the Macintosh." One score being 20, I guess that means maybe a couple hundred Windows users switched over?
I found it odd too, though they seem to be reviewing boxes that do dedup on live data, as opposed to backup streams. Appliances like the NS-series claim dedup percentages of 95%+, but they accomplish this seeming miracle when slowly changing datasets are backed up over and over (even differential backup systems usually do a full backup fairly regularly).