Okay, so at Tudor's suggestion I have renamed my blog... The "The adjective plural-noun" formula apparently no good.
So instead how about my most frequently uttered phrase at work?
Today what I really hate is VISUAL SOURCE SAFE. ARGH! What a huge pile of steaming poo. And what's worse, the people who use it are rarely prepared to change to something else until way way too late (ie. the database corrupts, or as is the case at work right now-- it's effing useless over a WAN).
Of course, by that time their processes are totally entrenched in the SourceSafe model and you'd be hard pressed to find anyone who understands the concept of branching or merging. And OMG what's this about "concurrent" working models?
Anyways, the main problem we're seeing is a combination of stupidities where we _need_ to use Visual Studio to pull down the project out of SourceSafe since it has web projects within it that it needs to create. And part way through it just freaks out and stops downloading from the repository. And apparently there is no way to fix this, and the only way we can get the code is to go locally to Fredericton and get it there. VSS is NOT designed to work over a WAN, as it basically treats the repository as a local filesystem (it just happens to be on a network share, I guess it assumes) and opens files left, right and center. Pretty inefficient.
However, I _am_ able to get all the code when I just use the standalone client. But I can't open up the solution because it contains web projects, and for some reason it _has_ to go to sourcesafe to get those. ARGH! This is why people should NOT program via Wizards.
So, long story short, I am investigating two options. One is a client/server app called SourceOffSite that essentially is a proxy for VSS. The server runs on the LAN, and is a VSS client. The client runs on your machine (integrates with VisualStudio) and basically is a proper client/server protocol that is clean and mean. The messy shit happens over on the server side which should be local to the VSS repository.
The other option is to change the Web projects into DLL projects so that they can be opened without any freaky Visual Studio integration to the IIS web server. It means you have an extra step of set up initially (import the Web applications into the IIS configuration metabase) but damn, at least you can use a standalone client!
So, I promise I won't talk always about what I hate. But it'll most likely come up frequently. :)
Hope y'all are doing well out there on other coast. I miss all you guys!