|
And have you saw that part of the list that full of real bugs but closed nevertheless?
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
Microsoft will never fix any bug that will cost them more money to fix it, then if they didn't. As long as it does not impact overall product satisfaction and use.
....um, so they close them, or leave them open, doesn't matter - never gonna get done.
Simples
|
|
|
|
|
Slacker007 wrote: Have you seen Microsoft's bug list?
I just can't resist.
The real question is has Microsoft?
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
|
|
|
|
|
Rage wrote: I wonder what my boss would say if I had not fixed a bug after 18 years. You fix every bug in your project? Is that the goal, delivering bug-free software? Or to make money?
It is not the kind of bug that hurts sales, does it? Is it the kind of bug that creates huge problems for users? No, doesn't sound like it.
If your project is as large as "Office" with the same turnover, you need a boss that can prioritize between real problems and stuff that is less important.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
|
While I get your point, I do not subscribe to it. It means that you end up fixing exclusively things that brings you money or really annoys the customer.
In our system, priority of bugs increase proportionally to the time they have been opened, so that eventually everything gets addressed.
|
|
|
|
|
Rage wrote: In our system, priority of bugs increase proportionally to the time they have been opened, so that eventually everything gets addressed. That's a choice.
Rage wrote: While I get your point, I do not subscribe to it. It means that you end up fixing exclusively things that brings you money or really annoys the customer. You end up wasting a lot of resources on bugs that aren't really bothering anybody. People will also start to call any RFC a "bug", since that means you'll be fixing it for free
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: People will also start to call any RFC a "bug" When did they ever stop?
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
The other thing to consider when a bug has been opened for so long is that people have come to expect it, and so what comes into play is whether or not changing the now-expected behavior will break things.
And that can translate into a real cost for customers.
MS has a long list of well-documented "bugs" they'll never fix for this reason.
|
|
|
|
|
|
Rage wrote: I wonder what my boss would say if I had not fixed a bug after 18 years.
He would say you could have rewritten the application with the fix in that time.
|
|
|
|
|
is no bug!
is pending feature.
other feature more important.
you try update.
if no then coming soon.
be patient, many feature to make.
ps: only clippy know when.
Signature ready for installation. Please Reboot now.
|
|
|
|
|
Rule relaxed about new trade regulations at first (7)
98.4% of statistics are made up on the spot.
modified 22-May-18 6:13am.
|
|
|
|
|
Control
relaxed = cool
New Trade Regulations at first = NTR
about = co-ntr-ol
|
|
|
|
|
Yep!
98.4% of statistics are made up on the spot.
|
|
|
|
|
Two Very good clues, as well as yesterdays
|
|
|
|
|
Thanks!
98.4% of statistics are made up on the spot.
|
|
|
|
|
So it's almost 8:15 and I'm still at home having breakfast.
Going to work in about 15 minutes.
I still have a pretty huge commute ahead of me, but at least it's not in the dead of night (well, maybe tonight as I'll be home late ).
This almost feels like the good old days (which lasted up to eight months ago) when I left for work at 9:30
In the meantime I've been leaving at 5:30
I hope never to leave before 8 again, but that's wishful thinking
|
|
|
|
|
Sander Rossel wrote: that's wishful thinking
Or mindful dreaming.
I am not the one who knocks. I never knock.
In fact, I hate knocking.
|
|
|
|
|
So stop working as a security guard.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I should stop working so damn far from home.
The reason I had to start so early is to avoid traffic.
I get past two big cities with a lot of traffic jams.
If I leave at the wrong time I'm looking at a 2+ hour commute easily
If I leave at the right time it's still well over an hour.
|
|
|
|
|
We have a requirement for business process automation and workflow solution. I am looking at number of tools but evaluating them is getting bit tedious. Any suggestions from anyone out there in corporate world using decent workflow and business process automation tool ?
Requirements are to be able to integrate with AD, have ability to call web services, run basic SQL query , send notification emails to users , design some basic data entry forms and delegate work to someone.
Zen and the art of software maintenance : rm -rf *
Maths is like love : a simple idea but it can get complicated.
|
|
|
|
|
I've used Windows Workflow Foundation in the past. It's straightforward enough to use and the fact that it integrates directly into Visual Studio is a major plus.
This space for rent
|
|
|
|
|
MS has an enterprise-level system called BizTalk. IIRC, it can do all of the things that you want, and is integrated with their development tools. They used to have demo disks of the server (the server would expire after 180 days, or some such).
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
If you have cash to burn, you could go with CA Technologies: they bought Automic last year. Automation[^]. Last place I worked at used their workflow automation tech and seemed pretty happy with it. It's just a *tad on the expensive side but it can do just about anything.
* the price is not cheap
if (Object.DividedByZero == true) { Universe.Implode(); }
|
|
|
|