Not if the announcement of the recall need makes that car much more likely to be e.g. stolen, while at the same time no actual fix is available from the carmaker.
As a practically oriented car owner I'm neither interested in having my car stolen or keeping it locked up in a sealed garage for an unspecified period of time.
I would however be willing to take the minute risk that someone else might discover the same ingenious break-in vulnerability and try it out on my car while my car vendor is secretly working on a solution to the problem.
I prefer to use my laptop indoors due to LCD display contrast issues in direct sunlight. A GPS receiver, on the other hand, is designed for outdoors use.
It requires a straight signal path between the satellite and the receiver. For exact positioning you even need a straigth signal path to 3 GPS satellites.
Here in Europe you may get positioning services based on GSM phone signal triangulation principles. It works well for devices located indoors, but the positioning is provided as a service through the mobile network and is not performed by calculations in your mobile phone PCMCIA card.
What has always worried me about the so called "war on terrorism" is
a) The intense volume and passion with which our leaders boast their efforts to counter terrorism. This may win hearts, minds and votes at home. But when the same speech is televised live on Al Jazeera it is interpreted by many muslims almost like Osama bin Laden speeches are interpreted by us.
b) The ridiculous use of bombs causing huge explosions and the massive stationing of uniformed military personell in the environments that are most sensitive to the perceived consequences of western influence. You might kill a terrorist or two, but the propaganda value of the TV pictures create 10 new ones.
I don't object to using a lot of resources to combat terror. Neither do I believe that anti-terror measures should have a lower priority.
But we could do it a lot more intelligently:
i)By using our resources to increase our capabilities for clandestine operations.
ii)By whacking all the terrorists we find and then shut up about it.
iii)By tripling the number of people following the different terrorist money trails.
iv)By quadroupling the efforts to set up schooling arrangements that aren't bogged down with religious crap in the concerned muslim countries.
v)By investing a lot more in pro-western media (propaganda) directed at a muslim audience.
vi)On every other level: By staying out of these people's affairs and let them sort out their own problems.
And - most importantly - to keep such a well financed campaign against terrorism effective we STFU about it as much as possible, thereby making it less easy for militant terrorist to paint a convincing picture of an actual enemy.
Therein lies the rub, I guess. Since the politicans need public support for their antiterrorism spending, they will keep using high profile tactics (with a lot of bang for the buck). They will also keep on boasting their achievements to get the funding that they need. Kind of sad really.
The design document should feature explanations of your architectural patterns. Those are less likely to change in the short term and therefore makes the document less problematic to maintain.
Let's say that you are writing an MS.NET Windows forms application and you have the following dataaccess strategy (which may or may not be 100%, though that is irrelevant) - write stored procedures, - generate datasets, - encapsulate the datasets in a business object. - implement typical NELS features in the business object - databind GUI on top of that.
Your design document should contain one or more system sequence diagrams, and a class diagram to communicate to other/new developers the key aspects of how this pattern is implemented and which consequences it has. Document the stuff that represents core design desicions, and not all the stuff that is evident from the code.
Don't hesitate to use descriptions such as "Adapter", "Bridge" or "Abstract Factory" in your design document. It might actually help a future co-worker.
Do not Ctrl-C Ctrl-V chapters in your design document to cover every single business object that is created using a pattern. Mention special cases only if they deviate significantly.
Document complexity and not the simple stuff! A complex security model, an algorithm to calculate optimal scheduling are both examples of things that should be given special attention. Use the appropriate documentation techniques in each case.
Document a specific feature type or an idea behind the application as opposed to describing how these ideas apply to every single class
Document a design decision even if you know it could be better! A lot of developers make design decisions that they know have deficiencies. Either due to incompetence or lack of time (or both). It may even be these design decisions that are most important to document(since really good designs often are more selfexplanatory). Many developers choose to leave such low-quality decisions silently undocumented because their gut feeling tells them they're on thin ice.
I have no idea how many hours I have spent trying to figure out whether I can change some spaghetti code or whether there is som hidden meaning behind those 20 layers of nested if's:-D
Firstly: I actually find it easiest to think of the Universe (in the true sense of the word) as something that have existed for infinity.
Secondly: Maybe the dimension time as such is too simplistic a dimension to be applying when measuring the development of the universe. After all: Time really only makes sense for slow moving objects in proximity to eachother.
The problem is that even though it feels nice to fill the seeming holes of scientific theory with religious stuffing, it doesn't make it reasonable or scientifically sound to do so.
The
"where do we come from?" "why are we here?" and "where are we going?"
questions have been asked by humans in many generations in all known cultures.
IMHO those questions where the reason we as humans invented our multitude of different religions.
I believe the answers to the questions to be: a) nowhere special (we are constituted by the atoms that are part of our cellular organism) b) no particular reason (other than to reproduce our DNA for future generations) and
c) nowhere special (other than to have our biological material be decomposed or combusted)
Now most people will say that this is a cynical, cold, uninspired and pessimistic view of life. Sure it is. But it is by far the most probable explanation.
Why is it that when faced with a negative consequence of their logical reasoning so many minds go bluescreen and stop responding.
A lot of people here have made a mockery of the relevance of spyware removal tools, and even questioned whether spyware is a real issue at all.
These people probably haven't tried to combat the latest strains of the CoolWebSearch infestation.
Visiting a friend recently I noticed his laptop had gone totally Ga-ga, and I offered to help, thinking that a quick anti-virus scan accompanied by ad-aware cleansing, would get the unit back in shape. It didn't. I tried every automated and manual step-by-step procedure I could find on the net and nothing seemed to help.
The premier anti-CoolWebSearch volunteer on the net seemed to have given up (as reported by the Register)
I ended up deciding that it was less time consuming to save the few vital files that existed on the machine, and reinstall the operating system, rather than trying a meticulous process-creation-timestamp-analysis.
The operating system I reinstalled was Win XP (not Linux). Why? Because my friend is a technically challenged moron and will never be capable of using anything but Windows for desktop computing.
Well. No.
Not if the announcement of the recall need makes that car much more likely to be e.g. stolen, while at the same time no actual fix is available from the carmaker.
As a practically oriented car owner I'm neither interested in having my car stolen or keeping it locked up in a sealed garage for an unspecified period of time.
I would however be willing to take the minute risk that someone else might discover the same ingenious break-in vulnerability and try it out on my car while my car vendor is secretly working on a solution to the problem.
GPS in laptops might not work so well.
I prefer to use my laptop indoors due to LCD display contrast issues in direct sunlight. A GPS receiver, on the other hand, is designed for outdoors use.
It requires a straight signal path between the satellite and the receiver. For exact positioning you even need a straigth signal path to 3 GPS satellites.
Here in Europe you may get positioning services based on GSM phone signal triangulation principles. It works well for devices located indoors, but the positioning is provided as a service through the mobile network and is not performed by calculations in your mobile phone PCMCIA card.
What has always worried me about the so called "war on terrorism" is
a) The intense volume and passion with which our leaders boast their efforts to counter terrorism. This may win hearts, minds and votes at home. But when the same speech is televised live on Al Jazeera it is interpreted by many muslims almost like Osama bin Laden speeches are interpreted by us.
b) The ridiculous use of bombs causing huge explosions and the massive stationing of uniformed military personell in the environments that are most sensitive to the perceived consequences of western influence. You might kill a terrorist or two, but the propaganda value of the TV pictures create 10 new ones.
I don't object to using a lot of resources to combat terror. Neither do I believe that anti-terror measures should have a lower priority.
But we could do it a lot more intelligently:
i)By using our resources to increase our capabilities for clandestine operations.
ii)By whacking all the terrorists we find and then shut up about it.
iii)By tripling the number of people following the different terrorist money trails.
iv)By quadroupling the efforts to set up schooling arrangements that aren't bogged down with religious crap in the concerned muslim countries.
v)By investing a lot more in pro-western media (propaganda) directed at a muslim audience.
vi)On every other level: By staying out of these people's affairs and let them sort out their own problems.
And - most importantly - to keep such a well financed campaign against terrorism effective we STFU about it as much as possible, thereby making it less easy for militant terrorist to paint a convincing picture of an actual enemy.
Therein lies the rub, I guess. Since the politicans need public support for their antiterrorism spending, they will keep using high profile tactics (with a lot of bang for the buck). They will also keep on boasting their achievements to get the funding that they need. Kind of sad really.
Apparently an individual named Benoit Lecomte actually completed the feat. http://www.everything2.com/index.pl?node_id=142558 6
The design document should feature explanations of your architectural patterns. Those are less likely to change in the short term and therefore makes the document less problematic to maintain.
:-D
Let's say that you are writing an MS.NET Windows forms application and you have the following dataaccess strategy (which may or may not be 100%, though that is irrelevant)
- write stored procedures,
- generate datasets,
- encapsulate the datasets in a business object.
- implement typical NELS features in the business object
- databind GUI on top of that.
Your design document should contain one or more system sequence diagrams, and a class diagram to communicate to other/new developers the key aspects of how this pattern is implemented and which consequences it has. Document the stuff that represents core design desicions, and not all the stuff that is evident from the code.
Don't hesitate to use descriptions such as "Adapter", "Bridge" or "Abstract Factory" in your design document. It might actually help a future co-worker.
Do not Ctrl-C Ctrl-V chapters in your design document to cover every single business object that is created using a pattern. Mention special cases only if they deviate significantly.
Document complexity and not the simple stuff!
A complex security model, an algorithm to calculate optimal scheduling are both examples of things that should be given special attention. Use the appropriate documentation techniques in each case.
Document a specific feature type or an idea behind the application as opposed to describing how these ideas apply to every single class
Document a design decision even if you know it could be better! A lot of developers make design decisions that they know have deficiencies. Either due to incompetence or lack of time (or both). It may even be these design decisions that are most important to document(since really good designs often are more selfexplanatory). Many developers choose to leave such low-quality decisions silently undocumented because their gut feeling tells them they're on thin ice.
I have no idea how many hours I have spent trying to figure out whether I can change some spaghetti code or whether there is som hidden meaning behind those 20 layers of nested if's
Firstly: I actually find it easiest to think of the Universe (in the true sense of the word) as something that have existed for infinity.
Secondly: Maybe the dimension time as such is too simplistic a dimension to be applying when measuring the development of the universe. After all: Time really only makes sense for slow moving objects in proximity to eachother.
The problem is that even though it feels nice to fill the seeming holes of scientific theory with religious stuffing, it doesn't make it reasonable or scientifically sound to do so. The
"where do we come from?"
"why are we here?" and
"where are we going?"
questions have been asked by humans in many generations in all known cultures.
IMHO those questions where the reason we as humans invented our multitude of different religions.
I believe the answers to the questions to be:
a) nowhere special (we are constituted by the atoms that are part of our cellular organism)
b) no particular reason (other than to reproduce our DNA for future generations) and
c) nowhere special (other than to have our biological material be decomposed or combusted)
Now most people will say that this is a cynical, cold, uninspired and pessimistic view of life. Sure it is. But it is by far the most probable explanation. Why is it that when faced with a negative consequence of their logical reasoning so many minds go bluescreen and stop responding.
A lot of people here have made a mockery of the relevance of spyware removal tools, and even questioned whether spyware is a real issue at all. These people probably haven't tried to combat the latest strains of the CoolWebSearch infestation. Visiting a friend recently I noticed his laptop had gone totally Ga-ga, and I offered to help, thinking that a quick anti-virus scan accompanied by ad-aware cleansing, would get the unit back in shape. It didn't. I tried every automated and manual step-by-step procedure I could find on the net and nothing seemed to help. The premier anti-CoolWebSearch volunteer on the net seemed to have given up (as reported by the Register) I ended up deciding that it was less time consuming to save the few vital files that existed on the machine, and reinstall the operating system, rather than trying a meticulous process-creation-timestamp-analysis. The operating system I reinstalled was Win XP (not Linux). Why? Because my friend is a technically challenged moron and will never be capable of using anything but Windows for desktop computing.