Check out my collection of ClearCase posts and feel my pain. Continuing our latest adventures with ClearCase, (I haven’t worked on anything else since Wednesday) today we reviewed the situation. We had to roll back the changes made on Thursday, due to side-effects that appeared. (Basically square one). Currently there’s no real solution in sight,
So a minute after I’m tossed into the ClearCase mix here’s what happens: We are opening a channel to our partners in the company’s headquarters to work on the server. ClearCase being what it is, it looked like a small task but grew into a large one. Most of the chages were done by TesCom,
I’m not that crazy about this, but I’ll play along for awhile. Our flop of the ClearCase implementation has left us with an addiction for the implementation company. In the past I’ve reduced the dependency by transferring knowledge to IT. This worked and now we want to get rid of the on site support completely.
I really like working with smart people. Especially, when I hired them. And that means I like being right. Moving on… Smart people identify bad things and propose changes. They sometimes stubborn to a fault doing that. But that’s OK. The stubborn ones are willing to fight the system, or at least try to prove
So where do you put all the knowledge you collect? The easiest place is documents. The problem with those, is that the more knowledge you document, the less likely people are to read them. Today (another) argument I was involved in was regarding the use of dynamic/snapshot views in ClearCase. The methodology we have (due
No, it’s not about Microsoft. Today I found myself explaining arguments that are “organizational” and “administrative” although with some technical merit. The discussion was with one of the developers regarding piloting V7 of ClearCase, rather than using the 6.15 we have installed. (For the compassionate readers, leave condolences in the comments section). I’m not the