Replies

I'm not backpeddling. I read it, I thought it meant one thing, you thought it meant something else, I was right. Spend some time in an MS only shop you to will get the secret decoder wheel. As for "admitting error" what error is there to admit? That I grocked?! I also know that when we in MS shops work on a tiered system we don't do one tier then the next, the work is done in parallel, so it's kind of hard when to say "the GUI took this long". You know how long the project took, you know you worked on the GUI during the entire length of the project in some way or another. If it was a mistatement then why is it only you didn't get it?

Maybe we have different definitions of monolithic. The accounting project I worked on the DB was 45 megs on install, no data. As for maintaining it that was nothing, we spend about 2 hours outlining a recommended backup process which took about 20 minutes to implement in SQL and that was it. As for letting people look at the data that was through our application only, you could look at the raw data but it probably wouldn't make sense. Being a fully flushed accounting/ business process app there's tons of confidential data in there that only certain people should be looking at (like SSNs) and the security was via our app.

I'm not backpeddling.

You have not yet admitted that his original statement was, in fact, incorrect. A highly misleading exaggeration.

Think about it: he made an exaggerated claim about .NET's ability to migrate existing code, and instead of correcting his claim you insulted the fool who believed his claim.

Does this give you any insight into why the claims of .NET's success have to be questioned?

As far as data integrity -- as you said, there are things like SSN that must be hidden. Then there are things like 'home address and phone number' that should be available, but will not be accurate unless the users can easily update it themselves. And things like HR 'resource requests' (job openings) that will not be accurate unless maintained by the HR folks. And things like 'estimate to complete' and 'project variance' that can only be accurate if maintained by project managers.

And on, and on.

That's already the way it works. And we've found it works *best* that way, here.

Q. Do you admit that, as written, his original post (#17) was an exaggeration of .NET's ability to migrate code?

I'm sure it was an honest mistake. But he said something that was very clear, and it was not true.

Agreed?