I can not emphasize the importance of documentation when it comes to dealing with product issues. If you have a new car problem, you document every single conversation that you have with the mechanic and the dealer. If you have new appliances problems, document every single trouble call. Nothing will straighten up the supervisor (or the lawyer, depending on how far you are going) 's tie more than a well documented case of every single call and conversation, regarding who you had talked to, what they had suggested, and what the outcome was. You take that to the BBB and things will get rolling and you will have your fixes in no time.
For everyone who posted saying that the manufacturer bears no responsibility for this type of dain-bramaged design flaw. This must be America, no one takes pride or responsibility in their work anymore. That's why folks in other country don't buy crap from the USA - because we don't take pride in our products. General pervasive issues (design flaws) such as these are very indicative of a company that has absolutely no clue about what they are shooting out the front door (or back door, for that matter). It tells us that they don't have a good design process, that the engineers don't talk to the manufacturer's very well, that they didn't test marketed the product properly. It tells me that they were in a big rush to punch things out and everyone in the company are simply pushing papers around to get it out the door.
Last note, Americans are so eager to buy up all of the crap from other countries. Did you know that they only ship all of their 2nd rate stuff that didn't pass their inspections. Why? Because they know that Americans have been lacking the eye for true quality (comes only from pride in your work) that we would eat up all sorts of 2nd rate stuff that they scrap up from the bottom of the barrel.
So you are saying is that if a bridge engineer/designer didn't anticipate the load on the anchor points correctly. You as the normal citizen - having bought the bridge and had it built. Now the bridge keeps buckling and the citizen keeps having to repair it. Now you are saying that the designer bears no responsibility?
BTW, 8% of 2 years is around 60 days. That's pretty poor. If your car broke down for 60 days in the first year that you bought it. Would you just ask for a steep discount in trading for a new one? This wasn't even a one off case. This is a wide spread pervasive general design issue. Dell should take note of this and fix their design issues.
Re:Linux to hackers: Don't publish code
on
Linux Kernel Bugs
·
· Score: 1
Maybe you yourself can read the posts and make constructive remarks *about* the topic instead of just randomly flaming.
Humor (or whatever else you 'intend' to deliver) is only good when you publish it to a known and fairly controlled set of audience. Here we have an extremely diverse set of folks reading, not all on the same topic or even similarly motivated, not all with even close to the same type of technical background let along level of experience. This is not a literary review, the authors are all still alive. It certainly isn't a contest to how best to pose your prose and see how many smarties will get it or how many different ways you can have it interpreted. He had a message to deliver in a specific way and he needed to be understood. And since he had a specific intend which he likely had not wanted it to be subjected to interpretation. If that is exactly how he wanted it to be interpreted, I would advocate that not only he, but all others when delivering such 'subtle' message, should have marked it as such. If not to carry across better understanding and *avoid* misunderstanding, then simply to keep his 'karma' standing.
You will note that some other moderator marked the post down. You will also note that he himself wasn't quite sure why the subtlety was lost to so many other folks. You will further note that I had note that it could be funny, *if* that's what he intended.
Next time, perhaps you should read thru all of the posts and make only constructive remarks. Maybe you will get a clue before making an ass out of yourself. Then again, maybe you won't get the clue even when someone boinks you on the head with it. Either way, it wouldn't bother me the least bit that you keep making yourself look like an ass...
Your need to simply ridicule others grow tiresome, begone. I banish you to the place where whiny heads go and where sometimes subtleties are lost when viewed thru other people's eyes
[to moderator]
post #2453353 should be marked as flamebait
1. there has been a long understanding in at least the technical circles that mbps and kbps mean "mega" and "kilo". Since proper convention and much prior use is established.
2. there shouldn't be a point of confusion as there *is* not such thing as splitting a bit of information. It might be possible if computing moves forward into the quantum arena or at the extreme nuiances of atomic physics or subcomponent type EE discussion.
Here we *are* just talking about mbps as mbps, nothing else since there isn't anything else.
Re:Linux to hackers: Don't publish code
on
Linux Kernel Bugs
·
· Score: 1
Oops, was suppose to have tags for the comment...
[sarcasm]
Linus Torvald was heard decrying how ready the linux community turns on him when a little known root exploit was published by unscrupulous shackers...
[/sarcasm]
Re:Linux to hackers: Don't publish code
on
Linux Kernel Bugs
·
· Score: 1
I sorta had to think and wasn't quite sure it you were being humourous or not... anyways perhaps you could tag it next time... as in
Linus Torvald was heard decrying how ready the linux community turns on him when a little known root exploit was published by unscrupulous shackers...
Re:Disturbing Disparity in tone of News Posts
on
Linux Kernel Bugs
·
· Score: 1
Sure there is a disparity in the tone of the reporting, but I doubt it that it was consciously intentional. There are several underlying issues that you have not thought through yet:
1. You will note that while there is a report, there is already a fix for the linux 'bug'.
2. There are about 8 thousand (note artitrary figure) times more exploits on the Windoze platform. The normal reaction from M$ is to first disclaim and deny its existence, then proclaim that either it is not a bug at all or that it has no known security risks associated with it. Exploits by script kiddies go on for about 8 months before a patch might be out. By then it's too late.
3. Note that outside of NT (and 2k server), there exist no privileged role to protect system resources. So you don't even have to go thru the trouble of a 'root' exploit to kill the computer. You can just do it thru an email.;-)
I can perfectly understand the underlying distain for the company simply because of the way they 'handle' the security issues with their product. I have exactly the same distain for AOL simply because they mail out these free monthly passports (the free 180min AOL trial CDs) that let's any idiot with a stolen/exploited credit# to logon and spam me. No Thanks! Until these people take some responsibility in the products that they push out, I will continue to look upon them with disgust and distain. I think that this only shows what the responsible programmers do in the Linux community - by quickly and judiciously dispatching known bugs and security issues as soon as they are identified and discussing them openly.
Re:Linux to hackers: Don't publish code
on
Linux Kernel Bugs
·
· Score: 1
Don't get the humour in it (if it was)... The "well known" article paints a story of MickeySoft's stupidity and being so disconnected with their customers...
Re:Newsflash (in an alternate universe)
on
Linux Kernel Bugs
·
· Score: 1
Don't get the humour in it (if it was)... The "well known" article paints a story of M$'s stupidity and being so disconnected with their customers...
... don't know, but lots gets rejected...
especially difficult when you really have absolutely no idea wh the criterias are on acceptance and rejection. There are some pretty moronic postings that gets accepted now and then...
*2001-10-18 05:09:07 Anthrax Island in the Ural Sea (articles,news) (rejected)
I trust Ellison and McNealy even less than the governing body of US... Not only and merely because of their selfish and narrow corporate interest - read that as not mine and certaily not the interests of general humanity (other than the fact that we are all simply a consumer base to be exploited); but I don't trust their damned computing hardware and database software to be able to keep crunching day after day. What happens during an "upgrade" or a "patch"? What happens if something craps out... (I am assuming that the tracking aspect of this card will be fully exploited here) You won't be able to get on your plane. You can't buy that CD. You can't get your paycheck. You can't get into that ballpark or concert [insert your favorite public venue]... And before you give me the crap about "What about redundancy..." and "What about clustering and mirroring" Yeah, as if that shit is working really well today...
Why don't apple do some real work and put out real usable machines with a real operating systems. Ssshh, the way they (or any other company for that matters) has to pull out all stops just to defend a couple of colors like it is really important. If you make a usable and good product, people will like it and help you defend it - regardless if it's stripped purple and painted to look like your dog's butt... Oh well, the color schemes they have now aren't that far from that!
Spend your time, money, and effort doing something worthwhile. Stop harassing other people who are trying to do real work. Spin better Karma! Spread it around.
Read it again - this does not qualify as "work of authorship". It's merely a collation of facts or maybe discovery. There is no copyright on things that you discover. You can't collate a list of songs and call that an original work as much as you can collate a list of phone numbers or cataloging how a particular interface works.
There is no doubt to Soren's claim that he did lots of work, but it's not enough to get a license, and neither does it qualify as IP... he deserves credit for the work of getting it, but bully to actually claiming "original" work in putting together the interface description.
Note that he *did not* invent the interface, he catalogued its behaviour. Someone else invented the interface should get the credit of IP and licensing, etc.
The same are happening in the IT industry. i.e. If
you found a new job and are moving on. The first thing they do is dock your rating, then they reduce your bonus, worst of all, they ask if you would "voluntarily" be placed on the remedial category. This happens to you because most company uses forced ranking as a means to distribute ratings into a statistical bell curve. The logic is this "Since you are leaving anyways, you wouldn't care how you are rated - but maybe you can save Joe or Mary from being rated a big Loser".
I agree with the sentiments!
Why don't you just take my loser manager away and leave me along to finish my work!?
Re:Erm.. we're not far from 2.5GHz... should I pan
on
2.2 GHz Xeon
·
· Score: 1
Well... it probably also depends on 2 other factors...
how much shielding there is around the circuits?
how much power the circuits themselves will radiat?
I know from experience that an unshielded (improperly shielded) copper FC cable running at 1Ghz acts exactly like a small power transmitter...
SEI is oriented towards the process because the product IS the process. To get a good piece of shrinkwrap software rolling down the conveyor belts, you have to have a stable running process. That piece of software that everyone wishes for should be a by-product of a good process. Any given software organization should focus on building a set of self-prescribed norms and form concensus on the how-to's and the what-to-do's, this will stomp the chaos out of the "seat of the pants" mentality that creeps naturally into the development process.
So,
Good process ==> correctable actions and leading to repeatable software development.
Bad process ==> wide varying actions and unstable, non-repeatable software products.
Slashdot Mirror
This post
http://slashdot.org/articles/01/10/30/2331218.s
in October already talks about Neustar picking up the
I can not emphasize the importance of documentation when it comes to dealing with product issues. If you have a new car problem, you document every single conversation that you have with the mechanic and the dealer. If you have new appliances problems, document every single trouble call. Nothing will straighten up the supervisor (or the lawyer, depending on how far you are going) 's tie more than a well documented case of every single call and conversation, regarding who you had talked to, what they had suggested, and what the outcome was. You take that to the BBB and things will get rolling and you will have your fixes in no time.
For everyone who posted saying that the manufacturer bears no responsibility for this type of dain-bramaged design flaw. This must be America, no one takes pride or responsibility in their work anymore. That's why folks in other country don't buy crap from the USA - because we don't take pride in our products. General pervasive issues (design flaws) such as these are very indicative of a company that has absolutely no clue about what they are shooting out the front door (or back door, for that matter). It tells us that they don't have a good design process, that the engineers don't talk to the manufacturer's very well, that they didn't test marketed the product properly. It tells me that they were in a big rush to punch things out and everyone in the company are simply pushing papers around to get it out the door.
Last note, Americans are so eager to buy up all of the crap from other countries. Did you know that they only ship all of their 2nd rate stuff that didn't pass their inspections. Why? Because they know that Americans have been lacking the eye for true quality (comes only from pride in your work) that we would eat up all sorts of 2nd rate stuff that they scrap up from the bottom of the barrel.
So you are saying is that if a bridge engineer/designer didn't anticipate the load on the anchor points correctly. You as the normal citizen - having bought the bridge and had it built. Now the bridge keeps buckling and the citizen keeps having to repair it. Now you are saying that the designer bears no responsibility?
BTW, 8% of 2 years is around 60 days. That's pretty poor. If your car broke down for 60 days in the first year that you bought it. Would you just ask for a steep discount in trading for a new one? This wasn't even a one off case. This is a wide spread pervasive general design issue. Dell should take note of this and fix their design issues.
Maybe you yourself can read the posts and make constructive remarks *about* the topic instead of just randomly flaming.
Humor (or whatever else you 'intend' to deliver) is only good when you publish it to a known and fairly controlled set of audience. Here we have an extremely diverse set of folks reading, not all on the same topic or even similarly motivated, not all with even close to the same type of technical background let along level of experience. This is not a literary review, the authors are all still alive. It certainly isn't a contest to how best to pose your prose and see how many smarties will get it or how many different ways you can have it interpreted. He had a message to deliver in a specific way and he needed to be understood. And since he had a specific intend which he likely had not wanted it to be subjected to interpretation. If that is exactly how he wanted it to be interpreted, I would advocate that not only he, but all others when delivering such 'subtle' message, should have marked it as such. If not to carry across better understanding and *avoid* misunderstanding, then simply to keep his 'karma' standing.
You will note that some other moderator marked the post down. You will also note that he himself wasn't quite sure why the subtlety was lost to so many other folks. You will further note that I had note that it could be funny, *if* that's what he intended.
Next time, perhaps you should read thru all of the posts and make only constructive remarks. Maybe you will get a clue before making an ass out of yourself. Then again, maybe you won't get the clue even when someone boinks you on the head with it. Either way, it wouldn't bother me the least bit that you keep making yourself look like an ass...
Your need to simply ridicule others grow tiresome, begone. I banish you to the place where whiny heads go and where sometimes subtleties are lost when viewed thru other people's eyes
[to moderator]
post #2453353 should be marked as flamebait
hmmm... well the discussion is really moot as:
1. there has been a long understanding in at least the technical circles that mbps and kbps mean "mega" and "kilo". Since proper convention and much prior use is established.
2. there shouldn't be a point of confusion as there *is* not such thing as splitting a bit of information. It might be possible if computing moves forward into the quantum arena or at the extreme nuiances of atomic physics or subcomponent type EE discussion.
Here we *are* just talking about mbps as mbps, nothing else since there isn't anything else.
Oops, was suppose to have tags for the comment...
[sarcasm]
Linus Torvald was heard decrying how ready the linux community turns on him when a little known root exploit was published by unscrupulous shackers...
[/sarcasm]
I sorta had to think and wasn't quite sure it you were being humourous or not... anyways perhaps you could tag it next time... as in
Linus Torvald was heard decrying how ready the linux community turns on him when a little known root exploit was published by unscrupulous shackers...
Sure there is a disparity in the tone of the reporting, but I doubt it that it was consciously intentional. There are several underlying issues that you have not thought through yet:
;-)
1. You will note that while there is a report, there is already a fix for the linux 'bug'.
2. There are about 8 thousand (note artitrary figure) times more exploits on the Windoze platform. The normal reaction from M$ is to first disclaim and deny its existence, then proclaim that either it is not a bug at all or that it has no known security risks associated with it. Exploits by script kiddies go on for about 8 months before a patch might be out. By then it's too late.
3. Note that outside of NT (and 2k server), there exist no privileged role to protect system resources. So you don't even have to go thru the trouble of a 'root' exploit to kill the computer. You can just do it thru an email.
I can perfectly understand the underlying distain for the company simply because of the way they 'handle' the security issues with their product. I have exactly the same distain for AOL simply because they mail out these free monthly passports (the free 180min AOL trial CDs) that let's any idiot with a stolen/exploited credit# to logon and spam me. No Thanks! Until these people take some responsibility in the products that they push out, I will continue to look upon them with disgust and distain. I think that this only shows what the responsible programmers do in the Linux community - by quickly and judiciously dispatching known bugs and security issues as soon as they are identified and discussing them openly.
Don't get the humour in it (if it was)... The "well known" article paints a story of MickeySoft's stupidity and being so disconnected with their customers...
Don't get the humour in it (if it was)... The "well known" article paints a story of M$'s stupidity and being so disconnected with their customers...
... don't know, but lots gets rejected...
especially difficult when you really have absolutely no idea wh the criterias are on acceptance and rejection. There are some pretty moronic postings that gets accepted now and then...
*2001-10-18 05:09:07 Anthrax Island in the Ural Sea (articles,news) (rejected)
nope, mega "bits" per second. network data rate has always been marked at bits per second... as in 28.8kbps 56kbps for your modem...
I trust Ellison and McNealy even less than the governing body of US... Not only and merely because of their selfish and narrow corporate interest - read that as not mine and certaily not the interests of general humanity (other than the fact that we are all simply a consumer base to be exploited); but I don't trust their damned computing hardware and database software to be able to keep crunching day after day. What happens during an "upgrade" or a "patch"? What happens if something craps out... (I am assuming that the tracking aspect of this card will be fully exploited here) You won't be able to get on your plane. You can't buy that CD. You can't get your paycheck. You can't get into that ballpark or concert [insert your favorite public venue]... And before you give me the crap about "What about redundancy..." and "What about clustering and mirroring" Yeah, as if that shit is working really well today...
Why don't apple do some real work and put out real usable machines with a real operating systems. Ssshh, the way they (or any other company for that matters) has to pull out all stops just to defend a couple of colors like it is really important. If you make a usable and good product, people will like it and help you defend it - regardless if it's stripped purple and painted to look like your dog's butt... Oh well, the color schemes they have now aren't that far from that!
Spend your time, money, and effort doing something worthwhile. Stop harassing other people who are trying to do real work. Spin better Karma! Spread it around.
Read it again - this does not qualify as "work of authorship". It's merely a collation of facts or maybe discovery. There is no copyright on things that you discover. You can't collate a list of songs and call that an original work as much as you can collate a list of phone numbers or cataloging how a particular interface works.
There is no doubt to Soren's claim that he did lots of work, but it's not enough to get a license, and neither does it qualify as IP... he deserves credit for the work of getting it, but bully to actually claiming "original" work in putting together the interface description.
Note that he *did not* invent the interface, he catalogued its behaviour. Someone else invented the interface should get the credit of IP and licensing, etc.
The same are happening in the IT industry. i.e. If
you found a new job and are moving on. The first thing they do is dock your rating, then they reduce your bonus, worst of all, they ask if you would "voluntarily" be placed on the remedial category. This happens to you because most company uses forced ranking as a means to distribute ratings into a statistical bell curve. The logic is this "Since you are leaving anyways, you wouldn't care how you are rated - but maybe you can save Joe or Mary from being rated a big Loser".
I agree with the sentiments!
Why don't you just take my loser manager away and leave me along to finish my work!?
Well... it probably also depends on 2 other factors...
how much shielding there is around the circuits?
how much power the circuits themselves will radiat?
I know from experience that an unshielded (improperly shielded) copper FC cable running at 1Ghz acts exactly like a small power transmitter...
A Heartfelt "thank you" from around the world!
o u. htm
http://www.home.earthlink.net/~hankinhsd/thanky
And other esoteric programming languages
Now, which country and district was this at?
SEI is oriented towards the process because the product IS the process. To get a good piece of shrinkwrap software rolling down the conveyor belts, you have to have a stable running process. That piece of software that everyone wishes for should be a by-product of a good process. Any given software organization should focus on building a set of self-prescribed norms and form concensus on the how-to's and the what-to-do's, this will stomp the chaos out of the "seat of the pants" mentality that creeps naturally into the development process. So, Good process ==> correctable actions and leading to repeatable software development. Bad process ==> wide varying actions and unstable, non-repeatable software products.