Split the balls into 2 sets of 6, place the sets on both ends of the scale and weigh them
It's all in the presentation. I immediately thought of using a bathroom scale. It doesn't have two sides.. (Though I can't think that I've ever used a two sided scale.. only had one side in chem..)
I would be satisfied if Mozilla's new name was just "Not Internet Explorer".
Why not just 'IE'? I don't know anything that's NAMED "IE", there is some other browser that I think some people CALL "IE", but that's not it's name...
OR.
1. Get a life.
Please XP is a PITA enough just trying to remember the key itself. You REALLY think I'm going to go through all that garbage so someone can't spy on my slashdot profile?
Get a life. It's 802.11. If anyone tries that at my house, they're on my property, and will get a pummeling.
I need a sign, "Forget the dog, beware of owner (802.11)".
I strongly disagree. There were two big hurdles to getting VFP working. First was a mouse click bug. Duane Clark (IIRC, can't seem to reach the arcives) fixed that. The second was file locking. File locking is a BIG issue for any program that wants to be multi-user friendly (such as FoxPro or Access). Alexandre Julliard did that work, and is DIRECTLY related to Codeweavers being able to say they support MS Access.
Umm.. Borland's Delphi/CPP-Builder does all this. And Kylix too for Linux machines.
I'd agree with everything but the RAD stuff. Foxpro actually allows you to program 'interactively'. You get a command window, and can execute a single line of code, just to see what would happen.
The commands are stupid-simple, and unfortunately, Kylix doesn't open VFP tables. I need VFP on Linux, because I have legacy tables from proprietary applications to support:/
When you have several gigabytes of data to process in a non-CPU-intensive manner, you can't afford to save everything to a central server.
I don't get it.. You are hardly using any CPU cycles, but at the same time can't process that data off a central server?
Non-CPU intensive manner? Did you mean it's just simple work on large files (such as importing tab/comma delimited text files to a database)?
You have users do this? AND run MS Office? That seems like an odd combination..
Sometimes, it just makes sense to store vital data on workstations (and back them up periodicaly).
IMHO, a 'workstation' is a place to work. Not to save data. 'workstations' should be able to be replaced without the knowledge of the user. Not for being sneaky, of course, but to allow a user with a bad 'workstation' to be able to get back to work asap.
You have so much problems - Emails with the wrong date which make you look stupid (and may cause to not be read at all), programs complaining about files made in the future, confusion about which day is today ("but my calendar said that the 8th was saturday") and lots of other problems.
What the hell are you talking about?
OHHH you are ASSUMING these people use Outlook for email/calendar.
You're assuming they run programs that compare the time stamp on files to the system time.
You're assuming they use roaming profile shit
Don't assume. I'm merely pointing out that environments DO EXIST (the orginal post also said it interfered with their content mgmt system) where a correct workstation time isn't necessary.
If someone can't figure out on their own if this applies to them or not, then they're an idiot.
Tell the users to save ALL files on S:\. Now set your office prefs default directory to S:, and 99% of the time the user won't even know the difference.
Yeah, they won't notice the difference because they will still save the files on their C drive. At least that's been my experience.
I've been doing this at different companies for 7 years from Win 3.1 to Win2k. If they have files on C:, move them to S:, change their default save locations, tell them to save everything on S:. S: is their personal home directory.
Once their default locations are changed, they have to PURPOSELY save to c:. If you've informed them in writing, AND you've made these default changes, any lost files due to workstation issues is entirely the fault of the user. They can bitch an moan all they want, but if you lay it all out for them, there's nothing that can touch you.
You can say, "Hey, I did this, this and told them that. Their workstation is configured to save on the server, and that user decided not to. There isn't anything more that can be done, they need to change their habits."
If need be, include the S: drive notification with the information you give new users (passwords/email addr/etc). Make it a template, standard form, whatever. Make SURE they know saving on C is nothing less than reckless.
You have (L)users that actually listen to what you say? Dude, where do I sign up?
I didn't say they listened, you have to tell them to cover your butt.;) That's why I also said to change their default paths too, that double covers your butt, because now the users have to purposely save somewhere else.
You assume everything is kept on the fileservers, not in most environments. Yes you want to save thing off to the fileservers for distribution and backup but most people work on their files on their local pc's. This is the situation at almost every shop I have been to.
And you didn't fix it? That's just bad networking.
MAP ROOT S:=SERVER/Volume:USERS/$USERNAME
Tell the users to save ALL files on S:\. Now set your office prefs default directory to S:, and 99% of the time the user won't even know the difference.
IMHO, in a Windows environment, MAP ROOT is a PITA. But what are you using Windows as a file server for? Ahh, you're paid hourly:P
No no.. Why would you set the server clock back? It's not the timestamps on the files that Office is reading, it's the PC's clock. When I write from a PC with a date of 01-01-01, to a server with today's date, the file created/modified will have todays date on it.
So you can change the workstations, and not affect your file's timestamps.
Seems like it would be a good idea to me to hire a woman who 'straightened out' DoubleClick's privacy issues, for a job with a government that is currently pushing laws like the Patriot Act.
It's a logical assumption that she will bring her DoubleClick experience to the 'Homeland Security' table. Instead of having guys sitting around trying to figure out how to track/spy on criminals, and not thinking about how it might affect the average joe, there's now somebody there to essentailly speak for the privacy advocates before privacy altering laws are drafted.
My professor later berated my choice of topics as (his words not mine) "he is an obvious lawless felon and is not worthy of this class's time". How do you respond to this unfair characterization by others?
Or better:
How do you respond to those who say you merely stumbled onto something (the whistle) that did something that was already known by EVERYONE (2600hz tones which was published in AT&T Manuals in PUBLIC Libraries), and exploited it for personal gain (free phone calls/publicity)?
So, what are you saying? That we should just let it happen because it's going to anyway? That it's wrong to correct people?
It IS possible to be TOO anal.
You win some, and you lose some. Haven't you ever played Othello?
If you don't lose some, you'll get labeled as a fanatic, and you won't win ANYTHING from that point on. Like I've said before, the language is constantly changing. It's probably the only thing that's truly democratic.
Now, all dilbert joking aside, this is one disease that scares me... without a common vector identified.... we might all be in for it.
No kidding. This thing is being reported as the kiss of death. This is the first time I've seen ANYTHING like the following in ANY news report: Around two-thirds of people diagnosed with SARS in Singapore have recovered.
I wish someone would have said that earlier. It's the last line in the linked article, and it almost seems like an afterthought. Why is it just like the media to never say "Oh, yeah, and people really ARE surviving this disease."
If you no longer have the machines then you don't renew. What's the big deal?
I think people are thinking it's paid yearly, on a 3 year contract.
In any case, IMHO, this only applies to companies that aren't going downhill. Any decently large company will have a their own lawyer, and already leverage that person to get out of contracts regularly. (I worked at a credit card processor that got out of quite a few contracts with just a phone call to the corp lawyer).
"In the three different states that I grew up in (15 years ago), 'gay' meant 'stupid' - it had nothing to do with sexual orientation"
Yes you dumb fuck, it means stupid to stupid, bigotted people. So when people call a stupid law or a fat person "american-style", you don't find that offensive? Get a life, loser.
Ignoring the first sentence, which is nothing more than drivel, I don't personally have a problem with you replacing 'stupid law' or 'fat person' with 'american-style'. Could you use that in a sentence, so I can recognize it in the future? That almost seems too broad a replacement to be anything more than more drivel.
I live in the fattest state in the Union (Oh damn, I offended all the southerners now), you can call us fat/cheeseheads/whatever. I personally don't have a problem with that, and that's direct name-calling.
There was this thing I learned a LONG time ago.. Hmm, how did that go? Oh, yeah: "Stick and Stones may break my bones.."
Slashdot Mirror
It's all in the presentation. I immediately thought of using a bathroom scale. It doesn't have two sides.. (Though I can't think that I've ever used a two sided scale.. only had one side in chem..)
Did anyone else just automatically put 'disk' at the end of 'large properly formatted data'?
I was wondering why anyone would still want an 8" disk..
Why not just 'IE'? I don't know anything that's NAMED "IE", there is some other browser that I think some people CALL "IE", but that's not it's name...
Get a life. It's 802.11. If anyone tries that at my house, they're on my property, and will get a pummeling.
I need a sign, "Forget the dog, beware of owner (802.11)".
In a strange ironic twist, those go away when you do pay..
I strongly disagree. There were two big hurdles to getting VFP working. First was a mouse click bug. Duane Clark (IIRC, can't seem to reach the arcives) fixed that. The second was file locking. File locking is a BIG issue for any program that wants to be multi-user friendly (such as FoxPro or Access). Alexandre Julliard did that work, and is DIRECTLY related to Codeweavers being able to say they support MS Access.
I'd agree with everything but the RAD stuff. Foxpro actually allows you to program 'interactively'. You get a command window, and can execute a single line of code, just to see what would happen.
The commands are stupid-simple, and unfortunately, Kylix doesn't open VFP tables. I need VFP on Linux, because I have legacy tables from proprietary applications to support :/
I don't get it.. You are hardly using any CPU cycles, but at the same time can't process that data off a central server?
Non-CPU intensive manner? Did you mean it's just simple work on large files (such as importing tab/comma delimited text files to a database)?
You have users do this? AND run MS Office? That seems like an odd combination..
Sometimes, it just makes sense to store vital data on workstations (and back them up periodicaly).
IMHO, a 'workstation' is a place to work. Not to save data. 'workstations' should be able to be replaced without the knowledge of the user. Not for being sneaky, of course, but to allow a user with a bad 'workstation' to be able to get back to work asap.
What the hell are you talking about?
OHHH you are ASSUMING these people use Outlook for email/calendar.
You're assuming they run programs that compare the time stamp on files to the system time.
You're assuming they use roaming profile shit
Don't assume. I'm merely pointing out that environments DO EXIST (the orginal post also said it interfered with their content mgmt system) where a correct workstation time isn't necessary.
If someone can't figure out on their own if this applies to them or not, then they're an idiot.
Yeah, they won't notice the difference because they will still save the files on their C drive. At least that's been my experience.
I've been doing this at different companies for 7 years from Win 3.1 to Win2k. If they have files on C:, move them to S:, change their default save locations, tell them to save everything on S:. S: is their personal home directory.
Once their default locations are changed, they have to PURPOSELY save to c:. If you've informed them in writing, AND you've made these default changes, any lost files due to workstation issues is entirely the fault of the user. They can bitch an moan all they want, but if you lay it all out for them, there's nothing that can touch you.
You can say, "Hey, I did this, this and told them that. Their workstation is configured to save on the server, and that user decided not to. There isn't anything more that can be done, they need to change their habits."
If need be, include the S: drive notification with the information you give new users (passwords/email addr/etc). Make it a template, standard form, whatever. Make SURE they know saving on C is nothing less than reckless.
I didn't say they listened, you have to tell them to cover your butt. ;) That's why I also said to change their default paths too, that double covers your butt, because now the users have to purposely save somewhere else.
And you didn't fix it? That's just bad networking.
MAP ROOT S:=SERVER/Volume:USERS/$USERNAME
Tell the users to save ALL files on S:\. Now set your office prefs default directory to S:, and 99% of the time the user won't even know the difference.
IMHO, in a Windows environment, MAP ROOT is a PITA. :P
But what are you using Windows as a file server for? Ahh, you're paid hourly
No no.. Why would you set the server clock back? It's not the timestamps on the files that Office is reading, it's the PC's clock. When I write from a PC with a date of 01-01-01, to a server with today's date, the file created/modified will have todays date on it.
So you can change the workstations, and not affect your file's timestamps.
Do you have a central fileserver? Granted I'm a Novell guy, but doesn't the SERVER time stamp the files?
The time-stamp shouldn't be an issue, but then again, I'm a Netware guy and that's how Netware works..
It's a logical assumption that she will bring her DoubleClick experience to the 'Homeland Security' table. Instead of having guys sitting around trying to figure out how to track/spy on criminals, and not thinking about how it might affect the average joe, there's now somebody there to essentailly speak for the privacy advocates before privacy altering laws are drafted.
I don't suppose this will help me buy from them then..
Or better:
How do you respond to those who say you merely stumbled onto something (the whistle) that did something that was already known by EVERYONE (2600hz tones which was published in AT&T Manuals in PUBLIC Libraries), and exploited it for personal gain (free phone calls/publicity)?
It IS possible to be TOO anal.
You win some, and you lose some. Haven't you ever played Othello?
If you don't lose some, you'll get labeled as a fanatic, and you won't win ANYTHING from that point on. Like I've said before, the language is constantly changing. It's probably the only thing that's truly democratic.
The technical definition of broadband is going the way of the technical definition of 'hacker'.
God damn protesters spending all the other New Yorker's tax dollars again...
No kidding. This thing is being reported as the kiss of death. This is the first time I've seen ANYTHING like the following in ANY news report:
Around two-thirds of people diagnosed with SARS in Singapore have recovered.
I wish someone would have said that earlier. It's the last line in the linked article, and it almost seems like an afterthought.
Why is it just like the media to never say "Oh, yeah, and people really ARE surviving this disease."
I think people are thinking it's paid yearly, on a 3 year contract.
In any case, IMHO, this only applies to companies that aren't going downhill. Any decently large company will have a their own lawyer, and already leverage that person to get out of contracts regularly. (I worked at a credit card processor that got out of quite a few contracts with just a phone call to the corp lawyer).
AND only if you re-release your application. If you keep it in house, you don't have to release anything.
Ignoring the first sentence, which is nothing more than drivel, I don't personally have a problem with you replacing 'stupid law' or 'fat person' with 'american-style'. Could you use that in a sentence, so I can recognize it in the future? That almost seems too broad a replacement to be anything more than more drivel.
I live in the fattest state in the Union (Oh damn, I offended all the southerners now), you can call us fat/cheeseheads/whatever. I personally don't have a problem with that, and that's direct name-calling.
There was this thing I learned a LONG time ago.. Hmm, how did that go? Oh, yeah:
"Stick and Stones may break my bones.."