They know it's carried in the brain and tissue of the spinal cord. If you don't cut into the brain or spinal cord when butchering the animals, you have nothing to worry about. You can handle all the meat from the animals that you want with no effects to you at all.
So how does it spread, then? The elks rub their brain stems together in the throws of passion?
Damn right! For a geek a strike would mean not touching the computer for an extended period of time. Can you imagine abstaining from games and pr0n for that long? A few days and we'd be ready for a pay cut...
This will take at least 15 years. People don't buy new washing machines all that often.
All present and accounted for -- always.
This will be in mobile phones within 5 years.
Walk now, pay later.
Probably unfeasible as described. More likely you will authorize payment for the item before putting it in the bag. The receiver at the entryway will only check that you don't leave with any unpaid items. 10 years is about right, I wager.
Prime time is your time
Not very adventurous there. 5 more years.
Finally, we can talk to our computers
People curse them every day, so this is already reality.;-)
I doubt true voice control will be there in 10 years either, unless there is a major break through in AI technology. Before that, we will be limited to simple voice keyed activation.
Relying on link layer security is stupid anyway. What you need to do, as a network admin, is to view wireless access as any other access mechanism that is not physically in your control. Use end-to-end IPSEC or VPN to secure it.
These days all serious software projects are written by a group of people. In some ways, a software project is like a marriage. If the people are compatible, the team grows together into a well oiled machine and produces some great software. That can be a very rewarding experience. The opposite can happen too; the team can fall apart because of slackers or strong willed individuals with serious differences of opinion and no ability to compromise.
I think it's important that the team consist of a variety of people with different talents and insights. The different views enrich the project. While everyone should have a say in where the project is going, someone must also be in charge and be able to make the final decision after the ideas are on the table.
In real life projects sometimes get cancelled for business reasons that have nothing to do with how the project is going. The many cancelled commercial adventure games are a prime example: no market for it. That is something you, as a professional, will have to learn to live with. If you have been working on a project for two tears, having it cancelled can suck big time. But, all things considerd, it is still only a job.
I always have great plans to make some sweet ass game. As a programming student i get myself way in over my head and end up scratching it long before it becomes playable. Typical problem or not organizing and shooting too high.
The person who modded you a troll must be on a fantasy adventure, or something.
I have to say that I have my share of aborted adventure games in the closet. In my experience, every piece of software consists of two main components: a) the neat bit; and b) the boring bit. I usually wrote the neat bit first (that's the game engine), and then got started on the boring bit (the game itself). As it happens, something else with a neat bit in it usually came along before I managed to finish the project.
It makes me think that i dont wanna do coding as a living becuase if i actually did make progress and someone cancled my work it would not be very fun at all.
Writing software for a living can sometimes be like that. In my experience, there are two kinds of jobs: a) neat jobs; and b) boring jobs. Just make sure you are skilled enough to get a neat job. You want to be the one who gets to write the neat bits.
Well said. The tradition in the software industry is that you get paid for listening to stupid customers and for writing documentation. It's customary.
They spend hours and months poring over the code, providing traceability and working on correctness because if they fuck up, people die.
I wonder if people expend the same effort on the embedded software that controls traffic lights. Seems to me that borking traffic lights are a lot more likely to kill large numbers of people.
Talk about left hand not talking to the right hand.
These things happen in every large company. People disagree. Usually the differences are resolved in-house.
The BBC is also carrying the story.
However, this has got to be a big embarrasment for Microsoft, unless a miracle has happened and they have truly realized the futility of DRM and are starting to turn the ship around.
Unless these guys cleared the article with the top management they're going to be in big trouble.
I remember any number of studies reporting that in univeristy classes, men talked far more and were more likely to interrupt, not just each other but more so female students, and also female instructors.
This is a social safeguard often employed by men of above average intelligence when confronted by breasts. The babbling is a desperate attempt to keep the higher cognitive functions going while the blood is rushing the other way. Even so, we often fail, as witnessed by the occasional glazed eyes and hanging yaw.
Very true. As it happens, there are plenty of engineers who are quite willing to work on things that Don't Really Matter (DRM) as long as someone is willing to pay Really Indecent Amounts of Acmids (RIAA) for it. It puts bread on the table. Telling them what they don't want to hear doesn't.
This poor little alien is trapped. It has chosen the most innocuous, uninteresting, and non-threatening shape it can imagine, that of an indigenous life form with the appearance of box emitting a peaceful glow.
And yet the threatening native steadfastly refuses to wander away, instead choosing to squat and stare at it in ominous silence, fingering the obvious weapon tucked under its left upper appendage and no doubt mentally rehearsing several of its favorite ways of committing murder, each more violent and gruesome than the rest.
The little alien is gazing back in desperation, afraid to make the smallest move.
You can tell the difference between a developer who gets it and one who doesn't because the developer who doesn't get it is content to build a custom system using closed source components that they cannot understand, let alone keep secure.
when he goes on to say that
High level languages are usually more secure than C/C++...
High level languages are built on layers and layers of things written by other people, things that you know nothing about. If you use C or assemlber, you're much more likely to be in control of the security of your code.
I guess the comment about C/C++ is aimed at coders who suck more than average; they're certainly better of using code written by other people.
Those running slashdot are more devoted to trying to find flaws in their 'enemy' than promoting the virtues of their cause.
'tis true, for we may look like penguins but we have the hearts of warriors.
I propose that this site state its purpose: does it exist to provide news, or is it merely attempting to blast Microsoft in a selfish, childish, jealous manner?
'tis both, a shrine for wisdom and quiet reflection, and oftentimes a site of banter and merriment.
Slashdot Mirror
They know it's carried in the brain and tissue of the spinal cord. If you don't cut into the brain or spinal cord when butchering the animals, you have nothing to worry about. You can handle all the meat from the animals that you want with no effects to you at all.
So how does it spread, then? The elks rub their brain stems together in the throws of passion?
What a geek would one be without an own computer ?
It kind of defeats the purpose of the strike if you go and do it at home for free, don't you think?
HELL NO.
Damn right! For a geek a strike would mean not touching the computer for an extended period of time. Can you imagine abstaining from games and pr0n for that long? A few days and we'd be ready for a pay cut...
The Internet is everywhere -- and nowhere.
;-)
This will take at least 15 years. People don't buy new washing machines all that often.
All present and accounted for -- always.
This will be in mobile phones within 5 years.
Walk now, pay later.
Probably unfeasible as described. More likely you will authorize payment for the item before putting it in the bag. The receiver at the entryway will only check that you don't leave with any unpaid items. 10 years is about right, I wager.
Prime time is your time
Not very adventurous there. 5 more years.
Finally, we can talk to our computers
People curse them every day, so this is already reality.
I doubt true voice control will be there in 10 years either, unless there is a major break through in AI technology. Before that, we will be limited to simple voice keyed activation.
Nah, no need throwing poor Bill into a volcano. Just follow the great example provided by Isildur on how to handle problems like these. >:)
Isildur? You mean the chap who defeated Sauron at Barad-dûr and cut off his finger to get... Oh!
Although it is encrypted, it is most likely that within two years, it will be possible to crack this.
Cables are securer.
With a wire cutter I can crack a cable today. Cables are not more secure. They are just slightly less accessible.
Relying on link layer security is stupid anyway. What you need to do, as a network admin, is to view wireless access as any other access mechanism that is not physically in your control. Use end-to-end IPSEC or VPN to secure it.
We must find Bill's cock ring and toss it into a volcano! And, mind you, I don't care if Bill is still wearing it when we do that.
These days all serious software projects are written by a group of people. In some ways, a software project is like a marriage. If the people are compatible, the team grows together into a well oiled machine and produces some great software. That can be a very rewarding experience. The opposite can happen too; the team can fall apart because of slackers or strong willed individuals with serious differences of opinion and no ability to compromise.
I think it's important that the team consist of a variety of people with different talents and insights. The different views enrich the project. While everyone should have a say in where the project is going, someone must also be in charge and be able to make the final decision after the ideas are on the table.
In real life projects sometimes get cancelled for business reasons that have nothing to do with how the project is going. The many cancelled commercial adventure games are a prime example: no market for it. That is something you, as a professional, will have to learn to live with. If you have been working on a project for two tears, having it cancelled can suck big time. But, all things considerd, it is still only a job.
I always have great plans to make some sweet ass game. As a programming student i get myself way in over my head and end up scratching it long before it becomes playable. Typical problem or not organizing and shooting too high.
The person who modded you a troll must be on a fantasy adventure, or something.
I have to say that I have my share of aborted adventure games in the closet. In my experience, every piece of software consists of two main components: a) the neat bit; and b) the boring bit. I usually wrote the neat bit first (that's the game engine), and then got started on the boring bit (the game itself). As it happens, something else with a neat bit in it usually came along before I managed to finish the project.
It makes me think that i dont wanna do coding as a living becuase if i actually did make progress and someone cancled my work it would not be very fun at all.
Writing software for a living can sometimes be like that. In my experience, there are two kinds of jobs: a) neat jobs; and b) boring jobs. Just make sure you are skilled enough to get a neat job. You want to be the one who gets to write the neat bits.
Well said. The tradition in the software industry is that you get paid for listening to stupid customers and for writing documentation. It's customary.
They spend hours and months poring over the code, providing traceability and working on correctness because if they fuck up, people die.
I wonder if people expend the same effort on the embedded software that controls traffic lights. Seems to me that borking traffic lights are a lot more likely to kill large numbers of people.
Talk about left hand not talking to the right hand.
These things happen in every large company. People disagree. Usually the differences are resolved in-house.
The BBC is also carrying the story.
However, this has got to be a big embarrasment for Microsoft, unless a miracle has happened and they have truly realized the futility of DRM and are starting to turn the ship around.
Unless these guys cleared the article with the top management they're going to be in big trouble.
You would not believe the trouble I had looking up the Trojan War.
That's a story about men entering a horse.
I remember any number of studies reporting that in univeristy classes, men talked far more and were more likely to interrupt, not just each other but more so female students, and also female instructors.
This is a social safeguard often employed by men of above average intelligence when confronted by breasts. The babbling is a desperate attempt to keep the higher cognitive functions going while the blood is rushing the other way. Even so, we often fail, as witnessed by the occasional glazed eyes and hanging yaw.
We're not talking about Pamela Anderson, are we?
Does it also grope nurses' buts and listen to Chopin (or is that Choppin' ?) while performing surgery?
Very true. As it happens, there are plenty of engineers who are quite willing to work on things that Don't Really Matter (DRM) as long as someone is willing to pay Really Indecent Amounts of Acmids (RIAA) for it. It puts bread on the table. Telling them what they don't want to hear doesn't.
Alternate Explanation #3:
This poor little alien is trapped. It has chosen the most innocuous, uninteresting, and non-threatening shape it can imagine, that of an indigenous life form with the appearance of box emitting a peaceful glow.
And yet the threatening native steadfastly refuses to wander away, instead choosing to squat and stare at it in ominous silence, fingering the obvious weapon tucked under its left upper appendage and no doubt mentally rehearsing several of its favorite ways of committing murder, each more violent and gruesome than the rest.
The little alien is gazing back in desperation, afraid to make the smallest move.
Really quite sad.
Asking Slashdotters.. To go outside.. I don't know if this is an insult or a mistake.
So that's what this is all about? All this talk about a shower was making me nervous.
Pretty soon, they'll have everything, then they'll go after the dildo market(assuming in the future their will be some mini-os in dildos :)
Where do you want to come today?
I've never met a civilized computer professional.
The matted hair and the reek of unwashed skin is a dead giveaway. That, and the ferocious growl if you try to touch his things.
He's contradicting himself here:
...
You can tell the difference between a developer who gets it and one who doesn't because the developer who doesn't get it is content to build a custom system using closed source components that they cannot understand, let alone keep secure.
when he goes on to say that
High level languages are usually more secure than C/C++
High level languages are built on layers and layers of things written by other people, things that you know nothing about. If you use C or assemlber, you're much more likely to be in control of the security of your code.
I guess the comment about C/C++ is aimed at coders who suck more than average; they're certainly better of using code written by other people.
User 1 "Did my computer just crash?"
User 2 "Couldn't tell, happened to fast."
Light travels less than 10 centimeters in one clock cycle. Of course you didn't see it crash.
Those running slashdot are more devoted to trying to find flaws in their 'enemy' than promoting the virtues of their cause.
'tis true, for we may look like penguins but we have the hearts of warriors.
I propose that this site state its purpose: does it exist to provide news, or is it merely attempting to blast Microsoft in a selfish, childish, jealous manner?
'tis both, a shrine for wisdom and quiet reflection, and oftentimes a site of banter and merriment.