I have also directly experienced an IRA attack when my office was destroyed in the 1996 South Quay bombing. Fortunately I was in the pub at the base of the office block at the time. The windows blew in but we were sheltered from the direct blast. The attack happened in a single moment. Then there was half an hour when everyone was running on pure adrenaline. Then there were the days and weeks of discussing the moment and its aftermath in minute detail. I don't know anyone who experienced it who felt fear at the time or afterwards.
In contrast, the aftermath of the 7/7 attack, which I did not experience directly, was far more stressful for me. Over the next week I was very stressed when using the tube. There would actually be beads of sweat on my face.
I found the difference in my response rather surprising. There could be a number of reasons:
I was ten years older - and more aware of my mortality.
The 'war-on-terror' (TM) had influenced the way the events were reported by the media.
I had directly experienced the first event and not the second.
Explosions in tunnels scare me more than explosions above ground.
Personally I think that terrorism is far more frightening for the detached observer. For those involved it is really no different to any other kind of tragedy such as a serious car accident - something that happens to people all the time. Suddenly something bad happens. Hopefully you get through it and then you get on with your life.
It's a summertime Northern Hemisphere and a wintertime Southern Hemisphere. Slice the world the other way and its daytime in one hemisphere and nighttime in the other. And its always dark down here in my parents' basement.
DST is ambiguous. On morning of the day the clocks go back there is a repeated hour. Scheduling something to happen at a particular time during that hour is ambiguous. It is necessary to say if you want it to happen on the first or second occurrence of that time. Of course that is one of the reasons software should use UTC internally. But what about the human interface? If I want to let people specify a time using their own local time with DST then a bizarre complexity is added to the interaction. Perhaps a dialog box should pop up asking if they want the first or second occurence of 02:21am.
DST is a bad solution as it increase the complexity of the time model everyone has to use. Our experience of programming teaches us that solutions that increase global complexity are rarely a good thing.
A Wikiproof site could use an automated theorem prover (ATP)
to ensure that proofs were correct. I envision it working something like this:
Article submitter submits proof to Wikiproof in the ATP's formal language. This require specificiation of axioms and existing prerequist proofs as well as the steps of current proof.
Wikiproof would use the ATP to verify the proof and, assuming it is correct, translate it into a more human readable form. This could be an iterative process allowing submitter intervention.
The submitter could then annotate the human readable form to explain motivation and reasoning at any stage.
A Wikiproof site could focus on being the human interface to ATPs
Evolution Theory already has a talkback mechanism. Its called "natural selection". It provides a powerful feedback mechanism that filters out the non-beneficial genetic variations in a population. The repair and maintainance of the DNA is part of the phenotype and is also subject to evolutionary pressures of course.
It is possible that his belief that it was a homework problem gave him the confidence that there was a simple and elegant solution. Without this belief he might never have explored solutions that were "too simple" to work.
The creditors (debt holders) have no problem with you reducing the debt. It would allow them to sleep much much better at night if you did reduce it. They obviously have no interest in seeing the dollar collapse but the only way they can prevent this is by continuing to buy US debt. They do not want to do this either. If the US continues on its present economic course then one of the major creditors will blink and pull out as much credit as they can - and the others will follow. This would be a disaster for the world economy.
Ok that is good documentation. I was a bit too emphatic in my claim. But you know what I mean. I don't want to name names but there are a number of projects in which the Doxygen generated documentation is almost entirely pointless. That's not to blame the documentation programs. They clearly can be used well - as you indicated.
I have never seen good documentation produced with JavaDoc or Doxygen. Usually the documentation consists of a page for each class providing nothing that you could not get from a well formatted header file. People just seem to use these tools to tick the documentation box. Someone show me I am wrong and point me to some good automated documentation.
Spread spectrum such as WCDMA (Wide band code division multiplex) is probably the best way to prevent jamming. However there are a couple of difficulties:
1. You need a wide spectrum to spread the energy over. I don't know the details of spectrum allocation in your juristiction but it is unlikely to be available anywhere (except for the military).
2. Whatever the bit rate you transmit at (slow is best) a jammer will always be able to swamp your signal by raising the noise floor sufficiently.
The best way to avoid jamming is to spread the signal over as wide a spectrum as possible, transmit at the lowest possible bit rate and keep a low profile. Whether or not that helps depends on the application you have in mind.
Slashdot Mirror
I have also directly experienced an IRA attack when my office was destroyed in the 1996 South Quay bombing. Fortunately I was in the pub at the base of the office block at the time. The windows blew in but we were sheltered from the direct blast. The attack happened in a single moment. Then there was half an hour when everyone was running on pure adrenaline. Then there were the days and weeks of discussing the moment and its aftermath in minute detail. I don't know anyone who experienced it who felt fear at the time or afterwards.
In contrast, the aftermath of the 7/7 attack, which I did not experience directly, was far more stressful for me. Over the next week I was very stressed when using the tube. There would actually be beads of sweat on my face.
I found the difference in my response rather surprising. There could be a number of reasons:
Personally I think that terrorism is far more frightening for the detached observer. For those involved it is really no different to any other kind of tragedy such as a serious car accident - something that happens to people all the time. Suddenly something bad happens. Hopefully you get through it and then you get on with your life.
I hope you don't mean you use the same password everywhere. If so, CmdrTaco has access to your bank account ;-)
It's a summertime Northern Hemisphere and a wintertime Southern Hemisphere. Slice the world the other way and its daytime in one hemisphere and nighttime in the other. And its always dark down here in my parents' basement.
DST is ambiguous. On morning of the day the clocks go back there is a repeated hour. Scheduling something to happen at a particular time during that hour is ambiguous. It is necessary to say if you want it to happen on the first or second occurrence of that time. Of course that is one of the reasons software should use UTC internally. But what about the human interface? If I want to let people specify a time using their own local time with DST then a bizarre complexity is added to the interaction. Perhaps a dialog box should pop up asking if they want the first or second occurence of 02:21am.
DST is a bad solution as it increase the complexity of the time model everyone has to use. Our experience of programming teaches us that solutions that increase global complexity are rarely a good thing.
If only love were rational then a float would be useful. But love, being irrational, is greater than all things - even long doubles.
I agree.
A Wikiproof site could use an automated theorem prover (ATP) to ensure that proofs were correct. I envision it working something like this:
A Wikiproof site could focus on being the human interface to ATPs
Evolution Theory already has a talkback mechanism. Its called "natural selection". It provides a powerful feedback mechanism that filters out the non-beneficial genetic variations in a population. The repair and maintainance of the DNA is part of the phenotype and is also subject to evolutionary pressures of course.
It is possible that his belief that it was a homework problem gave him the confidence that there was a simple and elegant solution. Without this belief he might never have explored solutions that were "too simple" to work.
The creditors (debt holders) have no problem with you reducing the debt. It would allow them to sleep much much better at night if you did reduce it. They obviously have no interest in seeing the dollar collapse but the only way they can prevent this is by continuing to buy US debt. They do not want to do this either. If the US continues on its present economic course then one of the major creditors will blink and pull out as much credit as they can - and the others will follow. This would be a disaster for the world economy.
While the Russian ethnic group's heartland is in Europe, most of Russia is in Asia along with a huge part of Russia's population. Refer to maps.
Well it looks like your map is wrong then because it puts all of Russia in Asia, not just that part east of the Urals.
Ok that is good documentation. I was a bit too emphatic in my claim. But you know what I mean. I don't want to name names but there are a number of projects in which the Doxygen generated documentation is almost entirely pointless. That's not to blame the documentation programs. They clearly can be used well - as you indicated.
I have never seen good documentation produced with JavaDoc or Doxygen. Usually the documentation consists of a page for each class providing nothing that you could not get from a well formatted header file. People just seem to use these tools to tick the documentation box. Someone show me I am wrong and point me to some good automated documentation.
Spread spectrum such as WCDMA (Wide band code division multiplex) is probably the best way to prevent jamming. However there are a couple of difficulties: 1. You need a wide spectrum to spread the energy over. I don't know the details of spectrum allocation in your juristiction but it is unlikely to be available anywhere (except for the military). 2. Whatever the bit rate you transmit at (slow is best) a jammer will always be able to swamp your signal by raising the noise floor sufficiently. The best way to avoid jamming is to spread the signal over as wide a spectrum as possible, transmit at the lowest possible bit rate and keep a low profile. Whether or not that helps depends on the application you have in mind.