Comments on: Reasons NOT to use ClearCase

By: Reed Shilts

Reed Shilts — Sun, 29 Jan 2012 22:06:59 +0000

Big thumbs up!
I went from a Perforce project to a ClearCase project. What a joke – Perforce had its shortcomings, but ClearCase is an impediment to performing a “core competency” like “what files were checked in _with_ this file”.
And needing a full time administrator – give me a break. This is a TOOL to support the development people – needing an admin is so 1970’s.

A recent rant of mine….
http://reedteknik.wordpress.com/2011/08/11/gawd-i-hate-clearcase/

By: Eazy

Eazy — Thu, 16 Jun 2011 10:54:35 +0000

Actually, SayNoToClearCase has a very valid point “Who Has The Real Config Spec Defining The Tip Of Development”… Granted clearcase has some benefits, but overall, you have to understand that developers (those who use the tool everyday) are the people you want to listen to.. And tbh, I haven’t seen a good word about CC yet. I work in finance IT and as far as I know, two large IB’s are getting rid of it.

Companies make money on delivering software, not managing it – that should be an easy and intuitive task. In fact, one of the only things you should have to worry about, is when am I going to branch?

By: IHateClearCase

IHateClearCase — Wed, 09 Mar 2011 02:14:39 +0000

It is incredibly slow. It does unexpected things. The simplest tasks are made to be unbearably difficult. Eclipse integration sucks.

By: IHateClearCase

IHateClearCase — Wed, 09 Mar 2011 02:11:43 +0000

Another late night messing with ClearCase. It is the biggest steaming pile of s#$% software I have ever used. I spend more time dealing with ClearCase than writing code. It is absolutely ridiculous. I am an engineer with 17 years of experience and have used perforce, subversion, and others in the past. You would think any other SCM would be intuitive to me at this point. Well, no… I spend hours pouring over the ClearCase docs and still end up scratching my head. I’ve been dealing with ClearCase for a year now and I am the point person on my team for it. After a year of working with it, it is still completely unintuitive.

By: monty

monty — Wed, 09 Jun 2010 08:18:00 +0000

@SayNoToClearCase,

You have no idea what everyone talking abt. please take some rest

By: Nicam Energy

Nicam Energy — Sat, 17 Apr 2010 22:39:10 +0000

@SayNoToClearCase, I have a question for you.

Have you re-read the post before you submitted it?

You are a living contradiction my friend

By: Nicam Energy

Nicam Energy — Sat, 17 Apr 2010 22:35:14 +0000

I have learned that these negative posts are submitted by incompetent and troubled people, both developers and administrators.

I give you on piece of real example.

I have just started a new job in the city, the organization is using ClearCase.

You have no idea of the disgusting job the person that left has done.

Do no take it to the tool, kick in the arse those incompetent pricks.

You know the most ridicule fact? They paid that Muppet more than me.

By: SayNoToClearCase

SayNoToClearCase — Thu, 28 Jan 2010 16:37:15 +0000

The ability for developers to define ANY config specification in their development environment allows a dangerous form of mixing/matching branches/tags/timestamps of files in a view.

In a team of multiple developers, this results in the game “Who Has The Real Config Spec Defining The Tip Of Development”. Developers WILL try to workaround the merging/tagging system in source control to grab code from here, there, and everywhere in the repository by tailoring their config specs.

If you can’t define what the actual tip of development is, then you have no releasable product. No releasable product means may well induce contractual penalties when the related project misses its delivery dates. I’ve seen this situation nearly cost past employers millions in undelivered projects due to the ass-clownery that results.

This kind of obstacle also makes an excellent political game of “eliminate the developers and manager from the non-delivering project”.

Avoid jobs that require the use of ClearCase: it may just save you being laid off due to the ensuing politics.

SayNoToClearCase

By: Arbeitsverhinderungstool ClearCase : Zustandsforschung

Arbeitsverhinderungstool ClearCase : Zustandsforschung — Thu, 09 Jul 2009 09:48:32 +0000

[...] Features von ClearCase kann man in den beiden Artikeln ClearCase, making easy things hard und Reasons NOT to use ClearCase [...]

By: Garen

Garen — Thu, 28 May 2009 19:00:30 +0000

clearfsimport has been around for a long time and be used to import a lot of files into CC, although it’s not built into a context menu in CC Explorer. It is now in CCRC though.

Never had any big complaints with CC performance. If the project was large, simply used snapshot views.

Config-specs are a usability problem, and without atomic commits it’s hard to implement CI, which is my main complaint with CC.

And if I was going to use one of the new DVCS systems, I’d use Mercurial–which actually _works_ on platforms other than Linux. I don’t really care if git can run in 0.01 seconds rather than 0.1 for an operation I do once an hour.