You don't need requirements before you start coding
and later...
Quality doesn't matter
I say:
Dude.
XP is all about requirements and quality. You meet with the customer every day. You have regular meetings to evaluate progress. You write exhaustive unit tests. You perform daily integrations.
You havn't seen XP fail. What you saw wasn't XP. I don't know what it was.
My favorite pen was a green ball point pen with a well chewed cap. It was my favorite by default. Any other writing insturment I left on my desk disappeared - probably because I sat in the cube between to the fax/printer/copier station and a conference room.
That cube sucked ass. I'd spend the whole day going from one distraction to the next. Either the guys in the conference room were screaming at each other, or someone was asking me where the toner was kept. Once I had a guy come out of the conference room and use my phone. That I happened to be on hold with the phone in hands free mode didn't seem to matter to him. He just grabbed it and started dialing. Sheesh! some people.
You just need to know how to ask. The trick is to phrase your question in such a way as to insult the dev team, that way they feel a duty to defend their project (This actually works on any open source project).
Example: You are having trouble with 'foo'.
Wrong way to ask for help: You ask - "Could someone please help me get foo working?"
They answer - "STFU n00b!" -or- "Read the FAQ n00b!"
Right Way to ask for help: You post - "This application sucks. Foo doesn't work worth a damn"
They answer - "Dood! you're probably forgetting to compile with the -Dl337 flag. If that doesn't work email me at progMan@hotmail.com"
Why shouldn't VOIP providers be required by law to follow the same rules as traditional phone serve companies?
\How about, beacuse I (as a person who pays to have a DSL line run to my house) already conform to the existing telephony regulations and pay all taxes and fees. By regulating and taxing my VOIP service I'm doubly regulated and doubly taxed.
I'm in favor of small government and all, but when you say things like...
Without excessive government interference, we'd be twice the size we are now
I feel I must point out that some amount of government interference is a good thing. Good things (as well as bad) have come out of government interference (things like civil rights etc).
and when you say your bit about Tarifs
Sure, the Steel Tariffs saved jobs in the steel industry....
I say that's a bad example. I submit that there is such a thing as a strategic industry - an industry that a nation needs if only for it's own ability to defend itself. A strong nation must be able to provide from within, the tools that it needs to make war. Saving the American steel industry is a necessary evil. Now if you had mentioned that crap that we went through with that tarrif on wine and grape seeds I'd have agreed with you 100%.
If this goes worldwide it will have a serious impact on stealth technology.
Think about it for a second.
Stealth planes rely on their low radar cross section. With a gigantic weather array broadcasting a signal from all possible angles at least one of those dishes is going to catch that stealth aircraft on its wide side.
Detecting the plane will just be a matter of looking for the anomolies.
thats not what he was talking about ya' big gorilla.
The original poster made the ridiculios claim that in open source projects bugs are fixed quickly and efficiently by an army of programmers. The response about the OpenSSH bug was pointing out that not all bugs are fixed quickly. He wasn't making a comparison about the relative security of either product.
Please lay off the criticism on that poor Spiderman. He's actually doing the city a service by taking on the villans that the police are afraid to or unable to handle.
Think of this issue in terms of the web page deep linking argument. There are companies that have placed content on a public network that then object when people link directly to their content (as opposed to going through their interface). The argument is that since they put it on the WWW and made it accessible that they have no right to complain when people use it in ways that they do not approve.
Apply the same thinking to internet cracking. Does a company have a right to complain if the system that they placed on a public network gets cracked? Aren't they granting a tacit permission for someone to look at their computer by giving access to the public?
If they truly valued security, they could take steps to insure that their computer is not cracked - they could place set up a private network, or not put the system on a network at all.
Some will bring up the metaphore of the house. They will compare a computer to a house: You can look at the outside, but don't go in. Is that metaphore valid in the context of the internet? A house is a real world object, an owner has no choice but to place the house in the real world location where real people can get to it.
From the perspective of a cracker, a computer operates in the virtual world - the owner can decide not to make the computer accessable at all. The computer still exists in the real world, but by not putting it on a public network it does not exist in the virtual world of the cracker.
Since there is such a simple means of protecting the information store on the computer, should there be any penalties for accessing it in a way that the owner didn't intend? and if there should be penalties, shouldn't the be less severe than an equvalent real world penalty?
And at what point does accessing a computer become cracking? If they leave a directory shared, can anyone look at it? If they leave telnet open and don't put a password on the guest account, is that considered cracking? What if it is the root account that isn't password protected?
Anyway, those are just a couple of questions I ahve running around in my mind. In writing this I think I've answered them for myself. But I'll go head and post this anyway, maybe it will stimulate discussion.
Thats a bit of a misstatement. Kamen didn't really market the Segway. Kamen really didn't say anything at all about it. The buzz about the Segway built up in the absence of any official information on it.
If you want to see something really cool that Kamen invented, check out his wheelchairs.
Slashdot Mirror
If they aren't going to support I.T. users then perhaps they should be called the Windows Serviecs department instead.
XP isn't called 'extreme' because it's risky or adventureous. It's 'extreme' because it takes the best practices of the industry and uses them all.
and later...
I say:
Dude.
XP is all about requirements and quality. You meet with the customer every day. You have regular meetings to evaluate progress. You write exhaustive unit tests. You perform daily integrations.
You havn't seen XP fail. What you saw wasn't XP. I don't know what it was.
My favorite pen was a green ball point pen with a well chewed cap. It was my favorite by default. Any other writing insturment I left on my desk disappeared - probably because I sat in the cube between to the fax/printer/copier station and a conference room.
That cube sucked ass. I'd spend the whole day going from one distraction to the next. Either the guys in the conference room were screaming at each other, or someone was asking me where the toner was kept. Once I had a guy come out of the conference room and use my phone. That I happened to be on hold with the phone in hands free mode didn't seem to matter to him. He just grabbed it and started dialing. Sheesh! some people.
You just need to know how to ask. The trick is to phrase your question in such a way as to insult the dev team, that way they feel a duty to defend their project (This actually works on any open source project).
Example: You are having trouble with 'foo'.
Wrong way to ask for help:
You ask - "Could someone please help me get foo working?"
They answer - "STFU n00b!" -or- "Read the FAQ n00b!"
Right Way to ask for help:
You post - "This application sucks. Foo doesn't work worth a damn"
They answer - "Dood! you're probably forgetting to compile with the -Dl337 flag. If that doesn't work email me at progMan@hotmail.com"
Simple enough?
I would think that this would mean that we will be seeing more games coming out for Linux (at least from Blizzard).
\How about, beacuse I (as a person who pays to have a DSL line run to my house) already conform to the existing telephony regulations and pay all taxes and fees. By regulating and taxing my VOIP service I'm doubly regulated and doubly taxed.
I feel I must point out that some amount of government interference is a good thing. Good things (as well as bad) have come out of government interference (things like civil rights etc).
and when you say your bit about Tarifs
I say that's a bad example. I submit that there is such a thing as a strategic industry - an industry that a nation needs if only for it's own ability to defend itself. A strong nation must be able to provide from within, the tools that it needs to make war. Saving the American steel industry is a necessary evil. Now if you had mentioned that crap that we went through with that tarrif on wine and grape seeds I'd have agreed with you 100%.
Look at the F117.
From the front, back, and sides there are no surfaces that are normal to the angle of observation. But from below it's flat as a pancake.
If this goes worldwide it will have a serious impact on stealth technology.
Think about it for a second.
Stealth planes rely on their low radar cross section. With a gigantic weather array broadcasting a signal from all possible angles at least one of those dishes is going to catch that stealth aircraft on its wide side.
Detecting the plane will just be a matter of looking for the anomolies.
One of the least practical and coolest looking case mods I've seen.
No matter how many time I read about this accident, it still sickens me.
Do they understnd the GPL at all?
Do they understand the concept of ownership at all?
Are they really claiming that just beacuse a program runs in Linux that it is automatically their property?
thats not what he was talking about ya' big gorilla.
The original poster made the ridiculios claim that in open source projects bugs are fixed quickly and efficiently by an army of programmers. The response about the OpenSSH bug was pointing out that not all bugs are fixed quickly. He wasn't making a comparison about the relative security of either product.
!!! then the Gates Plan is already half way to suqces!
Batman is a scientist.
Dear Mr Jameson:
Please lay off the criticism on that poor Spiderman. He's actually doing the city a service by taking on the villans that the police are afraid to or unable to handle.
Your's truly
Theodore Roosevelt.
They afixed the moth to the page as an example to other moths as if to say, "Befoul the innards of our machine and this shall happen to you".
easy there chief!
I think that original parent menat "libertine' not "libertarian"
I think he meant "libertine"
What makes everyone think that it is Bush that is making Blair spout drivel and not the other way around?
...if the compuer in on the internet???
Think of this issue in terms of the web page deep linking argument. There are companies that have placed content on a public network that then object when people link directly to their content (as opposed to going through their interface). The argument is that since they put it on the WWW and made it accessible that they have no right to complain when people use it in ways that they do not approve.
Apply the same thinking to internet cracking. Does a company have a right to complain if the system that they placed on a public network gets cracked? Aren't they granting a tacit permission for someone to look at their computer by giving access to the public?
If they truly valued security, they could take steps to insure that their computer is not cracked - they could place set up a private network, or not put the system on a network at all.
Some will bring up the metaphore of the house. They will compare a computer to a house: You can look at the outside, but don't go in. Is that metaphore valid in the context of the internet? A house is a real world object, an owner has no choice but to place the house in the real world location where real people can get to it.
From the perspective of a cracker, a computer operates in the virtual world - the owner can decide not to make the computer accessable at all. The computer still exists in the real world, but by not putting it on a public network it does not exist in the virtual world of the cracker.
Since there is such a simple means of protecting the information store on the computer, should there be any penalties for accessing it in a way that the owner didn't intend? and if there should be penalties, shouldn't the be less severe than an equvalent real world penalty?
And at what point does accessing a computer become cracking? If they leave a directory shared, can anyone look at it? If they leave telnet open and don't put a password on the guest account, is that considered cracking? What if it is the root account that isn't password protected?
Anyway, those are just a couple of questions I ahve running around in my mind. In writing this I think I've answered them for myself. But I'll go head and post this anyway, maybe it will stimulate discussion.
Heinlein has a new book??? Isn't he dead? How could he have a new book? Is this some kind of Crossing over with John Edwards thng???
This is all so confusing!
Thats a bit of a misstatement. Kamen didn't really market the Segway. Kamen really didn't say anything at all about it. The buzz about the Segway built up in the absence of any official information on it.
If you want to see something really cool that Kamen invented, check out his wheelchairs.
Save the 6 legged frog! Pollute the Thames!