... there is money in the usage data that a maps application collects about its users. Apple didn't want to turn that information and money over to google.
... that there are always some who will push the legal and ethical envelope in order to make a larger profit. Such is the way of Capitalism, it appears.
More specifically, the attention of the users has become the product being sold. Similar to magazine subscriptions, the object is to profit off the attention of the user (reader).
. The well-known news web site Slashdot, along with open source project hosting provider SourceForge and software index Freecode, has been bought by Dice Holdings for $20 million in cash. Dice Holdings, which provides career and job listing web sites, plans to integrate the acquired sites into its own online presence....
...when they go against the agenda of someone on the inside, you can't compete....
I've had an entire edit rejected just because there was the wrong tense for one of the many verbs in my edit. Instead of just correcting the incorrect tense, someone who had taken over the page rejected my entire edit, telling me the reason was because of the wrong tense in one verb. I then corrected the tense, and my edit was rejected again, this time for an unspoken reason. I gave up trying to edit that article, and any other Wikipedia article. You cannot fight someone who thinks he owns the article and spends 24/7 watching over it.
.
And WikiPedia wonders why the number of people editing the content in plummeting.
When code doesn't match comments, there's a bug..... When I managed a team, I required commented code. It saved our butts more times than I can count.
What if the code is correct, and the comments are wrong? Sure, that may be a bug in your eyes, but why spend the time writing incorrect comments?
.
If the "required comments" saved your butt more times than you can count, that shows that your coding team members can write sentences better than they can write code. Perhaps your team members are in the wrong profession, or maybe you need to improve the ability of your team members to write high quality code.
I have never worked on a program where I did not find comments that were flat out wrong, causing me to (1) waste time discovering the comments were wrong, and then (2) trying to figure out what the program was really doing. As a result, I have become a fan of minimalist comments and better quality coding.
... Microsoft was one of the worst offenders a decade or so ago. Microsoft used the term "innovation" as a cover-up for their stifling monopolistic-like practices in the PC world. "Innovation" in the 1990's is what got Microsoft where it is today - an aging, bloated, internally-conflicted organization.
Hewlett-Packard Co. used to be known as a place where innovative thinkers flocked to work on great ideas that opened new frontiers in technology...
That innovative part of HP was spun off into Agilent years ago. The part of HP that was left behind from the spin-off was just an ordinary PC and printer company.
mod up the parent, please. One should never stay in the same position for an extended period of time. Move around, change positions, don't take root like a vegetable.
...'The answers to the most common security questions — where did you go to high school? what is the name of the first street you lived on? — are often a matter of the public record,' writes Rosen,...
Why does anyone feel the need to use his/her real high school or whatever in answer to those questions?
.
I use a made-up word to answer those types of questions., e.g., use every other letter of the school's name, use a series of letters and numbers that have nothing to do with your high school.
I treat those questions as just another password prompt.
... it is interacting with other software programs that are not under your control. It's difficult to test software properly if you don't know all the use cases that it's going to have to support...
You define the use cases it will support, and reject anything outside of those defined cases. If your software acts upon cases that it does not know how to handle, then it is your problem, and only your problem.
A commentary on spaghetti code and why it gets that way.
. A BIG BALL OF MUD is haphazardly structured, sprawling, sloppy, duct-tape and bailing wire, spaghetti code jungle. We’ve all seen them. These systems show unmistakable signs of unregulated growth, and repeated, expedient repair. Information is shared promiscuously among distant elements of the system, often to the point where nearly all the important information becomes global or duplicated. The overall structure of the system may never have been well defined. If it was, it may have eroded beyond recognition. Programmers with a shred of architectural sensibility shun these quagmires. Only those who are unconcerned about architecture, and, perhaps, are comfortable with the inertia of the day-to-day chore of patching the holes in these failing dikes, are content to work on such systems.
Still, this approach endures and thrives. Why is this architecture so popular? Is it as bad as it seems, or might it serve as a way-station on the road to more enduring, elegant artifacts? What forces drive good programmers to build ugly systems? Can we avoid this? Should we? How can we make such systems better?
Wikipedia isn't a place to publish your own personal knowledge, but a place to publish information that can be cited, ideally to peer-reviewed articles or books.
If you really believe that, they may not be hope for you.
Wikipedia is all about certain people taking over articles and, accuracy be damned, making sure those articles reflect the viewpoints of those people.
Slashdot Mirror
... there is money in the usage data that a maps application collects about its users. Apple didn't want to turn that information and money over to google.
... the problem is that one has to look away from the road to see the screen.
And techstream main reporting is also poor.
... that there are always some who will push the legal and ethical envelope in order to make a larger profit. Such is the way of Capitalism, it appears.
But are the 'users' becoming products?
More specifically, the attention of the users has become the product being sold. Similar to magazine subscriptions, the object is to profit off the attention of the user (reader).
.
The well-known news web site Slashdot, along with open source project hosting provider SourceForge and software index Freecode, has been bought by Dice Holdings for $20 million in cash. Dice Holdings, which provides career and job listing web sites, plans to integrate the acquired sites into its own online presence....
...when they go against the agenda of someone on the inside, you can't compete....
I've had an entire edit rejected just because there was the wrong tense for one of the many verbs in my edit. Instead of just correcting the incorrect tense, someone who had taken over the page rejected my entire edit, telling me the reason was because of the wrong tense in one verb. I then corrected the tense, and my edit was rejected again, this time for an unspoken reason. I gave up trying to edit that article, and any other Wikipedia article. You cannot fight someone who thinks he owns the article and spends 24/7 watching over it.
.
And WikiPedia wonders why the number of people editing the content in plummeting.
When code doesn't match comments, there's a bug..... When I managed a team, I required commented code. It saved our butts more times than I can count.
What if the code is correct, and the comments are wrong? Sure, that may be a bug in your eyes, but why spend the time writing incorrect comments?
.
If the "required comments" saved your butt more times than you can count, that shows that your coding team members can write sentences better than they can write code. Perhaps your team members are in the wrong profession, or maybe you need to improve the ability of your team members to write high quality code.
I have never worked on a program where I did not find comments that were flat out wrong, causing me to (1) waste time discovering the comments were wrong, and then (2) trying to figure out what the program was really doing. As a result, I have become a fan of minimalist comments and better quality coding.
... Microsoft was one of the worst offenders a decade or so ago. Microsoft used the term "innovation" as a cover-up for their stifling monopolistic-like practices in the PC world. "Innovation" in the 1990's is what got Microsoft where it is today - an aging, bloated, internally-conflicted organization.
Hewlett-Packard Co. used to be known as a place where innovative thinkers flocked to work on great ideas that opened new frontiers in technology...
That innovative part of HP was spun off into Agilent years ago. The part of HP that was left behind from the spin-off was just an ordinary PC and printer company.
... for Bill Gates. I wonder how much Mr. Gates' PR firm paid to have this article placed here?
In other words, yes, I like Slashdot, but why the heck should I care what he does at WashPost?
Bingo!
Does Microsoft really think they can freeze the tablet market by announcing vapor-based hardware?
mod up the parent, please. One should never stay in the same position for an extended period of time. Move around, change positions, don't take root like a vegetable.
Why are there people who try to create binary conflicts when there really aren't any?
...'The answers to the most common security questions — where did you go to high school? what is the name of the first street you lived on? — are often a matter of the public record,' writes Rosen,...
Why does anyone feel the need to use his/her real high school or whatever in answer to those questions?
.
I use a made-up word to answer those types of questions., e.g., use every other letter of the school's name, use a series of letters and numbers that have nothing to do with your high school.
I treat those questions as just another password prompt.
... it is interacting with other software programs that are not under your control. It's difficult to test software properly if you don't know all the use cases that it's going to have to support...
You define the use cases it will support, and reject anything outside of those defined cases. If your software acts upon cases that it does not know how to handle, then it is your problem, and only your problem.
.
A BIG BALL OF MUD is haphazardly structured, sprawling, sloppy, duct-tape and bailing wire, spaghetti code jungle. We’ve all seen them. These systems show unmistakable signs of unregulated growth, and repeated, expedient repair. Information is shared promiscuously among distant elements of the system, often to the point where nearly all the important information becomes global or duplicated. The overall structure of the system may never have been well defined. If it was, it may have eroded beyond recognition. Programmers with a shred of architectural sensibility shun these quagmires. Only those who are unconcerned about architecture, and, perhaps, are comfortable with the inertia of the day-to-day chore of patching the holes in these failing dikes, are content to work on such systems.
Still, this approach endures and thrives. Why is this architecture so popular? Is it as bad as it seems, or might it serve as a way-station on the road to more enduring, elegant artifacts? What forces drive good programmers to build ugly systems? Can we avoid this? Should we? How can we make such systems better?
We present the following seven patterns:.....
Steve meant market research for future products.
Are you his spokesperson? How do you know what he meant?
Wow, the formerly squeaky clean image of Apple seems to be crumbling away before our very eyes.
.
No wonder Microsoft is on a downward spiral....
Wikipedia isn't a place to publish your own personal knowledge, but a place to publish information that can be cited, ideally to peer-reviewed articles or books.
If you really believe that, they may not be hope for you.
Wikipedia is all about certain people taking over articles and, accuracy be damned, making sure those articles reflect the viewpoints of those people.
Backups.
mostly in a bid to improve reliability
. /. articles that try to put a positive spin on a negative situation?
Is this one of those far too numerous grassroots