• (cs) in reply to icelava
    icelava:

    "I made a makefile once in college; they're more trouble than they're worth."

    It is this very trait that proves to be the downfall of humanity. The stubborn ability to remain with, or should it be the inept disability to escape from, one single narrow-minded way of doing things with such a low-value single-sentence logic. Such mis-enforcements produce increasingly damaging results as the people are stationed higher up the ladder of power. It is quite amazing to witness how irrational people really are, evidenced by unqualified individuals placed at various stations of responsibilities.

    PS - nice CAPTCHA word there... LOL

    Sometimes all it takes is a bit of monetary pressure. My boss hated AMDs with a passion for years, since the days of Athlons and shitty, shitty, crash-prone Via chipsets, and for the first year and a half I worked there wouldn't entertain the thought of buying them. But eventually price differences won out, I got him to buy a few (both servers and workstations), and they've been working great so far. =D Thank God ATI and Nvidia make most of the AMD chipsets now.
     

  • (cs) in reply to foxyshadis

    Anybody know Serena Dimensions? I'm just curious because the managers in the company I work for swear by it and all the developers who have to actually use it only have swear-words for it.

  • Anonymous Merge Day Fan (unregistered)

    "I made a makefile once in college; they're more trouble than they're worth."

     No one can possibly be that stupid.

  • lostlogic (unregistered) in reply to Fran
    Anonymous:

    "Ok so Accurev has branches, can merge between them, but since it forces you to do it often you don't realize that you're working with branches and are therefore happy."

     Let's see...

    No mass merging...

    Code shared between multiple versions without re-coding...

    Conflict resolution against multiple baselines (instead of one at a time)...

    Ability to see potential conflicts not only between streams but even between two developer's seperate workspaces and deal with it ahead of time...

    No merging at all beyond development...

     By God you're right!  I am happy :)

    For whatever reason, you seem to like Accurev -- I don't know how they brainwashed you exactly, but ouch.

    One of my favorite Accurev behaviors is what it does if I modify a few files in my workspace, keep them, then rebase my workspace to another stream with different basis versions of those files and finally promote those files.  Now, any _sane_ VCS would tell me that what I've just done causes a conflict _or_ would automagically merge the differences between the two parent streams into my files and tell me about it.  Accurev does not.  It silently lets me promote my kept versions, INCLUDING the WRONG versions of the basis file.

    Did I mention the work-or-the-devil inconsistency in the CLI?  How about there's now way to see in a single output set the differences of a single transaction (or with anything less than a 100 line perl script afaics)?  How about someone telling me how to back out a specific transaction and not _every_ transaction that has followed it?  Tell me with Accurev how I might check out and keep up-to-date on a project without having to create a workspace?  This tool has increased my daily pain level more than any other change since I've worked at my current company.  I hate it with the fiery passion of a thousand burning deaths.

  • annoynimous (unregistered)

    So i wonder, why didn't Jim just finish his package, make it do the work and drink coffee with genios-and-dull grim all the day through ? Afterall he could pretend that this was plugin to WinWord, the editor absolutely needed to manually edit PATHs to those new packages :-)

  • AccurevHater (unregistered) in reply to lostlogic
    Anonymous:
    Anonymous:

    "Ok so Accurev has branches, can merge between them, but since it forces you to do it often you don't realize that you're working with branches and are therefore happy."

     Let's see...

    No mass merging...

    Code shared between multiple versions without re-coding...

    Conflict resolution against multiple baselines (instead of one at a time)...

    Ability to see potential conflicts not only between streams but even between two developer's seperate workspaces and deal with it ahead of time...

    No merging at all beyond development...

     By God you're right!  I am happy :)

    For whatever reason, you seem to like Accurev -- I don't know how they brainwashed you exactly, but ouch.

    One of my favorite Accurev behaviors is what it does if I modify a few files in my workspace, keep them, then rebase my workspace to another stream with different basis versions of those files and finally promote those files.  Now, any _sane_ VCS would tell me that what I've just done causes a conflict _or_ would automagically merge the differences between the two parent streams into my files and tell me about it.  Accurev does not.  It silently lets me promote my kept versions, INCLUDING the WRONG versions of the basis file.

    Did I mention the work-or-the-devil inconsistency in the CLI?  How about there's now way to see in a single output set the differences of a single transaction (or with anything less than a 100 line perl script afaics)?  How about someone telling me how to back out a specific transaction and not _every_ transaction that has followed it?  Tell me with Accurev how I might check out and keep up-to-date on a project without having to create a workspace?  This tool has increased my daily pain level more than any other change since I've worked at my current company.  I hate it with the fiery passion of a thousand burning deaths.

     Forget silently promoting. How about the fact that it silently fails to update.
    Kept/Anchored/Default Group == WTF???

    There should be a daily wtf just based on accurev.

    It could be a week long look at POS concepts that somehow people are brainwashed to use.

    A line in the article made me laugh: "They could now model their source control after their development model"

    That's what a coworker told me about Accurev.
     

  • (cs) in reply to AccurevHater

    I think the part of your email that stands out the most is where you say "That's what a co-worker told me about AccuRev".  No one has brainwashed me because I currently use the product at my company and it's great.  In fact, we have about 300 people using the same depot (database) in the US and India.  I've never found myself wondering what it does or why it does it.  It makes me a little uncomfortable that there are developers out there who are somehow confused by a product like this.  I hope I'm not using software developed by your company.

  • (cs) in reply to AccurevHater
    Anonymous:
    Anonymous:
    Anonymous:

    "Ok so Accurev has branches, can merge between them, but since it forces you to do it often you don't realize that you're working with branches and are therefore happy."

     Let's see...

    No mass merging...

    Code shared between multiple versions without re-coding...

    Conflict resolution against multiple baselines (instead of one at a time)...

    Ability to see potential conflicts not only between streams but even between two developer's seperate workspaces and deal with it ahead of time...

    No merging at all beyond development...

     By God you're right!  I am happy :)

    For whatever reason, you seem to like Accurev -- I don't know how they brainwashed you exactly, but ouch.

    One of my favorite Accurev behaviors is what it does if I modify a few files in my workspace, keep them, then rebase my workspace to another stream with different basis versions of those files and finally promote those files.  Now, any _sane_ VCS would tell me that what I've just done causes a conflict _or_ would automagically merge the differences between the two parent streams into my files and tell me about it.  Accurev does not.  It silently lets me promote my kept versions, INCLUDING the WRONG versions of the basis file.

    Did I mention the work-or-the-devil inconsistency in the CLI?  How about there's now way to see in a single output set the differences of a single transaction (or with anything less than a 100 line perl script afaics)?  How about someone telling me how to back out a specific transaction and not _every_ transaction that has followed it?  Tell me with Accurev how I might check out and keep up-to-date on a project without having to create a workspace?  This tool has increased my daily pain level more than any other change since I've worked at my current company.  I hate it with the fiery passion of a thousand burning deaths.

     Forget silently promoting. How about the fact that it silently fails to update.
    Kept/Anchored/Default Group == WTF???

    There should be a daily wtf just based on accurev.

    It could be a week long look at POS concepts that somehow people are brainwashed to use.

    A line in the article made me laugh: "They could now model their source control after their development model"

    That's what a coworker told me about Accurev.
     

    What do you not understand about Kept/Anchored/Default Group?  It sounds like you dont understand how to use the tool.

  • Nick (unregistered) in reply to rmg66
    rmg66:
    Shut up you!

    I like'em long.

    That's what she said.

  • Sumireko (unregistered)

    "...and more to do with the fact that Big Tech is known throughout the industry for making ... errr, how do I put this nicely ... marginally functional software products with user interfaces so absurdly bad that describing them as an amalgamation of the worst of the Pop-up Potpourri would actually be a compliment."

    It's okay, you can say Lotus. We all know it. And since this is an older article, I'll link to a "debunking" (I guess that's what you'd call it) of Lotus Notes (which Lotus is most infamous for): http://hallofshame.gp.co.at/index.php?file=lotus.htm&mode=original

  • Greg (unregistered) in reply to JD

    Add to that the fact that the entire build process stops dead on the 1st error (syntaxical or otherwise) encountered. Think 1,2039,404 errors in the build... 1,2039,404 errors! Take one down, patch it around, and there's 1,2039,403 errors in the build. 1,2039,403 errors in the build, 1,2039,403 errors! Take one down, patch it around, and there's 1,2039,402 errors in the build!... yeah... i had a few errors like that.

  • Anonym (unregistered)

    It's 2020, and our company was doing that for last 15 years, until I (I was new back then) and we other said STOP. And we migrated to GIT over three months... And now we have no conflicts. Its depressing...

  • DNP Capstone Project Writers (unregistered)

    Great post! Seeking professional help with your DNP capstone project? Simply click here: https://www.dnpcapstoneprojecthelp.com/

  • adamsmith104064 (unregistered)
    Comment held for moderation.
  • Razia Sultana Remi (unregistered)
    Comment held for moderation.

Leave a comment on “Happy Merge Day!”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article