Never hire anyone, of course, so you never pay for salaries, FICA, health care, vacation, paycheck distribution...
Next step: require that the interviewee simply telecommute in with their own computer. Now you don't even have to worry about covering transportation costs, desk space, office supplies...
Genius, I tell ya. Evil genius, of course. But still.
The SDK not being ready doesn't really rationalize charging money for access. If I'm beta-testing their SDK, they should pay me.
But of course, the answer to "why charge money?" is, invariably, "because they can". Everyone wants to start coding ASAP so they can get their app into the marketplace before their competitors do. So they'll pony up the dough.
To ensure that important information springs to the foreground, comments should exist primarily to document something which is not obvious from the code itself: requirements justifying the code, rationale for a particular approach, explanation of complex logic, and the occasional TODOs and FIXMEs.
For example, a method on Person called setName() does not need a comment "This sets the name of the person."
Additionally, there is no need to pepper "// end if" and "// end while" and "// end method" comments all over the code on every right curly-brace. IDEs that automatically comment are pure evil.
Wow, that's an interesting perspective. For any tl;dr folks out there, the summary boils it down nicely:
* Identification: who are you? * Authentication: how can you prove it? * Authorization: what can you do?
However, if biometrics are used to back up the assertion of the username in a supplied username/password combo (in 2-factor authentication), they feel a little more like authentication than identification to me. But I see your point, and mod you Informative with my imaginary mod points.
I think we're on the same page, but talking about two entirely different things. I agree that in James Bond scenarios, biometrics might pose a risk to the owner, but I'm talking about why you don't use biometrics by themselves. The article starts with this:
If your password management system is to use your "fingerprint as your master password," and if your laptop uses UPEK software, then you'll not be happy to know your Windows password is not secure and instead is easily crackable.
Absolutely. Using biometrics as a funny sort of password -- without any other authentication methods to supplement it -- is a bad idea, even if no one is lurking behind the bushes of your house waiting to brain you with a crescent wrench and steal your index fingers.
1. Something you know (such as a passphrase), plus... 2. Something you own (such as the ID number from a FOB which rotates IDs every minute), plus... 3. Something you are (biometrics).
You don't use biometrics *instead* of the passphrase or FOB; you use it to augment the effectiveness of those techniques.
So the choice is, sit down for nine hours each day or else get a standup desk to the tune of 500 bucks or more.
Sorry, but what about just standing up to stretch and walk around every few minutes? I hack code at a traditional desk, but I'm certainly not chained to my chair. Walk around, go to the water cooler, talk to your peers, go outside for lunch. Even if you had a stand-up desk you should still move around a little.
"The thing about a black hole - it's main distinguishing feature - is it's black. And the thing about space, the color of space, your basic space color - is it's black. So how are you supposed to see them?"
HP LaserJet 5MP; I've had it for years and only ever needed one minor repair (when the feeder broke). Printouts are crisp and professional looking, and laser toner doesn't smudge or blotch if you accidentally spill a little tea on it, unlike ink.
I'll grant that if you're printing out photos, a high-end ink jet printer is favored by artists for a good reason -- but those are the top-quality ones with 7 or 9 separate cartridges. Laser printouts on photo paper just don't look right to me.
...to follow suit, and wean consumers off the "cheap inkjet printer" crack pipe. I have a full-color (4 cartridge) laser printer that I virtually never need to change the toner on, and when I do it's invariably the black cartridge. My significant other, meanwhile, goes through inkjet cartridges like I go through socks. And I *love* socks.
You're basically right: as I understand it, in America around either pre-Colonial or Colonial times, you were expected to keep your windows open (or at least unshuttered and with curtains open) so that neighbors could peek in and make sure you weren't up to anything ungodly. Failure to do so would have been regarded as suspicious.
But there was still shame in those days, despite the expected lack of privacy. You could easily be shamed for what you did right out in the open. The concepts of shame and privacy have existed since people started wearing pants.
Add me to the list of people who could not figure out why Amarok's author made such ill-advised changes in 2.x. The UI went from being completely intuitive to maddeningly confusing, and (well, for me at least) iPod synching broke horribly, which effectively forced me to jettison the thing in favor of gtkpod.
At some point, an author needs to go back to the community and say "I'm sorry. I've heard the complaints, and it's pretty clear that my last version, although well-intended, was a complete mistake. I'm going to re-fork the last popular version and try to make something that looks basically the same and works better under the hood."
Slashdot Mirror
Well played, sir, well played.
There will now be a slight pause while we all google "cache line"...
...perpetual "working" interviews.
Never hire anyone, of course, so you never pay for salaries, FICA, health care, vacation, paycheck distribution...
Next step: require that the interviewee simply telecommute in with their own computer. Now you don't even have to worry about covering transportation costs, desk space, office supplies...
Genius, I tell ya. Evil genius, of course. But still.
The SDK not being ready doesn't really rationalize charging money for access. If I'm beta-testing their SDK, they should pay me.
But of course, the answer to "why charge money?" is, invariably, "because they can". Everyone wants to start coding ASAP so they can get their app into the marketplace before their competitors do. So they'll pony up the dough.
This "story" is just one big ass troll isn't it?
Nah, you're thinking of "Shrek".
To ensure that important information springs to the foreground, comments should exist primarily to document something which is not obvious from the code itself: requirements justifying the code, rationale for a particular approach, explanation of complex logic, and the occasional TODOs and FIXMEs.
For example, a method on Person called setName() does not need a comment "This sets the name of the person."
Additionally, there is no need to pepper "// end if" and "// end while" and "// end method" comments all over the code on every right curly-brace. IDEs that automatically comment are pure evil.
I can create a laser pulse lasting ZERO attoseconds. There, just did it. There, just did it again. Top *that*, UCF!
Wow, that's an interesting perspective. For any tl;dr folks out there, the summary boils it down nicely:
* Identification: who are you?
* Authentication: how can you prove it?
* Authorization: what can you do?
However, if biometrics are used to back up the assertion of the username in a supplied username/password combo (in 2-factor authentication), they feel a little more like authentication than identification to me. But I see your point, and mod you Informative with my imaginary mod points.
I think we're on the same page, but talking about two entirely different things. I agree that in James Bond scenarios, biometrics might pose a risk to the owner, but I'm talking about why you don't use biometrics by themselves. The article starts with this:
Absolutely. Using biometrics as a funny sort of password -- without any other authentication methods to supplement it -- is a bad idea, even if no one is lurking behind the bushes of your house waiting to brain you with a crescent wrench and steal your index fingers.
...can (3.0 + 0.6) be less than 2.
A treadmill desk would make me feel way too much like I'm a hamster running to earn my daily ration of kibble.
(I know that's what my job really amounts too... I just don't want the analogy to be quite so... obvious...)
The best authentication has three components:
1. Something you know (such as a passphrase), plus...
2. Something you own (such as the ID number from a FOB which rotates IDs every minute), plus...
3. Something you are (biometrics).
You don't use biometrics *instead* of the passphrase or FOB; you use it to augment the effectiveness of those techniques.
You said:
Sorry, but what about just standing up to stretch and walk around every few minutes? I hack code at a traditional desk, but I'm certainly not chained to my chair. Walk around, go to the water cooler, talk to your peers, go outside for lunch. Even if you had a stand-up desk you should still move around a little.
...by such an obvious fake. We promise that in the future, the misleading ads won't be *nearly* as easy to debunk.
Try Readability:
http://readability.com/
Also available as a browser plug-in.
You are correct -- that's what I get for replying off the top of my head when I'm miles away from the printer. :-(
Sigh... are there no "Red Dwarf" fans around?
"The thing about a black hole - it's main distinguishing feature - is it's black. And the thing about space, the color of space, your basic space color - is it's black. So how are you supposed to see them?"
HP LaserJet 5MP; I've had it for years and only ever needed one minor repair (when the feeder broke). Printouts are crisp and professional looking, and laser toner doesn't smudge or blotch if you accidentally spill a little tea on it, unlike ink.
I'll grant that if you're printing out photos, a high-end ink jet printer is favored by artists for a good reason -- but those are the top-quality ones with 7 or 9 separate cartridges. Laser printouts on photo paper just don't look right to me.
...to follow suit, and wean consumers off the "cheap inkjet printer" crack pipe. I have a full-color (4 cartridge) laser printer that I virtually never need to change the toner on, and when I do it's invariably the black cartridge. My significant other, meanwhile, goes through inkjet cartridges like I go through socks. And I *love* socks.
...the headline is all that anyone is going to read (here and elsewhere). And it's not good PR for Google.
You're basically right: as I understand it, in America around either pre-Colonial or Colonial times, you were expected to keep your windows open (or at least unshuttered and with curtains open) so that neighbors could peek in and make sure you weren't up to anything ungodly. Failure to do so would have been regarded as suspicious.
But there was still shame in those days, despite the expected lack of privacy. You could easily be shamed for what you did right out in the open. The concepts of shame and privacy have existed since people started wearing pants.
I hear you bro. I'm still having to hunt and find the stop/play/shuffle buttons
Wow, I was afraid I was the only one. :-)
BTW, I installed Clementine... it's definitely worth a try if you loved Amarok 1.x.
...people voluntarily reveal private information like the location of their homes, what they had for breakfast, favorite sexual positions, etc.
Add me to the list of people who could not figure out why Amarok's author made such ill-advised changes in 2.x. The UI went from being completely intuitive to maddeningly confusing, and (well, for me at least) iPod synching broke horribly, which effectively forced me to jettison the thing in favor of gtkpod.
At some point, an author needs to go back to the community and say "I'm sorry. I've heard the complaints, and it's pretty clear that my last version, although well-intended, was a complete mistake. I'm going to re-fork the last popular version and try to make something that looks basically the same and works better under the hood."