> I think the cost of dumping Clearcase is so high that no individual
> project can afford to do it. So no one does. So you're stuck with it
> forever. In practice, the issue of it being a sunk cost never enters the
> discussion.
"It's never too late to throw out all the code and start over."
Pr
I think the cost of dumping Clearcase is so high that no individual
project can afford to do it. So no one does. So you're stuck with it
forever. In practice, the issue of it being a sunk cost never enters the
discussion.
The problem is that Clearcase is integrated into your builds, into
develope
>
> When your organization has a sunk cost, it's wise to recognize it as early
> as possible and move on. True, as a technical person it can be difficult
> to deal with situations like this because often management doesn't
> consider seriously the business acumen of technical people. But, honest
> "JOO" == James Olin Oden <[EMAIL PROTECTED]> writes:
>
> JOO> As it is though the current company I am working with has
> JOO> invested heavily in clearcase and so any solution would require
> JOO> it.
>
> Vladimir G. Ivanovic http://leonora.org/~vladimir:
> Precisely. Once yo
"JOO" == James Olin Oden <[EMAIL PROTECTED]> writes:
JOO> As it is though the current company I am working with has
JOO> invested heavily in clearcase and so any solution would require
JOO> it.
Precisely. Once you start with ClearCase, you're effectively locked into
a costly, proprietary s
