It depends on the *environment*. In a certain environment, individual prowess beats out team effort. Try having a baby in 1 month w/a team.
Parallel/group processes can get more done overall, but they cannot achieve the same heights or Einstein like brilliance that can drive game-changing results.
Actually, most of the brilliant people like Einstein did have a team with them. It may not have been a formal arraingment, though...
The very fact that we are multicellular organisms with specialized body tissues supports this. For if evolution favored selfishness most of all, primordial life would not have banded together.
Working together with others, as a team, is a skill that must be learned. Those that never learned, and don't want to learn, are more successful as individuals. But those who work together can beat them.
Thats why criminals end up losing. But a criminal who can take control of the team can cause great damage, so be careful who you follow...
In EVE you're the captain, not the helmsman. If you're looking to wiggle your joystick, I'd recommend the Freespace series.
Or try the EgoSoft X-Universe series, current version "X3, Albion Prelude". (also on steam) Single Player Only, so there are not many griefers. (Still a few, though. 8-) ) Flight simulation where you are always flying a ship, but with data displays of other places and things. Can also give commands to your other ships and stations, to run on their own. But the NPCs are independent operators and can produce "Emergent Behavior", so it can get surprising sometimes. The control interface is still a "bear", but it works well once you get used to it. Own more than one ship. Lots of them. Own more than one station. Lots of them. Do what ever you feel like, or follow a "quest". Write your own command programs for ships and stations. Good to play for years. The "multi-player" interaction is still there, on the game forum at EgoSoft.
"Never point a gun (doesn't matter if it is loaded or not) at or near a person"
Isn't that a bit like teaching someone they should never drive their car on or near a public road?
No, it's more like never drive your car at a person. As I was taught not to. At that time it was considered funny, by some, to swerve your car at a person as a joke. A few accidents and it became less funny...
High schools used to teach safe gun handling and marksmanship, a long time ago. When the education establishment was first demonising gun ownership, some administrators were embarrised to find old shooting ranges in the school basements. The current accident rate is at least partly due to the educational system's failure to teach children.
... In some places it can also expose you to stigma. Imagine not getting a job (and not being told why) because you're on one of these lists.
Imagine not getting a job becasuse someone lied and put you on that list, because they had a grudge against you about something else! I don't see any way to check for that, so the list would get more and more garbage.
I think it would depend on the magnet material. Remember that dynamic situations can be a lot different from the static situations that they teach in school. Speeding into the shield field lines might just re-magnitize the magnet. It also depends on speed and the mass of the magnet, it might hit the ship before being turned much.
The OP is about a shaped magetic field with plasma particles suspended in it. Remember that the intruding particles are moving at a high rate of speed, and that changes what is going to happen to them when their path intersects the field lines of the magnetic field.
The math is similar to what is used to describe the operation of an electric motor or generator, the field lines are distorted by the movement and the moving conductors have a current induced in them. That induced current produces a magnetic field that opposes the original field and exerts force.
Actually not. The passage through the shield induces flux into conductive particles, that reacts with the shield flux and turns them aside. Also, the field flux in the shield is curved, not straight. So they would not point to the pole, anyway, even if they were not moving fast.
Small towns have good restaurants, it's just that everyone knows where they are except you! They don't bother with big signs because everyone grew up there and knows where everything is. But small towns don't have as many good places as a big city. On the other hand, everyone has guns and you can walk down a dark street without getting robbed. Some places they don't even bother to lock their car doors!
They don't even need to be magnetized. They only need to magnetizable. Or, for that matter, just conductive. Magnetic induction would supply the secondary field.
... But fact remains: the "ether" idea is now proven as childish.
Don't kid yourself, the terms are no better known than they were then. The "Luminiferous Aether" was basically a description of the "Space-Time Continuum", except with fewer than 12 dimensions.The terms were not wrong, they just were struggling to describe the concepts. But our math is more complete now...
... Most literature no older than 100 years looks now dated and plain boring (yes, even golden classics). Music from 2 decades ago is mostly stuff that nobody listens anymore (Yes, i know there are exceptions, but few and far between)...
The reason that young people claim not to like old stuff, is not that it is bad. It is that they are scared of the opinion of their peers. They are terrified that they might not be "first and newest", so they cut down the older things. They usually grow out of it eventually...
All of this is probably just a description of instrument loading effects, The answer is easy, just find instruments that are smaller than the sub-atomic particles ! 8-)
Get a good global search utility. Search for every use of the symbol names that you are working with, to see what their scope is and how they are used. You can see how the other code uses them, steal snippets of working code you need, and tell what might "break" your use of them. If you have seen every use of a symbol, in the whole code set, then you can feel more confident that what you are doing will not break things.
Don't try to learn everything at once, your brain can't hold it all right away. Study about the modules and symbols that you must work on. Start with finding out how much you actually -do- have to work on. Then widen your scope as you find more "connections" to other things.
Everything is more complicated than you think, and more complicated than your boss thinks. Be cautious, go carefully, and don't go "running full speed off a cliff". This will actually end up being much faster to a working version.
Frustration is normal, when learning something new. It does not necessarily indicate that the thing you are studying is screwed up (although it might be). Work through the frustration before making changes. (Except, it might be good to make temporary "test" changes to help in the learning.) It is painful, but you will learn and grow from it.
Strongly resist the temptation to re-write stuff that is new to you, no matter how bad it looks. There will usually be good reasons that it is that way, and you will make a disaster. Make good backups of everything before each change and at least every day. There will be places where you must throw away what you have done and go back.
On the other hand, don't be afraid to make global changes to the code set if it is really needed. Just back up a working copy that you can go back to, and be careful.
Do things in phases, even if the "customer" only wants a final version. Make a reasonable set of changes than get it working and debugged. Then do it again for the next changes. Debugging as you go is actually much faster in the long run. Learn to use a Debugger, it is like turning on a light in a dark room.
Find quiet time for several hours to work on it, so that you can get into a "state of flow" mentally. This is much more effective than normal work with interruptions.
Give a government (or other powerful organization) the power to protect something, and you are also giving it the power to destroy that thing. It has happened before...
Slashdot Mirror
you are oversimplifying.
It depends on the *environment*. In a certain environment, individual prowess beats out team effort. Try having a baby in 1 month w/a team.
Parallel/group processes can get more done overall, but they cannot achieve the same heights or Einstein like brilliance that can drive game-changing results.
Actually, most of the brilliant people like Einstein did have a team with them. It may not have been a formal arraingment, though...
... these nimby types are either being funded by morons, or by those with a vested interest in fossil fuels.
How about both, "in bed" together ?
Quite a combination, the greens and the polluters...
The very fact that we are multicellular organisms with specialized body tissues supports this. For if evolution favored selfishness most of all, primordial life would not have banded together.
Good point, but I have no mod points today...
Working together with others, as a team, is a skill that must be learned.
Those that never learned, and don't want to learn, are more successful as individuals.
But those who work together can beat them.
Thats why criminals end up losing.
But a criminal who can take control of the team can cause great damage, so be careful who you follow...
Ask "either - or" ?
What was the usual answer to a multiple choice question when you were in school?
"D: All of the above."
In EVE you're the captain, not the helmsman. If you're looking to wiggle your joystick, I'd recommend the Freespace series.
Or try the EgoSoft X-Universe series, current version "X3, Albion Prelude". (also on steam)
Single Player Only, so there are not many griefers. (Still a few, though. 8-) )
Flight simulation where you are always flying a ship, but with data displays of other places and things.
Can also give commands to your other ships and stations, to run on their own.
But the NPCs are independent operators and can produce "Emergent Behavior", so it can get surprising sometimes.
The control interface is still a "bear", but it works well once you get used to it.
Own more than one ship. Lots of them.
Own more than one station. Lots of them.
Do what ever you feel like, or follow a "quest".
Write your own command programs for ships and stations.
Good to play for years. The "multi-player" interaction is still there, on the game forum at EgoSoft.
RF... the next type of pollution to demonstrate against! 8-)
"Never point a gun (doesn't matter if it is loaded or not) at or near a person"
Isn't that a bit like teaching someone they should never drive their car on or near a public road?
No, it's more like never drive your car at a person. As I was taught not to.
At that time it was considered funny, by some, to swerve your car at a person as a joke. A few accidents and it became less funny...
If the murder rate did not -Greatly Increase-, as was predicted, then the assertion is disproved.
High schools used to teach safe gun handling and marksmanship, a long time ago. When the education establishment was first demonising gun ownership, some administrators were embarrised to find old shooting ranges in the school basements.
The current accident rate is at least partly due to the educational system's failure to teach children.
... In some places it can also expose you to stigma. Imagine not getting a job (and not being told why) because you're on one of these lists.
Imagine not getting a job becasuse someone lied and put you on that list, because they had a grudge against you about something else!
I don't see any way to check for that, so the list would get more and more garbage.
Nothing more fearful then the worry of having grues attack you as you go into a dark server room.
Me too, ever since I got lost in that collossal cave. But don't you have a light on your keychain? Doesn't everyone?
I think it would depend on the magnet material. Remember that dynamic situations can be a lot different from the static situations that they teach in school. Speeding into the shield field lines might just re-magnitize the magnet. It also depends on speed and the mass of the magnet, it might hit the ship before being turned much.
The OP is about a shaped magetic field with plasma particles suspended in it. Remember that the intruding particles are moving at a high rate of speed, and that changes what is going to happen to them when their path intersects the field lines of the magnetic field.
The math is similar to what is used to describe the operation of an electric motor or generator, the field lines are distorted by the movement and the moving conductors have a current induced in them. That induced current produces a magnetic field that opposes the original field and exerts force.
Actually not. The passage through the shield induces flux into conductive particles, that reacts with the shield flux and turns them aside.
Also, the field flux in the shield is curved, not straight. So they would not point to the pole, anyway, even if they were not moving fast.
Small towns have good restaurants, it's just that everyone knows where they are except you! They don't bother with big signs because everyone grew up there and knows where everything is.
But small towns don't have as many good places as a big city. On the other hand, everyone has guns and you can walk down a dark street without getting robbed. Some places they don't even bother to lock their car doors!
No, it won't.
There are no magnetic monopoles.
They don't even need to be magnetized. They only need to magnetizable. Or, for that matter, just conductive. Magnetic induction would supply the secondary field.
... But fact remains: the "ether" idea is now proven as childish.
Don't kid yourself, the terms are no better known than they were then. The "Luminiferous Aether" was basically a description of the "Space-Time Continuum", except with fewer than 12 dimensions.The terms were not wrong, they just were struggling to describe the concepts. But our math is more complete now...
... Most literature no older than 100 years looks now dated and plain boring (yes, even golden classics). Music from 2 decades ago is mostly stuff that nobody listens anymore (Yes, i know there are exceptions, but few and far between)...
The reason that young people claim not to like old stuff, is not that it is bad. It is that they are scared of the opinion of their peers. They are terrified that they might not be "first and newest", so they cut down the older things. They usually grow out of it eventually...
All of this is probably just a description of instrument loading effects, The answer is easy, just find instruments that are smaller than the sub-atomic particles ! 8-)
Get a good global search utility. Search for every use of the symbol names that you are working with, to see what their scope is and how they are used. You can see how the other code uses them, steal snippets of working code you need, and tell what might "break" your use of them. If you have seen every use of a symbol, in the whole code set, then you can feel more confident that what you are doing will not break things.
Don't try to learn everything at once, your brain can't hold it all right away. Study about the modules and symbols that you must work on. Start with finding out how much you actually -do- have to work on. Then widen your scope as you find more "connections" to other things.
Everything is more complicated than you think, and more complicated than your boss thinks. Be cautious, go carefully, and don't go "running full speed off a cliff". This will actually end up being much faster to a working version.
Frustration is normal, when learning something new. It does not necessarily indicate that the thing you are studying is screwed up (although it might be). Work through the frustration before making changes. (Except, it might be good to make temporary "test" changes to help in the learning.) It is painful, but you will learn and grow from it.
Strongly resist the temptation to re-write stuff that is new to you, no matter how bad it looks. There will usually be good reasons that it is that way, and you will make a disaster. Make good backups of everything before each change and at least every day. There will be places where you must throw away what you have done and go back.
On the other hand, don't be afraid to make global changes to the code set if it is really needed. Just back up a working copy that you can go back to, and be careful.
Do things in phases, even if the "customer" only wants a final version. Make a reasonable set of changes than get it working and debugged. Then do it again for the next changes. Debugging as you go is actually much faster in the long run. Learn to use a Debugger, it is like turning on a light in a dark room.
Find quiet time for several hours to work on it, so that you can get into a "state of flow" mentally. This is much more effective than normal work with interruptions.
HTH.
Maybe we should give him an aimbot, to blast people hiding behind the wall off his lawn
That's called a thutty ought six, and they are a second level perk...
Give a government (or other powerful organization) the power to protect something, and you are also giving it the power to destroy that thing. It has happened before...
Perhaps Al Gore was actually paid by the Oil Companies! Stranger things have happened...
What I don't understand, is how the CO2 level could effect Mars, which also had a temperature rise.
It sounds to me like an awful lot of people are assuming that, if the temperature rose it must have been us... 8-)