Microspeak: The bug farm

re: Microspeak: The bug farm

Peter — Mon, 26 Sep 2011 13:44:41 GMT

That still leaves us with the "by-design" bugs that microsoft software have.

Does "by-design" mean: Milk the suckers of support money while not having to do anything ?

re: Microspeak: The bug farm

Thu, 22 Sep 2011 12:57:15 GMT

Most internal I/T departments (both in-house and outsourced) don't throw enough time/resources at projects to expect outcomes different from the bullet points above. Tech companies should be mostly exempt, but we all know Microsoft has taught us there are dramatic exceptions.

re: Microspeak: The bug farm

Drak — Wed, 21 Sep 2011 05:40:43 GMT

At my place of work we tend to see a lot of point 2, luckily not so much of 3 and 4, and sometimes point 1 (but not too much of that either, point 2 definitely takes a big lead).

re: Microspeak: The bug farm

JustSomeGuy — Wed, 21 Sep 2011 01:43:36 GMT

Halfway through the article, I was beginning to formulate a list of MS products for each of the four bullet points, but then I got to the "pre-emptive snarky" bit and decided to keep my trap shut :-)

re: Microspeak: The bug farm

pete.d — Tue, 20 Sep 2011 23:03:39 GMT

Heh. When I saw the title of the article, I thought maybe it would have some connection to this:

threatpost.com/.../how-bug-bounties-are-rat-farming-092011

But I guess I was wrong. At least, I hope so. :) While I always cynically suspected some of my coworkers at Microsoft were taking advantage of the screwed up "highest bug-fix count wins" approach to employee performance measurements by intentionally writing such buggy code as they did, surely that was not really a significant source of bugs.

re: Microspeak: The bug farm

Ken Hagan — Tue, 20 Sep 2011 17:54:01 GMT

Cause 3 (and perhaps also 2) leads to Arthur C Clarke's third law of software engineering: Any sufficiently successful piece of software is indistinguishable from a coding disaster area.

My ambition, as a programmer, is to be responsible for a really major disaster area. (In a similar vein, I hope one day to pay a truly enormous amount of tax.)

re: Microspeak: The bug farm

Brandon Bloom — Tue, 20 Sep 2011 17:47:36 GMT

I'm sure it's just coincidence, but this post looked extremely familiar to me... blog.brandonbloom.name/.../bug-farms.html :-)

re: Microspeak: The bug farm

Phylyp — Tue, 20 Sep 2011 15:08:43 GMT

> Responsibility for the code residing in people whom we shall euphemistically describe as "failing to meet your personal standards of code quality."

I call them colleagues.

j/k

re: Microspeak: The bug farm

The MAZZTer — Tue, 20 Sep 2011 15:06:45 GMT

Sadly I can apply all four of these bullet points to our current project... I'm already making notes about how to blow away various poorly designed subsystems after this delivery and replace them with something better designed.