implies that "human" can and is also used to refer to the genus homo, not just the species and subspecies sapiens
Human: A member of the genus Homo and especially of the species H. sapiens. *Especially*. I doubt that you would find many people who would consider pre-Neanderthals to be 'human'. Maybe human like, but thats about it.
You're making things up stating that humans have lived for millions of years and have lived through several pole flips without incident. You have no basis for these claims.
My claim is based on the scientific knowledge of what the radiation from a solar flare will do to someone that has no protection.
No. Anyone who says ' this method will never work', or 'this is the only development method that is good', doesn't know what they are talking about. You adapt whatever process, tool or approach is necessary for the specific program. Agile doesn't work for everything and neither does waterfall (or any one specific approach for that matter)
Fixed price contracts are a reality, and I'd say a majority of development projects use this, where software is mixed with hardware. You have to adapt your practices to suit the business model and customer. You can't simply say 'I don't do that'. If you cant fix bid a contract you cant estimate your own time nor anyone elses.
There is nothing wrong with waterfall. requirements - preliminary design - advanced design - implement - test is the logical way to develop. However I agree it is unrealistic to try and do 100% completion on each step before going to the next step. That approach is a misunderstanding of how waterfall is to be used which is why I say modified iterative waterfall.
Actually your attitude is EXACTLY the problem I've been complaining about. It's either your way or no way, and every other way other than what you know is absolute crap. That is the closed minded approach that results in bad code, poor performance and failed projects. Open your eyes and your mind - you may learn something.
It depends on your definition of "human." The human lineage has been around for some three million years.
Sure if you want to call our ancestral monkeys 'human'. Typically 'human' refers solely to homo sapien. I don't call that nitpicking. The Neanderthals hadn't even made an appearance yet in the timeframe we are talking about.
I should clarify. How about without a magnetosphere, a whole shitload of people will die. If the earth gets hit by a solar flare without the protection of the magnetosphere, the radiation will kill a lot of people unless they are protected.
And what do you base the 'no mass extinction on previous pole reversals from'? No, there wasn't a mass extinction like the dinosaurs as the fossil record clearly shows a big gap in that timeframe. But the fossil records are not complete enough to determine even say a 50% or 70% reduction in the population. The time of the last pole reversal also coincides with the exodus out of Africa for our direct descendants. Maybe that major event in our history were tied to the pole reversal - maybe not. Who knows?
Where is your basis for 'a few'. Satellites in LEO and GEO are not heavily protected from solar flare activity. Many if not all will be fried if the magnetosphere is gone.
We will also not be protected from solar radiation as much. Special shelters will have to be constructed and skin cancers will go WAY up.
I don't use waterfall, we use a modified iterative waterfall. I guarantee you that is not the problem.
Our projects, all customer requirements are known up front. We have to provide a firm fixed price up front. If you think you can provide that with an Agile (just give me all the resources we need and we'll document what you get later, and I really dont know how much time or money this will take) approach then you are sorely mistaken and don't know how mission critical projects are costed or executed.
We know for a fact that geomagnetic reversals (including a period of dozens to hundreds of years without a significant magnetic field) happen several times every million years. They are not accompanied by mass extinctions. Therefore, we would not fry.
How is that since Homo Sapiens only first arrived 195 thousand years ago, mitochondrial eve was 150 thousand years ago, and as far as we cal tell, the last magnetic flip happened 780 000 years ago.
No, thats not it. I had an amazing team (multi discipline, not just software), and we did great work. I was project and technical lead, not management. However there was this one sole software lead on my program that refused to work to an established design, refused to document anything, refused to take any direction whatsoever because he thought he was perfect in every way. He would blam all his problems on everything and everyone you can imaging, management, the other members of the team, the hardware, the development tools, third party drivers, the OS, the CPU, you name it. Then lie and backstab to try and hide his incompetence.
I generally don't blame anyone as we are all a team, but in this case all problems can be clearly traced to one person and his refusal to follow any direction.
So, when the coder messes up it's the coders fault.
But when management messes up it's still the coders fault, just because he didn't quit fast enough?
No, thats not what I' saying at all.
If the coder blindly accepts a management directive to do the impossible without telling management that it cannot be done, yes that is the coders fault. If management asks for something impossible, and the coder responds with a 'sorry that cant be done, but I can do this, or I can do it in this amount of time', then there is no fault there - that just good teamwork. If the manager is stupid enough to not believe his team and says do it anyway, then its the managers fault.
And my original post wasn't about silly bugs - everyone makes mistakes and those are easy to fix and find. I'm talking about ignoring the desing, I'm doing it my way screw you fundamental architectural mistakes that in my case put peoples lives in danger.
As for blame, generally yes, its a team effort, there's no point in blaming anyone as this does not fix the issues. However there comes a time when a person has such a train wreck of disaster behind him, and no successes, and a history of backstabbing and lying to protect his incompetence that blame must be assigned. It's like having a driver speed drunk though a busy intersection against a red, causing a multi-car pileup. The police don't just say 'aww it was a team effort - we're not going to blame anyone'. At some level of screwup the person at fault needs to be removed for the sake of everyone else left.
Incidentally, this person in question would blame almost anything except the real problem which was himself - the customer, management, the other team members, the requirements, documentation, every piece of hardware, third party drivers, the operating system, bugs in the microcode of the CPU, you name it, I've heard every excuse in the book from this idiot.
Also, two identical programs can be bug free, but one architecture poorly and one well. A missed feature added to a poor architecture will likely break everything, or cause new bugs in previously working code. A well architected program can be expanded without a significant negative impact (within reason of course).
Please see my previous response on this. If a manager asks you to do the impossible - REFUSE, and give him an alternate suggestion or a cost and schedule of when it realistically CAN be done. Don't just say yes sir, then bitch about what a bunch of idiots management is. YOU are the domain expert - YOU tell management what can and cannot be done.
Slashdot Mirror
implies that "human" can and is also used to refer to the genus homo, not just the species and subspecies sapiens
Human: A member of the genus Homo and especially of the species H. sapiens. *Especially*. I doubt that you would find many people who would consider pre-Neanderthals to be 'human'. Maybe human like, but thats about it.
You're making things up stating that humans have lived for millions of years and have lived through several pole flips without incident. You have no basis for these claims.
My claim is based on the scientific knowledge of what the radiation from a solar flare will do to someone that has no protection.
No. Anyone who says ' this method will never work', or 'this is the only development method that is good', doesn't know what they are talking about. You adapt whatever process, tool or approach is necessary for the specific program. Agile doesn't work for everything and neither does waterfall (or any one specific approach for that matter)
Fixed price contracts are a reality, and I'd say a majority of development projects use this, where software is mixed with hardware. You have to adapt your practices to suit the business model and customer. You can't simply say 'I don't do that'. If you cant fix bid a contract you cant estimate your own time nor anyone elses.
There is nothing wrong with waterfall. requirements - preliminary design - advanced design - implement - test is the logical way to develop. However I agree it is unrealistic to try and do 100% completion on each step before going to the next step. That approach is a misunderstanding of how waterfall is to be used which is why I say modified iterative waterfall.
Actually your attitude is EXACTLY the problem I've been complaining about. It's either your way or no way, and every other way other than what you know is absolute crap. That is the closed minded approach that results in bad code, poor performance and failed projects. Open your eyes and your mind - you may learn something.
It depends on your definition of "human." The human lineage has been around for some three million years.
Sure if you want to call our ancestral monkeys 'human'. Typically 'human' refers solely to homo sapien. I don't call that nitpicking. The Neanderthals hadn't even made an appearance yet in the timeframe we are talking about.
I should clarify. How about without a magnetosphere, a whole shitload of people will die. If the earth gets hit by a solar flare without the protection of the magnetosphere, the radiation will kill a lot of people unless they are protected.
And what do you base the 'no mass extinction on previous pole reversals from'? No, there wasn't a mass extinction like the dinosaurs as the fossil record clearly shows a big gap in that timeframe. But the fossil records are not complete enough to determine even say a 50% or 70% reduction in the population. The time of the last pole reversal also coincides with the exodus out of Africa for our direct descendants. Maybe that major event in our history were tied to the pole reversal - maybe not. Who knows?
Where is your basis for 'a few'. Satellites in LEO and GEO are not heavily protected from solar flare activity. Many if not all will be fried if the magnetosphere is gone.
We will also not be protected from solar radiation as much. Special shelters will have to be constructed and skin cancers will go WAY up.
No, but they had a lot more hair, just like animals that tend not to get skin cancer.
They also didn't build a society on technology that will fail without the radiation protection of a magnetosphere.
I don't use waterfall, we use a modified iterative waterfall. I guarantee you that is not the problem.
Our projects, all customer requirements are known up front. We have to provide a firm fixed price up front. If you think you can provide that with an Agile (just give me all the resources we need and we'll document what you get later, and I really dont know how much time or money this will take) approach then you are sorely mistaken and don't know how mission critical projects are costed or executed.
We know for a fact that geomagnetic reversals (including a period of dozens to hundreds of years without a significant magnetic field) happen several times every million years. They are not accompanied by mass extinctions. Therefore, we would not fry.
Don't you read any scientific journals? http://www.indiadaily.com/editorial/1753.asp
Really? Pole reversals plural??
How is that since Homo Sapiens only first arrived 195 thousand years ago, mitochondrial eve was 150 thousand years ago, and as far as we cal tell, the last magnetic flip happened 780 000 years ago.
The magnetic north pole is also physically a south pole.
They must average the hell out of the measurements. Their stated accurtacy using DGPS is 2-3m.
I did a simple calculation: 3m error, typically you want to get the error below 10%, so that means multiply by 10. Hence a 30m cow.
Now if you moved the cow and averaged over time, then the error would become smaller and you can shrink your cow.
I would mod him down, but global warming caused my mod points to evaporate.
Actually to confuse things further, the magnetic north pole is physically a 'south' pole, and vice versa.
A lot of good alternative navigation will get us when the magnetosphere collapses and the suns radiation kills us all.
Hey! Don't make us start charging for all that free compass use we've been graciously letting you have.
Without a magnetic field to stop the solar wind, satellites tend to die.
Actually without a magnetic field, and the generated magnetosphere, pretty much all life on earth will die.
Granted, as the commenter previous to my original comment indicated, you need a large cow for this
Your cow would need to be about 30 meters long to get decent nose to tail pointing accuracy.
Magnetic North has been in Canada ever since Canadians invented it. The world owes us a LOT of back royalties for the use of those compasses.
Basically what QuoteMstr is saying is that Republicans are to blame for everything. Including Santa hating Linux.
No, thats not it. I had an amazing team (multi discipline, not just software), and we did great work. I was project and technical lead, not management. However there was this one sole software lead on my program that refused to work to an established design, refused to document anything, refused to take any direction whatsoever because he thought he was perfect in every way. He would blam all his problems on everything and everyone you can imaging, management, the other members of the team, the hardware, the development tools, third party drivers, the OS, the CPU, you name it. Then lie and backstab to try and hide his incompetence.
I generally don't blame anyone as we are all a team, but in this case all problems can be clearly traced to one person and his refusal to follow any direction.
Oh please... give it a rest.
So, when the coder messes up it's the coders fault. But when management messes up it's still the coders fault, just because he didn't quit fast enough?
No, thats not what I' saying at all.
If the coder blindly accepts a management directive to do the impossible without telling management that it cannot be done, yes that is the coders fault. If management asks for something impossible, and the coder responds with a 'sorry that cant be done, but I can do this, or I can do it in this amount of time', then there is no fault there - that just good teamwork. If the manager is stupid enough to not believe his team and says do it anyway, then its the managers fault.
And my original post wasn't about silly bugs - everyone makes mistakes and those are easy to fix and find. I'm talking about ignoring the desing, I'm doing it my way screw you fundamental architectural mistakes that in my case put peoples lives in danger.
As for blame, generally yes, its a team effort, there's no point in blaming anyone as this does not fix the issues. However there comes a time when a person has such a train wreck of disaster behind him, and no successes, and a history of backstabbing and lying to protect his incompetence that blame must be assigned. It's like having a driver speed drunk though a busy intersection against a red, causing a multi-car pileup. The police don't just say 'aww it was a team effort - we're not going to blame anyone'. At some level of screwup the person at fault needs to be removed for the sake of everyone else left.
Incidentally, this person in question would blame almost anything except the real problem which was himself - the customer, management, the other team members, the requirements, documentation, every piece of hardware, third party drivers, the operating system, bugs in the microcode of the CPU, you name it, I've heard every excuse in the book from this idiot.
Good post - I agree completely.
Also, two identical programs can be bug free, but one architecture poorly and one well. A missed feature added to a poor architecture will likely break everything, or cause new bugs in previously working code. A well architected program can be expanded without a significant negative impact (within reason of course).
Please see my previous response on this. If a manager asks you to do the impossible - REFUSE, and give him an alternate suggestion or a cost and schedule of when it realistically CAN be done. Don't just say yes sir, then bitch about what a bunch of idiots management is. YOU are the domain expert - YOU tell management what can and cannot be done.
What exactly was arrogant about my postings?
Why? Don't you think that is the way it should be?