It can't hurt. If the spammers can be found in the US, it will give the FTC somebody to (hopefully) go after. If they're also international, it will at least give the FTC the clue that spam isn't just a US problem.
You obviously have never designed or even remotely seen a well-designed network. In the ideal world, everything has its own box.
Given that there is no such thing as a "well-designed network", only networks that perform the duties required of them, I really don't think you should bray.
Obviously, "what you interview for" is going to depend on the position you're trying to fulfill. A systems programmer needs a different skill set then a web "programmer".
This may sound like a radical idea, but the interview isn't for you, it's for the people the new employee is going to work with. So, try this:
Take potential employee. Give them access bade for area they would work in. Take them down "to show them around". Manage to "lose them" for an hour or two. Come back, thank them, etc. Interview everybody else.
But here's the kicker - the next time you run Quicken it re-enables this "background downloading" again! If you remove this DLL from the Windows registry, Quicken adds it again the next time you run it.
Don't remove the registry keys, change them to run from a drive that doesn't exist on your system, or change the extension to "c:\quickenw\foobar.dll.donotrun" or something.
You can also get something like the tiny little fireall, and block access based on PID information.
A jpeg viewer does nothing more then read data, manipulate it, and send it to the video subsystem.
DeCSS does nothing more then read data, manipulate it, and send it to the video subsystem.
Is it legal to use a jpeg viewer against the White House? Yes.
Is it legal to use a jpeg viewer against top-secret, confidential documents help by the CIA? No.
If I purchase a DVD, I should be able to do anything I want to with it; decode it, burn it, watch it, flush it down the toilet, give it (and any copies) to a retirement home, you name it.
It's not that you can't copy it. Track 0 of a DVD contains the encryption keys used in the player(s). The various manufacturers of DVD-R disks pre-burn track 0 with all zeros so you can't write the keys onto the copied disk.
This isn't a zero sum game. There isn't just one winner and everyone else is a loser.
As you alluded to above, "this" should be a win-win-win-win situation. If Linux gains enough ground on the desktop that MS actually improves (as opposed to adding new features) their products, the people who still use MS products win, and the people who write Linux products will be given more impetus to make their products better. This should drive Apple to make their products betterm yaddah, yaddah, yaddah
1) A manual for whatever hardware you're going to be programming on.
2) A manual for whatever OS you're going to be programming on. DOS is not CP/M is not MP/M is not Solaris is not HP-UX is not AIX is not Red Hat Linux is not Debian Linux.
3) Anything (preferably put out by the company you're working for) on their programming standards. FOLLOW THEM. If the company you're working for doesn't have standards, find several, and figure out what will work best, and then FORCE THEM TO BE A STANDARD.
4) Anything (preferably put out by the company you're working for) on documentation standards. FOLLOW THEM. If the company doesn't have documentation standards, find several, figure out what will work best for your project, and then FOLLOW THEM.
Personally, I would put good, consistant documentation as priority #1 for any programmer. The rest of it you can beg, borrow, steal, or fake.
More then likely, the consoles are donated. The schools get some free equipment (if it breaks, that's what the EE classes are for), the company gets some free publicity, and if everything works out, the kids will be buying the pc version so they can do "extra homework" without their parents complaining too much.
Sadely, the first person who will fail to back up their information will be a VP or a sibling of the boss, who can't be fired.
You cannot be "given" the ability to ensure that people back things up, all you can do is ensure that your file servers are backed up & restorable. Users must be responsible for their own data. If they don't back it up, and it gets destroyed, see if they can fire the idiot.
The easiest, quickest way I can think of to start is in a cooking class. The ingredients are your inputs, the receipie is your program, the oven is your computer, and the cookies are your output.
From there it's all all powdered sugar and souffles.
1) The quote is "a bear to code up". It says nothing about complexity, difficulty, the bills I need to pay tomorrow, or the fact that there is a tiny man in boots, jeans, a light brown shirt, and an orange hat sitting on the shelf of my desk.
2) I can't even spell it, much less pronounce it, but I heave heard of them, and can usually understand what most of them do after some study.
3) For any non-trivial program 'foo', there is point of diminishing returns, 'bar', where further optimization is not a cost-saving measure. Can I have my MBA now?
You're lucky. I could work at least 150% better if I didn't have to hear every single conversation that every single person was having with everybody on the phone, in person, over the cubicle wall, on the cell phone, by telepathy, etc.
Yes, having the systems geek where I just have him conference me in by using the speakerphone does have advantages *at times*, but not all the time.
(Writing virii is illegal, unethical, extremely hard for companies to do secretly, etc).
So is selling crack, that didn't stop the US Government.
As for the rest, the code itself has infection length of 2132 bytes according to symantec, so it couldn't have been that much of a bear to code up, just a lot of knowledge.
I realize you were probably being cynical up there, but of course they didn't give any infection vector information.
Why? Because all you need to do is "buy our product, and your system will be fully-protected against this virus, plaque, unexpected crashes (it's not a windows box, stupid salesrep!), and will also prevent power failures in california!".
Because the "jam buffers" are initialized by the flash eprom *in the clear*, it is possible to initialize them to a faulty state, which causes the boot sequence to abort, and you can then run anything you can put into the eprom.
Slashdot Mirror
It can't hurt. If the spammers can be found in the US, it will give the FTC somebody to (hopefully) go after. If they're also international, it will at least give the FTC the clue that spam isn't just a US problem.
cscx spake:
Given that there is no such thing as a "well-designed network", only networks that perform the duties required of them, I really don't think you should bray.
The Hamma-mamma-jammer wrote:
Your doctor has several ways of making sure you're "full" nowadays.
Obviously, "what you interview for" is going to depend on the position you're trying to fulfill. A systems programmer needs a different skill set then a web "programmer".
This may sound like a radical idea, but the interview isn't for you, it's for the people the new employee is going to work with. So, try this:
Take potential employee.
Give them access bade for area they would work in.
Take them down "to show them around".
Manage to "lose them" for an hour or two.
Come back, thank them, etc.
Interview everybody else.
To blockquote the parent:
Don't remove the registry keys, change them to run from a drive that doesn't exist on your system, or change the extension to "c:\quickenw\foobar.dll.donotrun" or something.
You can also get something like the tiny little fireall, and block access based on PID information.
A jpeg viewer does nothing more then read data, manipulate it, and send it to the video subsystem.
DeCSS does nothing more then read data, manipulate it, and send it to the video subsystem.
Is it legal to use a jpeg viewer against the White House? Yes.
Is it legal to use a jpeg viewer against top-secret, confidential documents help by the CIA? No.
If I purchase a DVD, I should be able to do anything I want to with it; decode it, burn it, watch it, flush it down the toilet, give it (and any copies) to a retirement home, you name it.
It's not that you can't copy it. Track 0 of a DVD contains the encryption keys used in the player(s). The various manufacturers of DVD-R disks pre-burn track 0 with all zeros so you can't write the keys onto the copied disk.
As the wise sage saith forsooth:
As you alluded to above, "this" should be a win-win-win-win situation. If Linux gains enough ground on the desktop that MS actually improves (as opposed to adding new features) their products, the people who still use MS products win, and the people who write Linux products will be given more impetus to make their products better. This should drive Apple to make their products betterm yaddah, yaddah, yaddah
I think this situation is what the LGPL is designed to cover.
95% of the world will never approach being the latter part of the previous sentence.
Um, no. The major reason why software sucks:
People don't know what they want.
The secondary reason why software sucks:
The "marketing" department.
Put the two together and you get the "office paperclip".
1) A manual for whatever hardware you're going to be programming on.
2) A manual for whatever OS you're going to be programming on. DOS is not CP/M is not MP/M is not Solaris is not HP-UX is not AIX is not Red Hat Linux is not Debian Linux.
3) Anything (preferably put out by the company you're working for) on their programming standards. FOLLOW THEM. If the company you're working for doesn't have standards, find several, and figure out what will work best, and then FORCE THEM TO BE A STANDARD.
4) Anything (preferably put out by the company you're working for) on documentation standards. FOLLOW THEM. If the company doesn't have documentation standards, find several, figure out what will work best for your project, and then FOLLOW THEM.
Personally, I would put good, consistant documentation as priority #1 for any programmer. The rest of it you can beg, borrow, steal, or fake.
I wonder if I could get my insurance company to pony up for one of these as therapy for me.
(As far as dancing goes, give me a waltz, or give me death!)
More then likely, the consoles are donated. The schools get some free equipment (if it breaks, that's what the EE classes are for), the company gets some free publicity, and if everything works out, the kids will be buying the pc version so they can do "extra homework" without their parents complaining too much.
In other words, microsoft is going to stay rich by turning "open .net" into "mostly-open, provided you can't beat us at, .net".
Sadely, the first person who will fail to back up their information will be a VP or a sibling of the boss, who can't be fired.
You cannot be "given" the ability to ensure that people back things up, all you can do is ensure that your file servers are backed up & restorable. Users must be responsible for their own data. If they don't back it up, and it gets destroyed, see if they can fire the idiot.
Only if you want to remove the user's freedom to install they way they want, build the way the want, put whatever files wherever they want, etc.
"With great power comes great responsbility."
The easiest, quickest way I can think of to start is in a cooking class. The ingredients are your inputs, the receipie is your program, the oven is your computer, and the cookies are your output.
From there it's all all powdered sugar and souffles.
1) The quote is "a bear to code up". It says nothing about complexity, difficulty, the bills I need to pay tomorrow, or the fact that there is a tiny man in boots, jeans, a light brown shirt, and an orange hat sitting on the shelf of my desk.
2) I can't even spell it, much less pronounce it, but I heave heard of them, and can usually understand what most of them do after some study.
3) For any non-trivial program 'foo', there is point of diminishing returns, 'bar', where further optimization is not a cost-saving measure. Can I have my MBA now?
You're lucky. I could work at least 150% better if I didn't have to hear every single conversation that every single person was having with everybody on the phone, in person, over the cubicle wall, on the cell phone, by telepathy, etc.
Yes, having the systems geek where I just have him conference me in by using the speakerphone does have advantages *at times*, but not all the time.
Ok, I guess folks haven't gotten the joke yet, but Sun is starting to do the exact same thing IBM did back in the 60's.
Maybe the Sun machines have more then 80x24 amber
7-character ASCII display, but the principle is the
same.
(Writing virii is illegal, unethical, extremely hard for companies to do secretly, etc). So is selling crack, that didn't stop the US Government. As for the rest, the code itself has infection length of 2132 bytes according to symantec, so it couldn't have been that much of a bear to code up, just a lot of knowledge.
I realize you were probably being cynical up there, but of course they didn't give any infection vector information.
Why? Because all you need to do is "buy our product, and your system will be fully-protected against this virus, plaque, unexpected crashes (it's not a windows box, stupid salesrep!), and will also prevent power failures in california!".
Because the "jam buffers" are initialized by the flash eprom *in the clear*, it is possible to initialize them to a faulty state, which causes the boot sequence to abort, and you can then run anything you can put into the eprom.
Should we start taking bets as to when the "xbox update" web site and service packs start coming out?