The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I'm still waiting for a problem in VS2005 to get fixed: If you create an abstract control, you can't use the designer on concrete derived controls unless you create a concrete intermediary class.
I.e. this gives a designer error:
That would explain when VS went to the Dark Side: it just hit puberty and painted its UI black.
I just figured Microsoft hired the colorblind idiot from Apple who thinks black & white is sufficient for a modern display. Dumping the colors after the 2010 releases of everything was just stupid and reduced usability.
As much as it's something that millions have wished that it would do over the years, it's really hard to argue that it was ever a bug or even an omission.
Notepad exists as a simple DOS/Windows text-editor and has never tried to claim any grander purpose than that.
Those of us (lets be honest, pretty well all of us) who have at some point used it to work on files from sources other than its native OS, have, in truth, being using the product for something for which it was never intended.
Microsoft could, had they wished, have made a very strong - possible inarguable - case for not doing it but have instead taken a pragmatic line and decided to give us a feature that we've always wanted even though it could be classed as mission creep.
This is classic paradox: you see a lot of "fixes", "improvements", made during YEARS, but.... why the hell THIS ONE BUG is not fixed?! What should happen that company pays attention to your report? Why MOST ANNOYING bugs sit for years?? That's the question!
Why? Here is answers:
1. Company is a moron who needs money - they don't need "good product", they need "soldable product".
2. For the goal above, they need to roll out "new features", not "new bugfixes". Only that way you can say "Our product become more advanced - see that big red button!".
3. Lazy monkeys. They are everywhere! They sit in "tops", they sit in coding rooms, they are stupidly lazy and don't want to fix anything requiring more than 2 minutes. Bastards.
4. Company management just don't see what people wants! (because management is on Bahamas, ha-ha) They don't understand importance of problems - they are happy with just diagrams of LOC. INCOMPETENT MANAGERS are EVIL.
5. Incompetent developers are even more EVIL! All those "seniors", who come from India after 2-weeks programming courses - why you're hired?!! By "best dancer" competition??? What are you doing on positions, where YEARS of serious experience required? Why you touch "architectural" tasks? Who gave you keyboard, at last?
Incompetence is everywhere. We cannot run thru 'em. Support monkeys, developing stupids... they stop us. Just give me email of "big boss" and sure, next day all these pandas will be fired! Because incompetence is the road to the hell. Slow, far way, but always down. Sigh.........
Unfortunately I disagree with that "numerology" position! You're poisoned with "facebook".
If most people wants to drink cocktail on the beach, IT IS NOT a rule for government. If most people wants "big red button", it is not what you should do!
"Importance" of bug is a subject for professional evaluation. "Password leaking" is MUCH MORE important than spell error, but how many people reports "my password is leaked"?? Here the point!
Related your items:
#6: OK, at some moment it's not critical. But I never believe bug cannot be fixed for months!! If your team in a permanent deadline, you do it wrong way. If you create new bug, not fixing "old bug", you do it wrong. Time also matters! If you don't fix it for months, do you think I'll suffer? I'll choice ANOTHER PRODUCT and your company fails. THIS is what you should think when looking at age of bug/feature.
#7: it's not an excuse, it's BUG OF ARCHITECTURE. If you break code by fixing bug, fix another code too - it's just dependency! No spaghetti code!
#8: Nice excuse, but not. Mostly people report about real bug and I cannot believe you cannot reproduce if you investigate properly.
My #9: NEVER HIDE INFO from user! Nobody need your idiotic "something went wrong" - gimme exact line and exact reason for failure - believe me, it will lead to fix way faster, than "bug reports" nobody send thru clumsy "register first, please" forms.
And we should not forget about features: they are not bugs, but also not done for years! And it's also task of developer/manager to evaluate it not by "likes", but by "professional opinion". If you do something 99% of the time for 3 clicks, IT MUST be redesigned to do it in one click! "Usability" - not many people understand its importance.
Imagine a million developers reporting bugs like "The wibbly-thingamajig sometimes wobbles, with no obvious pattern; fix it now!!!1!". How much time will you spend "investigating" each report?
Sure, you might send a canned response asking for more information and a minimal reproduction of the problem. But 90% of the users won't bother responding; and of those that do, another 5% won't provide any of the information you asked for.
And then, when you close 95% of the tickets as "can't reproduce", the developers who submitted the reports will start claiming that you're "too lazy" to fix the problem, or suggesting that you're "incompetent".
TLDR: If you want a bug fixed, submit the kind of bug report you'd like to receive on one of your own products.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Last Visit: 31-Dec-99 19:00 Last Update: 27-Jan-21 1:52