A friend's father, who is a computer nerd and retired electrician and flunked out of MIT in the mid 60s swears by the "zorch" theory, and has since I met him. He supports the notion that "zorch" is an onomatopoeia for the sound that a frying electrical component makes as it dies; with a soft "ch". The hard "k" is the fault of MIT sociolinguistics of the era, he explains.
And actually now that I think of it, if any of this has anything to do with the sociolinguistics of MIT at the area, someone should probably ask Chomsky where it came from. He probably knows for sure.
"but I think most of the great software engineers in the past were physicists and electrical engineers." --- which is, like good computer science, simply applied mathematics.
Every time one or more TSA employee screw up, such as letting some brainiac walk the wrong way through a checkpoint, every TSA employee on duty at that location is fired. This will work for three reasons:
1. fear is a good motivator for low salaried, low skill employees 2. fear is a good dilution agent for giant egos on low skill employees 3. its really easy to quickly hire a bunch more low salaried, low skill employees, especially in this economy (TM)
"Cutting 401k is the same as saying "we care about you SO little, that we hope you die hungry and cold in your old age.""
Having been in the unfortunate position of being forced to cut 401K contributions by asshole management, I can promise you that it's never got anything to do with them *just* not caring about their employees in their old age. It also has to do with trusting fully that the whole company will be Somebody Else's Problem inside 36 months, whether by bankruptcy or by acquisition.
Because I have this sort of experiential knowledge of the motivations of asshole management and executive layers, I make a point to never do business of any sort with any company that treats its employees badly. Without exception, every company that treats its employees badly has absolutely zero faith in every element in their product line and are interested only in lining their own pockets with cash.
1. with your palm face up, stick your middle finger as far as it will go into a dudette's vaginal canal 2. still with your palm face up, point back at yourself with your middle finger. Your middle finger should now be meeting resistance from the underside of the dudette's pubic bone. 3. move the tip of your finger around a little bit until you feel something a bit like fish gills.
That's what you're looking for.
If you're a dudette:
1. with your palm face down, stick your middle finger as far as it will go into your vaginal canal 2. still with your palm face down, curl your middle finger back towards your palm. Your middle finger should now be meeting resistance from the underside of your pubic bone. 3. move the tip of your finger around a little bit until you feel something a bit like fish gills.
That's what you're looking for.
These "scientists" evidently aren't having very good sex.
I have to step in and say something here. If at any point in the 90s or early oughts... even up to 2004, you'd considered dropping in the ability to do hot DB dumps without table locking, you would have very likely gotten bigger than Oracle. (Much as Linux has gotten bigger than Solaris). It was idiocy of you not to do so, in favor of... god only knows what.
And now frankly its too little, too late. MYSQL is pretty ok for a light-to-medium duty database, but you guys have had a couple of decades to really, *really* get it right, and you didn't.
If Oracle kills MySQL, the biggest pain in the arse will be moving things over to postgresql, which everyone should have done ten years ago in the first place.
I didnt say that android made all the same data available, I said they both cache the same things in comparable places. And yes, I did break open android for as long as it took to realize that you can't write for it in C or anything like it. And no, java isn't anything like it. (you'll probably think here that since they have similar syntax I don't know what I'm talking about, but I challenge you to think it through for five seconds)
If your programming is anything like your reasoning, it's become pretty clear why you've ultimately chosen java over C. (++/Obj)
It is a fact that "Little-Linux-Variation" (android) is precisely as insecure and for all the same reasons as "Little-BSD-Variation" (iphoneos). They both cache all the same things and in comparable places, and data in both is protected either by virtue of being in a binary database, or by virtue of POSIX style permissions. Apple does its best to scrub the malware out of the app store, and the open source community does its best to scrub the malware out of the android lexicon. Traditionally, both approaches have just about the same affect: the vast majority of binaries for both platforms are safe, but a few arent.
All of that said, I prefer the iphone. It's an aesthetic choice and has nothing to do with security or functionality, since they're both really pretty much the same logical device.
An EEG is not the same thing as a "brain scan". An EEG is an analog point to point system which is very good at "reading" the parts of the generalized electrical field that reaches the scalp from the brain. Using EEG output to control stuff is a fun sideline which is almost exactly as old as EEG technology itself.
It doesn't work very well, and it very probably never will. The variance in electrical activity in the brain between two people receiving the same sensory input is, in an average way, too great to be useful.
Once someone comes up with a way to shrink an MRI machine to the size of a quarter that you just stick to your forehead and talks bluetooth to all your devices, then we'll be ok.
I always tried to do this when I was programming. I took every project as an exercise in teaching; not only to pass down handy kung fu secrets that no one tells you in college, but also to hone my own teaching skills. If I can't explain what I'm doing so that it's interesting to a duck, then I need to be a better teacher./* Willfull recursion here. Note that nothing I say will likely ever be interesting to a duck, therefore I will always by my own measure come up short on the teaching skills, therefore I will always take every opportunity to sharpen what I have. Also, implicitly if I cannot explain what I've done in a way that *I* can understand, I probably shouldn't have done it at all. */
It's always heartwarming to see a Sysadmin ascend to the point where they begin to slowly realize that justification for their salary is going to have to involve some lying.
"They have NO RIGHT to tell me what I can or can't install their OS on."
Questionable at best. What is unquestionable is that they have absolutely no responsibility, legal or otherwise whatsoever, to continue supporting hardware that they do not use in the builds of their own systems.
Just as you have the unquestionable choice at this point to use an operating system which may be more suited to your needs.
Agreed. The attractive thing about this package is its small size and cost. Setting up a mail server for a small business suddenly means not having to hire an expensive hourly consultant (or worse, hire an expensive salaried administrator). It also enables the existence of small, cheap remote administration consoles in larger organizations which are tied to OS X server.
Wait... if you're rolling your own dice, why not use your eyeballs and temporal lobes to read the value?
The whole affair is just weird. Why would anyone plunk down thousands (tens of thousands?) for a "Microsoft Surface" to play D&D on, when they can get a used card table for ten bucks at a flea market?
Now, combine AD&D combat rules with dice and a bona fide MMORPG, throw THAT on the table and I'm sold.
Another big reason that people don't want to get off COBOL is because it's what the US Govt. is locked into for things like tax updates and computations. Anyone who's had the horrid experience of setting up or running a PeopleSoft Financial's installation knows all too painfully well about government tax updates and the COBOL they require.
Not that the COBOL itself was terrible to deal with. IMHO, it's an elegant, powerful language that doesn't get anywhere near the credit or respect it deserves.
Huh. You'd think that my original posit that pretty much anyone who would care in the first place knows all about Alan Turing-- and that that is a very large number of people, wouldn't have been met with such vehement denial.
It's almost like you people want things to complain about.
FWIW, two degrees away from the source:
A friend's father, who is a computer nerd and retired electrician and flunked out of MIT in the mid 60s swears by the "zorch" theory, and has since I met him. He supports the notion that "zorch" is an onomatopoeia for the sound that a frying electrical component makes as it dies; with a soft "ch". The hard "k" is the fault of MIT sociolinguistics of the era, he explains.
And actually now that I think of it, if any of this has anything to do with the sociolinguistics of MIT at the area, someone should probably ask Chomsky where it came from. He probably knows for sure.
Security did used to be very much about SYN packets and not much else. Hi, I used to build ISPs in the early 90s.
"but I think most of the great software engineers in the past were physicists and electrical engineers." --- which is, like good computer science, simply applied mathematics.
Every time one or more TSA employee screw up, such as letting some brainiac walk the wrong way through a checkpoint, every TSA employee on duty at that location is fired. This will work for three reasons:
1. fear is a good motivator for low salaried, low skill employees
2. fear is a good dilution agent for giant egos on low skill employees
3. its really easy to quickly hire a bunch more low salaried, low skill employees, especially in this economy (TM)
"Cutting 401k is the same as saying "we care about you SO little, that we hope you die hungry and cold in your old age.""
Having been in the unfortunate position of being forced to cut 401K contributions by asshole management, I can promise you that it's never got anything to do with them *just* not caring about their employees in their old age. It also has to do with trusting fully that the whole company will be Somebody Else's Problem inside 36 months, whether by bankruptcy or by acquisition.
Because I have this sort of experiential knowledge of the motivations of asshole management and executive layers, I make a point to never do business of any sort with any company that treats its employees badly. Without exception, every company that treats its employees badly has absolutely zero faith in every element in their product line and are interested only in lining their own pockets with cash.
If you're a dude:
1. with your palm face up, stick your middle finger as far as it will go into a dudette's vaginal canal
2. still with your palm face up, point back at yourself with your middle finger. Your middle finger should now be meeting resistance from the underside of the dudette's pubic bone.
3. move the tip of your finger around a little bit until you feel something a bit like fish gills.
That's what you're looking for.
If you're a dudette:
1. with your palm face down, stick your middle finger as far as it will go into your vaginal canal
2. still with your palm face down, curl your middle finger back towards your palm. Your middle finger should now be meeting resistance from the underside of your pubic bone.
3. move the tip of your finger around a little bit until you feel something a bit like fish gills.
That's what you're looking for.
These "scientists" evidently aren't having very good sex.
I have to step in and say something here. If at any point in the 90s or early oughts... even up to 2004, you'd considered dropping in the ability to do hot DB dumps without table locking, you would have very likely gotten bigger than Oracle. (Much as Linux has gotten bigger than Solaris). It was idiocy of you not to do so, in favor of... god only knows what.
And now frankly its too little, too late. MYSQL is pretty ok for a light-to-medium duty database, but you guys have had a couple of decades to really, *really* get it right, and you didn't.
If Oracle kills MySQL, the biggest pain in the arse will be moving things over to postgresql, which everyone should have done ten years ago in the first place.
I didnt say that android made all the same data available, I said they both cache the same things in comparable places. And yes, I did break open android for as long as it took to realize that you can't write for it in C or anything like it. And no, java isn't anything like it. (you'll probably think here that since they have similar syntax I don't know what I'm talking about, but I challenge you to think it through for five seconds)
If your programming is anything like your reasoning, it's become pretty clear why you've ultimately chosen java over C. (++/Obj)
It is a fact that "Little-Linux-Variation" (android) is precisely as insecure and for all the same reasons as "Little-BSD-Variation" (iphoneos). They both cache all the same things and in comparable places, and data in both is protected either by virtue of being in a binary database, or by virtue of POSIX style permissions. Apple does its best to scrub the malware out of the app store, and the open source community does its best to scrub the malware out of the android lexicon. Traditionally, both approaches have just about the same affect: the vast majority of binaries for both platforms are safe, but a few arent.
All of that said, I prefer the iphone. It's an aesthetic choice and has nothing to do with security or functionality, since they're both really pretty much the same logical device.
An EEG is not the same thing as a "brain scan". An EEG is an analog point to point system which is very good at "reading" the parts of the generalized electrical field that reaches the scalp from the brain. Using EEG output to control stuff is a fun sideline which is almost exactly as old as EEG technology itself.
It doesn't work very well, and it very probably never will. The variance in electrical activity in the brain between two people receiving the same sensory input is, in an average way, too great to be useful.
Once someone comes up with a way to shrink an MRI machine to the size of a quarter that you just stick to your forehead and talks bluetooth to all your devices, then we'll be ok.
Wow, if you saw a temper tantrum there, you really need to start taking your paxil again.
It is now.
I always tried to do this when I was programming. I took every project as an exercise in teaching; not only to pass down handy kung fu secrets that no one tells you in college, but also to hone my own teaching skills. If I can't explain what I'm doing so that it's interesting to a duck, then I need to be a better teacher. /* Willfull recursion here. Note that nothing I say will likely ever be interesting to a duck, therefore I will always by my own measure come up short on the teaching skills, therefore I will always take every opportunity to sharpen what I have. Also, implicitly if I cannot explain what I've done in a way that *I* can understand, I probably shouldn't have done it at all. */
Where does he keep the Truecrypt password?
It's always heartwarming to see a Sysadmin ascend to the point where they begin to slowly realize that justification for their salary is going to have to involve some lying.
I say "I'd rather pay nothing for bugs like this than $400 for all the same borkedness in Server 2008"
"They have NO RIGHT to tell me what I can or can't install their OS on."
Questionable at best. What is unquestionable is that they have absolutely no responsibility, legal or otherwise whatsoever, to continue supporting hardware that they do not use in the builds of their own systems.
Just as you have the unquestionable choice at this point to use an operating system which may be more suited to your needs.
Agreed. The attractive thing about this package is its small size and cost. Setting up a mail server for a small business suddenly means not having to hire an expensive hourly consultant (or worse, hire an expensive salaried administrator). It also enables the existence of small, cheap remote administration consoles in larger organizations which are tied to OS X server.
Wait... if you're rolling your own dice, why not use your eyeballs and temporal lobes to read the value?
The whole affair is just weird. Why would anyone plunk down thousands (tens of thousands?) for a "Microsoft Surface" to play D&D on, when they can get a used card table for ten bucks at a flea market?
Now, combine AD&D combat rules with dice and a bona fide MMORPG, throw THAT on the table and I'm sold.
"says such complaints and criticisms about PulseAudio in some Internet forums are not really shared by the vast majority of technical people."
Yes, actually they are.
Another big reason that people don't want to get off COBOL is because it's what the US Govt. is locked into for things like tax updates and computations. Anyone who's had the horrid experience of setting up or running a PeopleSoft Financial's installation knows all too painfully well about government tax updates and the COBOL they require.
Not that the COBOL itself was terrible to deal with. IMHO, it's an elegant, powerful language that doesn't get anywhere near the credit or respect it deserves.
Hey I remember you.
Huh. You'd think that my original posit that pretty much anyone who would care in the first place knows all about Alan Turing-- and that that is a very large number of people, wouldn't have been met with such vehement denial.
It's almost like you people want things to complain about.
How young do you have to be these days to assume that no one's heard of Alan Turing or his brilliant contributions and persecution?
Dear Planet Earth:
I'm really sorry for all those whip-its I did in college.