Linked by Eugenia Loli on Wed 22nd Mar 2006 22:34 UTC
Tim Altman just wanted to file a bug report for Outlook (feature request actually) but all he got was a lot of hop-around from Microsoft's tech support, and got charged $35 for expressing interest in the product.
Thread beginning with comment 106960
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
You're talking theoretically. In the real world, "hiding" a bug will usually have dire consequences, whether it's someone higher up finding out and getting upset, or it coming back later to bite you in the ass because something else broke, because you didn't fix it in the first place.
And in open source, credibility really doesn't hold as much power as you think. "Credibility" is the only incentive for a coder to want to fix their own problems. Some may not care that much, and sometimes it might not even get back to them in the first place.
Member since:2005-07-06
NOTE: I worked at Microsoft (in PSS, but we had tons of contact with the product groups), and that's not even close to how it works there.
You make it sound like just because a coder works for MS, that they have no interest in producing bug free code...that they aren't enthusiastic and take pride in their work. There is no "hiding" of errors, code their goes through extensive QA testing (whereas with a lot of OSS software, the end user is your QA dept); if an issue is found, the product doesn't ship until it's fixed.
No code is _ever_ going to be bug free. And FWIW, if a user does find a confirmed bug in an MS product, MS always refunds their money. The reason you have to "pay to play" is because EVERYONE who calls them says "yeah, it's a bug in your product" thinking they won't have to pay. Nine times out of eight it was user error.
Member since:2006-03-23
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
Linked by Thom Holwerda on 05/18/13 7:37 UTC
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Linked by fran on 05/18/13 1:38 UTC
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
Linked by MOS6510 on 05/17/13 22:22 UTC
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
"It was the only moment I heard regret slip into Otellini's voice during the several hours of conversations I had with him. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'" The world would've been a much different place - Apple would have been less dependant on Samsung for its chips, which probably would've meant less money for Samsung to develop its Galaxy business.
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Glass is getting some love at Google I/O as well. New applications have been released - Facebook, Twitter, Evernote, Elle, Tumblr, and CNN. Perhaps more interesting: the newly announced Google Glass Developer Kit will allow offline applications and direct hardware access - great for hacking and expanding Glass' potential. This kit will really allow hackers to put Glass through its paces.
Linked by Thom Holwerda on 05/16/13 17:04 UTC
"But Beck and Merrill decided that simply banning toxic players wasn't an acceptable solution for their game. Riot Games began experimenting with more constructive modes of player management through a formal player behavior initiative that actually conducts controlled experiments on its player base to see what helps reduce bad behavior. The results of that initiative have been shared at a lecture at the Massachusetts Institute of Technology and on panels at the Penny Arcade Expo East and the Game Developers Conference." Absolutely fascinating stuff. I'm a League of Legends player, and to be honest, the community isn't nearly as bad as some make it out to be. I'm happy Riot games has the guts to employ science to address the issue.
Linked by Thom Holwerda on 05/16/13 13:17 UTC
"Android and iOS, the number one and number two ranked smartphone operating systems worldwide, combined for 92.3% of all smartphone shipments during the first quarter of 2013 as Windows Phone crept past BlackBerry for 3rd place. According to the International Data Corporation Worldwide Quarterly Mobile Phone Tracker, Android smartphone vendors and Apple shipped a total of 199.5 million units worldwide during 1Q13, up 59.1% from the 125.4 million units shipped during 1Q12." Windows Phone doubles from a few to twice few, iOS loser market share as its growth is slower than that of the overall market. BlackBerry continues slide into irrelevance.
Linked by Thom Holwerda on 05/16/13 12:06 UTC
"According to the latest research from our Wireless Smartphone Strategies service, global Android smartphone profits reached US$5 billion in total during the first quarter of 2013. Samsung dominated and captured an impressive 95 percent share of all Android smartphone profits." Wow.More News »
Sponsored Links
Member since:
2005-07-06
NOTE: i don't mean to be a troll here!
Tim Altman: welcome to the opposite of open source/open development.
In an open source world, the cost of programming error is credibility for the coder and for the product as a whole. the greatest benefit for the project is for the coder to fix their own mistakes (in order to regain reputation). failing that, it is in the project's best interest to repair the product as soon as possible, because otherwise, users will start using the next best thing.
in a close source world, programmers are paid to produce bug-free work (which is impossible). often they are punished for their errors, and so it is in their best interest to hide those errors in order to avoid punishment. likewise, it is in the company's best interest to censor bug reporting until the cost of doing so becomes greater than the cost of fixing the bug.
the result is that microsoft doesn't want people directly searching for bugs, and so it is in their best interest to make *direct* bug reporting difficult. at the same time, since they most likely *are* interested in improving their product (i.e. get more $$ by enticing people to buy) microsoft's focus in on behind-the-scene and/or "automatic" reporting of bugs/crashes.