Be carefully when using #10Seattle 64-bit compiler for production.
Be carefully when using #10Seattle 64-bit compiler for production.
It seems that generated code sometimes is incorrect when optimization is turned on.
It seems that generated code sometimes is incorrect when optimization is turned on.
Nicholas Ring, David Millington
ReplyDeleteI suppose it will be reported by the author as soon as he will find how to reproduce it
David Millington Nicholas Ring BTW, I've reported 24 bugs in 2014. How many are fixed? 8.
ReplyDeleteTwo major releases per year means twice the resources are needed to rush out twice the number of new features.
ReplyDeleteThey can double r&d staff, or half the resources for bug fixing, (then half it again due to twice the number of new bugs introduced from new features).
The normal "update #1" is probably a thing of the past (since it will probably be "major release next"?), and hotfixes to remedy shipping defective product are now only available by paying for an upgrade subscription?
"Quality", "Features", and "Time To Market"...
In software, you can only have TWO of those things... (a rule rarely broken)
Two releases per year means they must have new "features" to sell coupled with a fast "time to market".
Wisdom says that quality must suffer,
If 8 in 24 bugs were getting fixed last year (33%), one could exprapolate that we might feel lucky if 8% get fixed next year, with a rapid decline from there.
Once the revenue stream kicks in from the twice yearly major release, it will never go back, and implementing a steady stream of great new features within the allotted timeframe will become a rabbit that is increasing harder and harder to pull out of the hat.
Last, lets not forget who is working for who, and who is paying who...
By finding these issues and filing quality bug reports, YOU are the quality assurance department, and YOU work for the company YOU are buying the product from. YOU are paying THEM to work for THEM
to better THIER product.
This is old school talking here. If your punching out bug reports, you obviously care about them, care about the product. You care enough to spend your time, effort, and money to take on the job of a free QA engineer.
And they care too. Fixing 8 out of 24 bugs says so. And charging to fix product defects means they want to be around next year to charge you again.
The line "if you don't report it there is zero chance it will get fixed" got me going... my how things have changed. When I worked at Borland, it was "we are developers, we use the product, we know what the product needs"...
My soapbox? No, simply my observation. Personally, I'm a quality and feature set kind of guy who feels like if you get the quality right, the rest will naturally fall in line, and if a company can't put quality behind the name,.. well.
Now if you want soapbox, let me turn that to marketing. Nothing chaps me more than making a high end purchase from a company in the database tools business, only to receive continued "buy me" emails (instead of thank you emails or tell a freind), or open up my RAD Studio to a stale old screen that smells of advertising... what, they don't update the database that I bought the product, or detect I am a registered user and send some sort of goodwill cheer? I really don't need or want a BOGO with ***conditions, ebook, or freemium styles to get me to buy at the "El cheapo" store. I'm dropping multi thousands of dollars, and feel like I'm getting a offer for a free large soda, and then getting hammered for every nickle and dime at every turn (should I really need a magnifyer on the fine print of the product matrix to see what version I need for mobile development? - I loose trust quickly). Does the big countdown timer and ebook offer really work on a big product buy like this or does it just cheapen the whole experience? Did anyone else see the "what developers are saying" and calculate a total lameness factor? Did you want fries with that? Am I on the wrong planet?
OK. Soapbox off. Sorry about that. I coded for months straight without a day off (in Delphi 6 uggg) I finally just got off, and typed this on a phone??? That's messed up!! I need sleep!