Once you've got "smart yoghurt" where does it go? Does it want to die? What if it figures out where it is before you pop a loaf, so to speak? What if it bears a grudge for being dumped? Will it seek revenge?
Will "smart stuff" cause a revitalization of Buddhist thought: "Be careful lest thou injure even the lowly turd, for it too lives!"
weeks later I get a call "I can't save my file! You've messed up my computer! It worked before!!! etc...". Turns out he was trying to use an illegal filename. So a problem he created that had nothing to do with what I had done, had become my problem. And this continued for months.
I've seen this pattern so many times in Windows users that there must be a name for it by now. Anyone know what to call this behavior?
I am astonished that people with no understanding of computers or OSs will
not accept advice to install anti-spyware (SpyBot, Ad-Aware),
not take the time to update or run antivirus software,
disable the software firewall,
download any damn program off the Internet and run it
and then blame me, their technical support specialist, when their system quits working!
Like the OP said, they will insist "It worked before!" or "It worked fine until you changed the system!" when, upon questioning, you find it really never worked. These compu-turds have such egos that they blame anyone/anything except themselves for the crappy state of their systems. In severe cases I put these people on my shitlist and refuse to speak to them. Their behavior unnecessarily dooms them to live in Windows Hell forever.
Perelman... unwilling to go into the level of pedantic and often overbearing detail demanded of modern mathematics journals... proved the theorem like the great masters of old.... [Yau] was the first to publish a more "complete" version of the proof by modern standards.
So Yau et al are "clean-up men" for Perelman? I can see them, with their Dirichlet dustbrooms and Gauss garbage cans, cleaning and polishing the equipment that the "great master of old" left. Rifling through his lab notes one of them yells "Hey, let's publish a paper about this...".
No need to physically destroy the drives; wipe them instead. There are utilities in Windows (e.g., BCWipe, Eraser, WipeDisk, DBAN) and Unix/Linux (dd, DBAN, EBAN ) to do that.
Paranoid nutballs claim that data can somehow be miraculously recovered after multiple overwrites by random data, but even Jesus, the CIA, NSA and George Bush together couldn't do that.
Because, other than IT people, businessmen believe tha "IT Doesn't Matter". The destructive influence of offshore outsourcing combined with the dotcom bust has reduced the influence of IT and IT ideas to noise. Consequently businessmen treat IT as noise.
Maybe businessmen are correct - perhaps IT is no longer important. Will that remain so? My suspicion is "yes".
William Thomson (a.k.a. Lord Kelvin) invented the inkjet printer for telegraphy and got a patent in 1867. Instead of requiring an operator to listen or watch for signals, the signals were printed. Read the story in the book Degrees Kelvin. The device worked well in dry climates, not so well in humid ones. Thompson made a fortune off of it.
In 8-12 years, when they graduate from college, will any current programming language be in popular use (other than COBOL)? Don't you think the computing landscape will be completely different then? You may as well teach them how to use the abacus or sliderule.
I suggest you use MathCad or MatLab or Maple since then at least they'll learn something useful (mathematics).
You're wrong about the designs. Any fissionable material can be used in the "gun" type of fission bomb, wherein two or more pieces of fissionable material are pushed together by an explosion. Hell, you can even do it by hand, as proven in some of the early accidents with nuclear materials. So fission bombs can be dirt simple. Fusion bombs OTOH are complex. See the Nuclear Weapon Archive for details (but remember: "Don't believe everything you read!").
This is the lesson that developing nations around the world have learned.
Noone fucks with you once you have nukes.
Not so: the U.S. will shortly nuke Iran and, after that, North Korea. So both are fucked despite having nukes.
You have to have a lot of nukes and the capability to deliver them before no one will fuck with you. Iran and North Korea do not have both unless, in the case of NK you consider a freighter full of flaky nukes a delivery system. Even then, trading San Francisco for NK is not such a bad deal.
Perhaps it was no accident that the Molotov cocktail was left instead of being tossed into a house. Perhaps they didn't have the criminality necessary to burn a house down and possibly burn men, women and children to death. One would hope so.
If outsourcing doesn't nail the coffin lid shut on software development in the U.S. then software patents certainly will. Now that a firm has patented the technique of navigating a hierarchical tree, the industry has reached new lows.
I need to find a job doing something else before arrays are patented.
After some thought I have concluded that the wiki idea has no advantage over the usual set of input/display forms over HTTP with an underlying relational database. One example mismatch: the wiki has no particular underlying structure so it won't suffice for typical recordkeeping, e.g., Uniform Crime Reporting, which requires gathering offenses by UCR code (e.g., assault, homicide, manslaughter, etc.). A relational database easily handles that.
This isn't to say that you couldn't develop a wiki over an RDBMS. It's just that, if you do, then there's no difference between the two (wiki vs [HTTP forms]).
While it sounds like a success story for FBI agent Depew, the IEEE Article about the VCF system underscores two gaping problems in the FBI's approach to IT:
"Unfortunately, the FBI couldn't provide him with a database program that would help organize the information, so Depew wrote one himself.
- Here we have an FBI agent with so little investigative work to do and so much time on his hands that he can write a DBMS! Why wasn't he prosecuting crimes and chasing the BGs? If indeed there was no software product available on the market, at worst he could have paid a programmer to do the job. This was a bored FBI agent who didn't want to do FBI work - he wanted to write software. But that's not his job! Depew should have been fired for writing a DBMS instead of doing investigative work. That's why specializations exists and that's why the FBI has software specialists.
Since Depew was skilled enought to write his own PC -based DBMS, the FBI decided that he should be put in charge of a multi-million dollar project. This also was a SNAFU. Writing a PC program doesn't qualify you to manage a huge software project.
One of the least known problems in law enforcement is keeping officers and agents focused on their work. They'd much rather take classes in programming, set up websites, build Access databases for the Captain, or in general do anything rather than get out on the street and do policing or legal work. The problem is, no matter what they do, they get the same pay. Policing or tracking down leads requires footwork and is physically demanding, so most veteran agents prefer a desk job.
I'm interested in hearing more about this Wiki approach, please.
The core requirement is merely keeping associated data together. A criminal incident occurs: a crime is committed, there are facts to be written down, photos taken, witnesses statements, objects stolen/used, evidence to be sent to crime lab, and all this has to be captured in a fairly short time and kept together by some tracking system. Incidents are managed: factors added that indicate the likelihood of successful prosecution, investigators assigned and reassigned, new evidence introduced and old evidence invalidated, etc. So the main effort is just in keeping the facts together.
Cross-linking is a second-order function necessary for criminal intelligence and (*gasp*) terrorism. But these are exceptional. Most crime is committed by fairly isolated individuals with significant markers of their behavior and they're not usually difficult to track. That's why I mention the "core requirement".
As for the Wiki, I'm all ears!8-)) I'd like more, please, Sir! [spoken as in the film "Oliver"].
Some other requirements: do/could these fit into the Wiki framework?
Data in a relational database. How do most Wikis store their data?
Statistics must be gathered. How many homicides, rapes, etc. by date, by district or beat, etc.
Auditing is necessary, so we can see who entered/changed data and when,
We'll need to store multimedia: photos, phone calls, lab results (blobs), etc. So seems that the WWW with HTTP is great, since it supports browsers (even w/plugins for arcane vendor-specific data),
I was tempted to say "use NNTP (newsgroups) as an adjunct to tracking criminal incidents", because newsgroups allow security, allow people to add data to a topic, nothing is ever deleted, and there's an obvious history to a topic, like here on/. But AFAIK newsgroups don't have the relational component underlying although it seems possible to build that into a system.
Anyone here know of vendors of criminal RMS (Records Management Software)? Requirements:
municipal police department (millions of citizens)
thousands of incidents per day, of which hundreds are
criminal offenses (100s per day) each offense consisting of data on
suspects
witnesses
victims
officers
leads
automobiles, boats, other vehicles (stolen, lost, used in crime, etc.)
goods, securities, monies, etc. (stolen, lost, etc.)
narrative descriptions from the above of what happened
later supplementary narrative of investigation
thousands of officers assigned
department organized by divisions, beats, special squads,etc. (which are periodically reorganized)
legal geographic management desired (so PD knows if call is inside/outside legal jurisdiction area)
management reports desired
Uniform Crime Reporting (UCR) standard statistics reporting mandatory
National Incident-Based Reporting System (NIBRS) if possible
tying into the above, audit trail of changes & who made them, security management of data (e.g., so suspeneded employess can't see data, only certain employees can see confidential, narcotics data, etc., employees can't snoop other employees' personal data, etc.)
tracking of towed vehicles, impounded goods
tracking of impounded evidence for cases
tracking of evidence through criminal laboratory processing, including outside state or federal (FBI) processing
interchange of data with other governmental entities (e.g., FBI, BATF, etc.) desirable
personnel management
The last item is optional.
Does anyone know of any vendors selling such solutions? My experience has been that this is usually customized, but many police departments have a serious need.
What companies make large COTS records management software solutions for criminal case management? Requirements are roughly:
large city police department (millions of citizens)
thousands of incidents per day, of which
hundreds of criminal offenses per day
thousands of officers assigned
many divisions, beats etc. (which are periodically reorganized)
legal geographic management desired (so PD knows if call is inside/outside legal jurisdiction area)
management reports desired
UCR statistics reporting mandatory
NIBRS if possible
interchange of data with other governmental entities (e.g., FBI, BATF, etc.) desirable
personnel management
tying into the above, security management of data (e.g., so suspeneded employess can't see data, only certain employees can see confidential, narcotics data, etc., employees can't snoop other employees' personal data, etc.)
tracking of towed vehicles, impounded goods]
tracking of impounded evidence for cases
tracking evidence through criminal laboratory processing, including state or federal (FBI) processing
Does anyone know of canned solutions? My experience has been that this is usually customized, but most police departments have a need.
Slashdot Mirror
Will "smart stuff" cause a revitalization of Buddhist thought: "Be careful lest thou injure even the lowly turd, for it too lives!"
I've seen this pattern so many times in Windows users that there must be a name for it by now. Anyone know what to call this behavior?
I am astonished that people with no understanding of computers or OSs will
and then blame me , their technical support specialist, when their system quits working!
Like the OP said, they will insist "It worked before!" or "It worked fine until you changed the system!" when, upon questioning, you find it really never worked. These compu-turds have such egos that they blame anyone/anything except themselves for the crappy state of their systems. In severe cases I put these people on my shitlist and refuse to speak to them. Their behavior unnecessarily dooms them to live in Windows Hell forever.
So Yau et al are "clean-up men" for Perelman? I can see them, with their Dirichlet dustbrooms and Gauss garbage cans, cleaning and polishing the equipment that the "great master of old" left. Rifling through his lab notes one of them yells "Hey, let's publish a paper about this...".
Here's a search at Google for robotic components fitting your requirements.
Sometimes it helps to simplify.
Paranoid nutballs claim that data can somehow be miraculously recovered after multiple overwrites by random data, but even Jesus, the CIA, NSA and George Bush together couldn't do that.
Maybe businessmen are correct - perhaps IT is no longer important. Will that remain so? My suspicion is "yes".
If not, then when will IT recover?
too bad - it's a good company from a stockholder's perspective.
There's no requirement that they accept you, much less take you into their clique. Get some friends outside of work and do your own thing.
I don't know how HP got ahold of his patents!8-))
I suggest you use MathCad or MatLab or Maple since then at least they'll learn something useful (mathematics).
You're wrong about the designs. Any fissionable material can be used in the "gun" type of fission bomb, wherein two or more pieces of fissionable material are pushed together by an explosion. Hell, you can even do it by hand, as proven in some of the early accidents with nuclear materials. So fission bombs can be dirt simple. Fusion bombs OTOH are complex. See the Nuclear Weapon Archive for details (but remember: "Don't believe everything you read!").
Not so: the U.S. will shortly nuke Iran and, after that, North Korea. So both are fucked despite having nukes.
You have to have a lot of nukes and the capability to deliver them before no one will fuck with you. Iran and North Korea do not have both unless, in the case of NK you consider a freighter full of flaky nukes a delivery system. Even then, trading San Francisco for NK is not such a bad deal.
Perhaps it was no accident that the Molotov cocktail was left instead of being tossed into a house. Perhaps they didn't have the criminality necessary to burn a house down and possibly burn men, women and children to death. One would hope so.
Vista appears to be a rare case where both apply.
I need to find a job doing something else before arrays are patented.
This isn't to say that you couldn't develop a wiki over an RDBMS. It's just that, if you do, then there's no difference between the two (wiki vs [HTTP forms]).
Since Depew was skilled enought to write his own PC -based DBMS, the FBI decided that he should be put in charge of a multi-million dollar project. This also was a SNAFU. Writing a PC program doesn't qualify you to manage a huge software project.
One of the least known problems in law enforcement is keeping officers and agents focused on their work. They'd much rather take classes in programming, set up websites, build Access databases for the Captain, or in general do anything rather than get out on the street and do policing or legal work. The problem is, no matter what they do, they get the same pay. Policing or tracking down leads requires footwork and is physically demanding, so most veteran agents prefer a desk job.
I'm interested in hearing more about this Wiki approach, please.
The core requirement is merely keeping associated data together. A criminal incident occurs: a crime is committed, there are facts to be written down, photos taken, witnesses statements, objects stolen/used, evidence to be sent to crime lab, and all this has to be captured in a fairly short time and kept together by some tracking system. Incidents are managed: factors added that indicate the likelihood of successful prosecution, investigators assigned and reassigned, new evidence introduced and old evidence invalidated, etc. So the main effort is just in keeping the facts together.
Cross-linking is a second-order function necessary for criminal intelligence and (*gasp*) terrorism. But these are exceptional. Most crime is committed by fairly isolated individuals with significant markers of their behavior and they're not usually difficult to track. That's why I mention the "core requirement".
As for the Wiki, I'm all ears!8-)) I'd like more, please, Sir! [spoken as in the film "Oliver"].
Some other requirements: do/could these fit into the Wiki framework?
I was tempted to say "use NNTP (newsgroups) as an adjunct to tracking criminal incidents", because newsgroups allow security, allow people to add data to a topic, nothing is ever deleted, and there's an obvious history to a topic, like here on /. But AFAIK newsgroups don't have the relational component underlying although it seems possible to build that into a system.
- municipal police department (millions of citizens)
- thousands of incidents per day, of which hundreds are
- criminal offenses (100s per day) each offense consisting of data on
- suspects
- witnesses
- victims
- officers
- leads
- automobiles, boats, other vehicles (stolen, lost, used in crime, etc.)
- goods, securities, monies, etc. (stolen, lost, etc.)
- narrative descriptions from the above of what happened
- later supplementary narrative of investigation
- thousands of officers assigned
- department organized by divisions, beats, special squads,etc. (which are periodically reorganized)
- legal geographic management desired (so PD knows if call is inside/outside legal jurisdiction area)
- management reports desired
- Uniform Crime Reporting (UCR) standard statistics reporting mandatory
- National Incident-Based Reporting System (NIBRS) if possible
- tying into the above, audit trail of changes & who made them, security management of data (e.g., so suspeneded employess can't see data, only certain employees can see confidential, narcotics data, etc., employees can't snoop other employees' personal data, etc.)
- tracking of towed vehicles, impounded goods
- tracking of impounded evidence for cases
- tracking of evidence through criminal laboratory processing, including outside state or federal (FBI) processing
- interchange of data with other governmental entities (e.g., FBI, BATF, etc.) desirable
personnel management
The last item is optional.Does anyone know of any vendors selling such solutions? My experience has been that this is usually customized, but many police departments have a serious need.
Does anyone know of canned solutions? My experience has been that this is usually customized, but most police departments have a need.