... is actually quite simple: You keep your hands off the systems. Period.
In detail, you plan, install and _test_ your setup before it enters production. You make sure that you can survive whatever you throw at it wrt. errors and incidents. You then figure out how much downtime you are allowed to have according to SLA. You then divide this number into equal sized maintaince windows together with the customer. And then you adhere to these windows! No manager should ever be allowed to demand downtime out of band. Period. In between you basically minimize your involvement with the systems and plan your activities for the next scheduled closing window.
And you ofcourse only deploy stable, true and tested versions of software and operating systems. And even though your OS supports online capacity expansion on the fly, you really shouldn't use the capability unless you absolutely have to. Instead you plan ahead in your capacity management procedure and add capacity in the closing windows. And you do not test and rehearse failures! It only introduces risks... besides that you have already tested and documented them. And as you haven't changed the configuration, there is no need to test again.
So in essence. Common sense will easily yield 99.9%. Carefull planning and execution will yield 99.99%. The really hard part is 99.999%.../zensonic
This problem was a device burried at the oceanic floorbed that took 2+ years to recover. The 'i am here' distress signal consists of 30 days worth of 'pings' that in itself requires a probe far down to be able to hear the pings.
But you are right, if it is bolted to the airframe, then a big flotation device is required.
It is no secret that IBMs legal department and their patent portfolio is what always gives IBM the upper hand. I'm sure that they managed to get alien cpu technology in an settlement for alien infringement on one or more of IBMs many patents.
Given that Peter Sestoft was Beta tester on C# 2.0 you can take it for granted that the book covers C# 2.0 as it was at the time of release. If you find anything that is inaccurate in the book I am sure the author would appriciate the feedback:-)
Instead of teaching a subject by a massive 778 pages of text, you should go for the consise description of C# as described in Peter Sestoft and Henrik Hansens book:
With 182 pages it is quickly read, yet you can also easily iterate over the text again and again as deeper and deeper understanding of C# is needed. A real gem on any developers bookshelf!
Coding together realtime in the same environment will not solve anything.
Errors introduced by bad programmers are more easily solved by replacing them than by working together with them realtime
If you do not have the time to do peer reviews of fellow co-workers code non-realtime, what makes you think you have the time when you are programming?
Having more than one person "working" (only one can work, otherwise it end up being a mess of different oppinions on how to write the particular piece of code) on the same piece of code is actually less efficient than having only one person writing it in the first place.
Programming is actually quite a lot like amdahls law: you need time to break the task down into independt task that can be parallized. That is called modular design and is an old topic. A fancy editor is not magically going to speed up development.
Except that the PS3 consumes anywhere from 120W to 300W depending on version and usage. The wii will stay below 20W at all times. If you can live with the non-HD output of the wii it will make a fine mediacenter, IMHO.
1. Aliens never have landed here in the first place 2. The DoD not being able to figure out how to work that mini-fusion reactor 3. Aliens being so advanced that they use cats and bread for their propulsion systems... 4. DoD being really naive, thinking someone, out there, have the information to do 5x better than current tech and not having patented it..... and willing to sell it for a mere $1000000?
True. But that is most likely a production volume issue. AMD can not afford to turn out new FABs at the same rate as Intel can. Sad but true. They can only win this game by thinking smarter not harder!
But its hard to beat the price of $100 if you can't scale. It really does make sense to produce these units at a centralized place, ie at quanta facilities, probably the worlds largest and most effecient laptop manufacturer.
Its not the best tech products of all times at the title states, its the most influential products of all time.
And even with that in mind I think the list is bogus. With criterias like:
So what's the best tech product to come out of the digital age? And what qualifies a product as being "best"? First and foremost, it must be a quality product. In many cases, that means a piece of hardware or software that has truly changed our lives and that we can't live without (or couldn't at the time it debuted). Beyond that, a product should have attained a certain level of popularity, had staying power, and perhaps made some sort of breakthrough, influencing the development of later products of its ilk. you have to wonder where mp3 (software and hardware), television (hardware), tcp/ip (software) and cellphones (hardware) are. But then again. I may have misunderstood what this is all about.
We have. If you read whats being said about power6 it hasn't got a deeper pipeline. So nobody knows how they do it...... If they actually are able to keep the promises, but thats another story.
they blow it on production, leaving Intel to fill the void they created
It's a bit harsh to say that they blow it on production. You do realize how much it costs to construct cleanrooms, right? All while still being profitable and pour lots of money into R&D.
I think they are playing their cards to the best of their abilities.
And besides the monetary issue of sending people out into space theres the problem with humans not really being built for traveling through space. To put it simply humans will not survive prolonged space trips due to radiation, lack of gravity, being squeezed into a small compartment for years and so forth.
In my oppinion interstellar travel for humans lives or dies foremost with the success of theoretic physics finding an effecient way of getting from A to B in space.
I just hope that the next generation of battery technolgy is inherently less likely to explode.
Not going to happend. The majority of a battery is chemical substance that will release its stored energy if asked to do so. The only thing preventing these chemicals from releasing energy too fast is the onboard control logic in the battery and on the mainboard.
Throw in companies that tries to save a dime for each produced unit and are willing to sacrifice security for money and you get a deadly mix of ingrediences.
As for the future. Well, the user driven demand is for faster and faster notebooks and reduced costs..... No matter what chemical substance is used for batteries.
* the hardware? Not able to make the hardware? * the drivers? Not able to utilize the hardware? * bad management? Not able to do a project like this? * bad implementation? Good ideas on paper, unusable in real life? * All of the above.
Could someone with a lot more understanding of how highend graphic hardware than me give an explanation? As long as I can remember S3 has tried to compete but have failed.
I cannot figure the reason behind waiting a year before getting a digital whiteboard. Anybody got any good explantions? Surely it can't be a question about money.
What consequences? Having the kernel be way better than it would have been if Linus had listened to you people and not used BitKeeper?
Sure, BitKeeper might be going away--but the things Linus accomplished while it was here will NOT go way.
This is the big difference between a religious attitude towards OSS and a laid back engineering style attitude.
Use the best tool for the job and do not let religion get in the way of that decision! Sure the kernel developers has to find another tool now, but as the parent said: it was good while it lasted.
Slashdot Mirror
... is actually quite simple: You keep your hands off the systems. Period.
In detail, you plan, install and _test_ your setup before it enters production. You make sure that you can survive whatever you throw at it wrt. errors and incidents. You then figure out how much downtime you are allowed to have according to SLA. You then divide this number into equal sized maintaince windows together with the customer. And then you adhere to these windows! No manager should ever be allowed to demand downtime out of band. Period. In between you basically minimize your involvement with the systems and plan your activities for the next scheduled closing window.
And you ofcourse only deploy stable, true and tested versions of software and operating systems. And even though your OS supports online capacity expansion on the fly, you really shouldn't use the capability unless you absolutely have to. Instead you plan ahead in your capacity management procedure and add capacity in the closing windows. And you do not test and rehearse failures! It only introduces risks ... besides that you have already tested and documented them. And as you haven't changed the configuration, there is no need to test again.
So in essence. Common sense will easily yield 99.9%. Carefull planning and execution will yield 99.99%. The really hard part is 99.999%... /zensonic
Once we have eternal life as computers do we even bother reproducing anymore?
I am curious. How do you plan to reproduce as a computer? Brings a totally new meaning to the word forking i suppose.
Trying to solve one problem at the time ;-)
This problem was a device burried at the oceanic floorbed that took 2+ years to recover. The 'i am here' distress signal consists of 30 days worth of 'pings' that in itself requires a probe far down to be able to hear the pings.
But you are right, if it is bolted to the airframe, then a big flotation device is required.
What about making the container so that it is able to float? Should be a matter of making the container airtight and creating enough uplift.
http://en.wikipedia.org/wiki/Interstellar_travel
http://en.wikipedia.org/wiki/Faster_than_light
It is no secret that IBMs legal department and their patent portfolio is what always gives IBM the upper hand. I'm sure that they managed to get alien cpu technology in an settlement for alien infringement on one or more of IBMs many patents.
Given that Peter Sestoft was Beta tester on C# 2.0 you can take it for granted that the book covers C# 2.0 as it was at the time of release. If you find anything that is inaccurate in the book I am sure the author would appriciate the feedback :-)
Instead of teaching a subject by a massive 778 pages of text, you should go for the consise description of C# as described in Peter Sestoft and Henrik Hansens book:
http://www.amazon.com/C-Precisely-Peter-Sestoft/dp/0262693178
With 182 pages it is quickly read, yet you can also easily iterate over the text again and again as deeper and deeper understanding of C# is needed. A real gem on any developers bookshelf!
Programming is actually quite a lot like amdahls law: you need time to break the task down into independt task that can be parallized. That is called modular design and is an old topic. A fancy editor is not magically going to speed up development.
Except that the PS3 consumes anywhere from 120W to 300W depending on version and usage. The wii will stay below 20W at all times. If you can live with the non-HD output of the wii it will make a fine mediacenter, IMHO.
So is this proof of
... ..... and willing to sell it for a mere $1000000?
1. Aliens never have landed here in the first place
2. The DoD not being able to figure out how to work that mini-fusion reactor
3. Aliens being so advanced that they use cats and bread for their propulsion systems
4. DoD being really naive, thinking someone, out there, have the information to do 5x better than current tech and not having patented it
Hmm.
True. But that is most likely a production volume issue. AMD can not afford to turn out new FABs at the same rate as Intel can. Sad but true. They can only win this game by thinking smarter not harder!
But its hard to beat the price of $100 if you can't scale. It really does make sense to produce these units at a centralized place, ie at quanta facilities, probably the worlds largest and most effecient laptop manufacturer.
And even with that in mind I think the list is bogus. With criterias like: So what's the best tech product to come out of the digital age? And what qualifies a product as being "best"? First and foremost, it must be a quality product. In many cases, that means a piece of hardware or software that has truly changed our lives and that we can't live without (or couldn't at the time it debuted). Beyond that, a product should have attained a certain level of popularity, had staying power, and perhaps made some sort of breakthrough, influencing the development of later products of its ilk. you have to wonder where mp3 (software and hardware), television (hardware), tcp/ip (software) and cellphones (hardware) are. But then again. I may have misunderstood what this is all about.
We have. If you read whats being said about power6 it hasn't got a deeper pipeline. So nobody knows how they do it. ..... If they actually are able to keep the promises, but thats another story.
they blow it on production, leaving Intel to fill the void they created
It's a bit harsh to say that they blow it on production. You do realize how much it costs to construct cleanrooms, right? All while still being profitable and pour lots of money into R&D.
I think they are playing their cards to the best of their abilities.
And besides the monetary issue of sending people out into space theres the problem with humans not really being built for traveling through space. To put it simply humans will not survive prolonged space trips due to radiation, lack of gravity, being squeezed into a small compartment for years and so forth.
In my oppinion interstellar travel for humans lives or dies foremost with the success of theoretic physics finding an effecient way of getting from A to B in space.
Not going to happend. The majority of a battery is chemical substance that will release its stored energy if asked to do so. The only thing preventing these chemicals from releasing energy too fast is the onboard control logic in the battery and on the mainboard.
Throw in companies that tries to save a dime for each produced unit and are willing to sacrifice security for money and you get a deadly mix of ingrediences.
As for the future. Well, the user driven demand is for faster and faster notebooks and reduced costs..... No matter what chemical substance is used for batteries.
Hey takker!
Thomas
"I sense a great disturbance in the Force, as if millions of toasters cried out in terror and were suddenly silenced..."
... Hurd lives!
Is it
* the hardware? Not able to make the hardware?
* the drivers? Not able to utilize the hardware?
* bad management? Not able to do a project like this?
* bad implementation? Good ideas on paper, unusable in real life?
* All of the above.
Could someone with a lot more understanding of how highend graphic hardware than me give an explanation? As long as I can remember S3 has tried to compete but have failed.
I cannot figure the reason behind waiting a year before getting a digital whiteboard. Anybody got any good explantions? Surely it can't be a question about money.
Thomas
MSR has some good ppl working an cambridge on computer language research and type systems!
.net are not stupid ideas you know!
C# and
But do not take my word for it, go see for yourself: http://research.microsoft.com/ppt/
This is the big difference between a religious attitude towards OSS and a laid back engineering style attitude.
Use the best tool for the job and do not let religion get in the way of that decision! Sure the kernel developers has to find another tool now, but as the parent said: it was good while it lasted.