• (cs) in reply to Anonymous
    Anonymous:
    Duct tape: heat resistant tape specifically designed for ducting and other high-heat applications.

    Duck tape: magic universal waterproof anything fixer.

    Get it right guys, you don't want end up with duct tape when you really need some duck tape.

    So you think those servers aren't pumping out a butt-load of heat? Just wait until your dedicated AC unit goes down.

  • (cs) in reply to mike
    mike:

    FYI: Donk tape is the tape you use to put over the mouths of pedants arguing about what to call a roll of tape.

    I thought that was called dork tape

  • jdw (unregistered) in reply to Kef Schecter
    Kef Schecter:
    Anonymous:
    Fun fact: that's what he told the music press once it came out so he wouldn't sound like a picky self-obsessed moron.

    Fun fact: random people on the internets know more about celebrities' motivations than people who actually know the people in question!

    SnopesHacker:
    Quis custodiet ipsos custodes?
    Ego illos custodiam. :)
    I don't like being a captcha-quoter, but mine is so appropriate this time: dolor.

    Dolor is what I feel reading your response. "Ego illos custodiam" is incorrect grammar. When you use the copula, you must use the predicate substantive. You must use nominativus, not accusativus.

    Okay, back to your regularly-scheduled commenting.

  • FuBar (unregistered) in reply to jdw
    jdw:
    I don't like being a captcha-quoter, but mine is so appropriate this time: dolor.

    Dolor is what I feel reading your response. "Ego illos custodiam" is incorrect grammar. When you use the copula, you must use the predicate substantive. You must use nominativus, not accusativus.

    Romanes eunt domus! Romanes eunt domus!

  • Matt (unregistered) in reply to highphilosopher
    highphilosopher:
    Anonymouse:
    So they only discovered this because they failed to put a whole freakin' rack of servers on a UPS? I thought planning for power problems was IT 101...

    No, ensuring job security is IT 101

    You're confusing IT with government unions.

  • Mark (unregistered)

    Silence is golden, duc[t|k] tape is silver.

  • (cs) in reply to avflinsch
    avflinsch:
    mike:

    FYI: Donk tape is the tape you use to put over the mouths of pedants arguing about what to call a roll of tape.

    I thought that was called dork tape

    A dork is a whale penis. Tape for a whale penis must be waterproof and very stretchy.

    You can get it in flesh tone so it isn't that noticeable.

  • Quirkafleeg (unregistered) in reply to luis.espinal
    luis.espinal:
    […] he had the right idea wrt to the SQL/script artifacts…
    “wrt to”, “PIN number” etc.

    Otherwise, I agree, VCS for the lot of them.

  • Some Wonk (unregistered)

    Whatever you do with duct tape, for the love of $entity don't use it on ducts: http://www.lbl.gov/Science-Articles/Archive/duct-tape-HVAC.html

  • (cs) in reply to Anonymous
    Anonymous:
    amischiefr:
    Anonymous:
    Duct tape: heat resistant tape specifically designed for ducting and other high-heat applications.

    Duck tape: magic universal waterproof anything fixer.

    Get it right guys, you don't want end up with duct tape when you really need some duck tape.

    Trolls get hungry too right? I'll feed one...

    interwebs:
    <snip>
    It's the same damn thing.
    If you say so, but don't come crying to me when you end up fixing the hydraulics of a 747 using duct tape instead of duck tape, then your plane explodes after taking off from a beach because you can't retract your landing gear and it rips off while you're trying to get home from the island you've been stranded on for three years. Just saying.

    Yeah, but what happened to the nuclear weapon?

  • Kef Schecter (unregistered) in reply to jdw

    [quote user="jdw"][quote user="SnopesHacker"]Quis custodiet ipsos custodes?[/quote] Ego illos custodiam. :)[/quote]I don't like being a captcha-quoter, but mine is so appropriate this time: dolor.

    Dolor is what I feel reading your response. "Ego illos custodiam" is incorrect grammar. When you use the copula, you must use the predicate substantive. You must use nominativus, not accusativus.[/quote]

    Sorry, but you're completely wrong. "Custodiam" here is the first-person singular future of "custodire", not the accusative of the noun "custodia". There is also no copula here, implied or otherwise.

    Quis custodiet ipsos custodes? - Who will watch the watchmen? Ego illos custodiam. - I shall watch them.

    Perhaps before you feel "dolor" at something, you should first make sure that you are actually right. :)

  • Buddy (unregistered) in reply to My Little Pony
    My Little Pony:
    Buddy:

    11 word sentence, each two letters:

    If it is to be, it is up to me.

    you mean in base 9?

    :) I was wondering if anyone would notice, and then come up with the solution!

  • EngleBart (unregistered) in reply to HenrikwL
    HenrikwL:
    Ah, I see someone has had a run-in with IBM ClearCase as well. *shivers*
    ClearCase is great if you use UCM with snapshots. I am sad that IBM killed ClearCase LT.

    I have been wanting to test drive SVN as well, but I guess I will have to that at home. The security side of SVN seemed like you would end up with one giant trigger to control all of your settings.

    Zips on a share work great for build snapshots!

    Visual Source Safe (Safe Source?) was the worst... TFS sounds a lot better.

  • your gibberish (unregistered)

    So most of you post a lot of gibberish out there - making geeky jokes is easy. Any realistic solutions?

  • (cs) in reply to your gibberish
    your gibberish:
    So most of you post a lot of gibberish out there - making geeky jokes is easy. Any realistic solutions?

    Solutions to what?

  • Anonymously Yours (unregistered)

    So you're back to silently deleting comments again? You're only inviting people to be critical of you rather than your work.

  • Buzz Killington (unregistered)

    Ok was it just me or was anyone else confused by this line?

    "Despite the consultant's hissy fit, upper management had seemingly caved to the consultant's demands, declaring the eSCM software as "business critical" and while there was technically no money budgeted for hardware, nor did anyone even have a project plan, it was to be the newest top priority."

    Despite? You mean the reason upper management caved was because of the hissy fit. Not despite it. I figured it meant the consultant was against it, but regardless of what he thought they went ahead with it anyway.

  • Barney (unregistered) in reply to luis.espinal
    luis.espinal:
    The manager sat back and laughed, "Heh heh. Yeah he wanted to store all our SQL and scripts in the eSCM. He got it all setup, but when we tried to use it was just too difficult so we stopped."

    Disregarding the diva-like stupidity of insisting for a completely different source control system over an already established one (SVN), the Van Halen guy actually tried to do the right think (version and store all SQL and script artifacts.)

    There are so many WTFs that are not exclusive of the Van Halen guys.

    1. Letting the guy act like a prima donna (typical business error.)
    2. Not being able to work with their SQL/script artifacts off a versioning system.
    3. Deciding to use zip files stored on someone's local box as an alternative.
    4. Not thinking of using what they had before (SVN) to do just that.
    5. Justin and Bryan not realizing the guy was gone until months passed
    • Couldn't they have asked anyone that worked with him?
    • Didn't they cc anyone when e-mailing Van Halen?
    • Who the heck leaves voice mails or knocks on doors but does not use e-mail for business communications?
    • How could his voice mail still work if he's gone?
    • Don't they have like, status meetings?
    • Why did they leave brown M&Ms backstage... err, not that.

    The guy was a prima donna fruit cake, but we gotta admit that at least he had the right idea wrt to the SQL/script artifacts... not that it excuses his other errors (or the errors of everyone else involved in this brown M&M debacle.)

    Yes buddy. You hit the real nail on the head. However because people like the hate the evil consultants so much they don't realize the real WTF was the company / developer culture all along, for all the reasons you mention.

    So a consultant comes in, demands what should be a baseline of source control and other systems, and then leaves when he realizes that they're a bunch of incompetent, lazy and stupid permy retards. Hmm that could have been me. Except instead of Subversion the client usually has an ancient version of Microsoft VSS and insists that it's never given them too much trouble.

    Yadda yadda yadda.

  • AnOldRelic (unregistered) in reply to Barney
    Barney:
    Yes buddy. You hit the real nail on the head. However because people like the hate the evil consultants so much they don't realize the real WTF was the company / developer culture all along, for all the reasons you mention.

    So a consultant comes in, demands what should be a baseline of source control and other systems, and then leaves when he realizes that they're a bunch of incompetent, lazy and stupid permy retards. Hmm that could have been me. Except instead of Subversion the client usually has an ancient version of Microsoft VSS and insists that it's never given them too much trouble.

    Yadda yadda yadda.

    Not all consultants are evil/terrible, but you have to admit, there are some pretty piss-poor examples out there. I mean - we had consultants here who, on an ASP.Net form, for "security purposes" disabled certain elements using Javascript. (Hint: To get around this "security," simply turn off Javascript in your browser.)

    Point: Generalization, both ways, sucks.

  • The Real Jason (unregistered) in reply to FuBar
    FuBar:
    jdw:
    I don't like being a captcha-quoter, but mine is so appropriate this time: dolor.

    Dolor is what I feel reading your response. "Ego illos custodiam" is incorrect grammar. When you use the copula, you must use the predicate substantive. You must use nominativus, not accusativus.

    Romanes eunt domus! Romanes eunt domus!

    Ramen Noodleous

    Shoot I wish I could say we have any sort of SCM, instead where I work we use the Source Control Shingle, colored tabs and version named folders. Hell even the dorks in the story do better than us by using compression!

  • David (unregistered)

    I want so badly to at least pretend like I haven't seen this exact scenario play out a thousand times over the years ...

    And people wonder why IT guys seem to be in a bad mood all the time ...

  • HenrikWL (unregistered) in reply to EngleBart
    EngleBart:
    ClearCase is great if you use UCM with snapshots.

    Unless, of course, you don't know the rediculously rigid workflow that UCM requires (because no one else knows it so no one can teach you) so that deliveries are fragile, fragile things more often than not thrown off by orphaned VOB objects (that you have no idea how became orphaned and have no idea how to prevent, again because no one really knows) for which you either need to call in an external "ClearCase expert" with VOB admin rights to fix or risk deadlocking the entire deliver operation trying to fix it yourself.

    I'm sure ClearCase is adequate provided the team gets enough training and VOB admins are readily available to assist when it is needed, but whichever way you swing it ClearCase is a tool first and foremost to satisfy the needs of executives and pencil pushers who curiously find it comforting to have big, enterprise-y systems delivered by Serious Men in fancy suits.

    And I'm sure that if you're working on some huge project with hundreds of millions of lines of code, with dozens of teams working from dozens of locations that maybe investing in ClearCase with the huge support apparatus it requires makes business sense.

    But for most projects, I'd recommend the following:

    svn checkout awesome code svn update; svn commit

    Or, even better:

    git pull awesome code git commit -a

  • tekhedd (unregistered) in reply to Crash Magnet
    Crash Magnet:
    So, doing nothing is better than using SourceSafe?

    Definitely. Fighting with its interface will waste your time, and when push comes to shove your data is very likely corrupt. At least when you do nothing you don't have the illusion of safety, and might take some precautions, like zipping up your changes once a week.

    Zip files are much better. With a directory full of date-stamped zip files and any off-the-shelf diff/merge tool, you're good to go. With SourceSafe, you're crying from the first check-in.

    Also, I have found that the metal tape that is for ducts (which is not what I think of when I think of duc[kt] tape) is great for affixing temperature sensors to various parts of your unwisely overclocked PC.

  • (cs)

    Maybe I'm slow today, but I don't get what the asset tag has to do with a network share. Unless the PCs are all named by asset tag, which is arguably one of the worse "logical" naming schemes out there since it conveys none of the info you usually care about when managing a PC (location, network segment, user, make, model, purpose...)

    The name scheme I've come to prefer for business use goes something like [division][office location][function][ID], e.g. FIN-NYC-FS-01 (finance division, NYC office, file server 01). When a user calls and tells me their network share on FIN-NYC-FS-01 is not responding, I know right away which field tech to have go kick it.

  • (cs) in reply to Anonymous
    Anonymous:
    ClutchDude:
    Fun fact: Van Halen actually put the M&M's clause into the contract to ensure that the concert runners had actually read through the contract and done everything according to spec.

    Van Halen's crew could tell real quick if they should double check the concert stage's setup if the M&M clause wasn't followed. It was especially useful to check before they unloaded and hooked up sound equipment that'd pop a circuit mid-show.

    Fun fact: that's what he told the music press once it came out so he wouldn't sound like a picky self-obsessed moron.

    As soon as you have a regular gig playing your nuts off for a bunch of unappreciative pricks, then you get to criticise what you view as a character flaw in an artistic genius.

  • PITA (unregistered) in reply to Kensey
    Kensey:
    Maybe I'm slow today, but I don't get what the asset tag has to do with a network share. Unless the PCs are all named by asset tag, which is arguably one of the worse "logical" naming schemes out there since it conveys none of the info you usually care about when managing a PC (location, network segment, user, make, model, purpose...)

    The name scheme I've come to prefer for business use goes something like [division][office location][function][ID], e.g. FIN-NYC-FS-01 (finance division, NYC office, file server 01). When a user calls and tells me their network share on FIN-NYC-FS-01 is not responding, I know right away which field tech to have go kick it.

    I think your emergency brake is on :)

  • Dan (unregistered) in reply to Anonymous
    Anonymous:
    If you say so, but don't come crying to me when you end up fixing the hydraulics of a 747 using duct tape instead of duck tape, then your plane explodes after taking off from a beach because you can't retract your landing gear and it rips off while you're trying to get home from the island you've been stranded on for three years. Just saying.

    And don't come crying to me when the hydraulic pressure ruptures the duck tape because its tensile/adhesive strength was inadequate to support it, or else the gear won't fully retract because you applied so much to strengthen the patch that there's not enough room left. Just saying.

  • Paula (unregistered)

    I like Diver Down the best. Little Guitars is very nice indeed.

  • Fedaykin (unregistered) in reply to Anonymous
    Anonymous:
    ClutchDude:
    Fun fact: Van Halen actually put the M&M's clause into the contract to ensure that the concert runners had actually read through the contract and done everything according to spec.

    Van Halen's crew could tell real quick if they should double check the concert stage's setup if the M&M clause wasn't followed. It was especially useful to check before they unloaded and hooked up sound equipment that'd pop a circuit mid-show.

    Fun fact: that's what he told the music press once it came out so he wouldn't sound like a picky self-obsessed moron.

    It's actually believable. I often put similar "coal mine canaries" in my code before QAQC. Toss in a few obvious but minor (and well documented) errors that don't prevent the QAQC folks from doing their job to make sure they are actually doing their job.

    It's a good way to test the testers -- and applicable to most any profession (e.g. writers/proofreaders, etc.)

    Is it kind of a dick move? Probably. Is it useful to make sure something is actually getting done (despite being probably dickish)? Certainly.

  • Izhido (unregistered)

    That could be readily solved if you outsourced expert IT consulting...

    ... from PANAMAAAAAA....!

    All right, all right, I'll show myself out... :(

  • Dongle (unregistered)

    Was it just me or were there too many consultants in there confusing things??

  • Bruce W (unregistered) in reply to Anonymous
    Anonymous:
    If you say so, but don't come crying to me when you end up fixing the hydraulics of a 747 using duct tape instead of duck tape, then your plane explodes after taking off from a beach because you can't retract your landing gear and it rips off while you're trying to get home from the island you've been stranded on for three years. Just saying.
    "I don't believe in a lot of things but I do believe in duck tape." Only thing good from the last episode of Lost.
  • Владмир (unregistered)

    What could possibly have been going through their heads, that they thought that after replacing SVN with eSCM, and not using eSCM, and after all the fussing everyone went through that they had to label eSCM as business critical to use it, they completely forgot about SVN and used a zip file with a spreadsheet after they dumped eSCM. That just screams WTF!

    CAPTCHA: genitus - What a unickus wishes he had.

  • glwtta (unregistered) in reply to DCRoss
    DCRoss:
    I read it in Snopes, so it must be true. And I can trust Snopes because Snopes tells me to. Trust the Snopes. The Snopes is your friend.

    Actually Snopes specifically tells you not to trust Snopes: http://www.snopes.com/lost/false.asp

    (Ok, what the fuck is Akismet and why does it think this is spam?)

  • deejayvee (unregistered) in reply to SteamBoat
    SteamBoat:
    A dork is a whale penis.

    Why do whales get a special name for their penis? Does any other animal? Are whales like insecure human men who name their penises?

  • Some Guy (unregistered) in reply to Crash Magnet
    Crash Magnet:
    So, doing nothing is better than using SourceSafe?
    Doing nothing means that you're always one bad edit away from losing everything - so you're going to be careful.

    Using Source Safe means there's a random number generator hooked up to the "corrupt source code" device, and no matter how careful you are, you're eventually going to be screwed.

    Therefore, "doing nothing" avoids a false sense of security.

    Crash Magnet:
    Look, I can respect your opinion of SourceSafe. But do you really want to make risky edits, delete one-of-a-kind files and drive down long blind allies with no possible way to get back to working code.
    Do you really want to make risky edits, delete one-of-a-kind files and drive down long blind allies with no way to know if your safety net has been frayed for the last 6 months and will fail the moment you need it?
    Crash Magnet:
    Or bite the bullet an use SouceSafe?
    If we could trust source safe to not corrupt those one-of-a-kind files you want to delete then we could get them back if we find we need them.

    Look, source code control is a no-brainer - you use it, or you're a moron. We all know this. But there's both commercial and open source alternatives that are far far superior to source "safe".

    And if my manager demanded I use it, I'ld do so, and be keeping my own backups anyway.

  • (cs) in reply to Bogolese
    Bogolese:
    summarise -- Japanese pizza doh?

    ROR!

  • (cs) in reply to EngleBart
    EngleBart:
    ClearCase is great if you are a complete fucktard.

    FTFY.

  • Vermis (unregistered) in reply to Matt Westwood
    Matt Westwood:
    As soon as you have a regular gig playing your nuts off for a bunch of unappreciative pricks, *then* you get to criticise what you view as a character flaw in an artistic genius.

    Well, what you say has merit, but we're talking about Van Halen here,.

  • Darius (unregistered) in reply to HenrikWL

    [quote user="HenrikWL"][quote user="EngleBart"]ClearCase is great if you use UCM with snapshots.[/quote]

    When our organisation considered ClearCase, the demonstration server did not install itself correctly and did not work and none of their consultants sent in to fix it could get it to work either.

    So our organisation bought it and we all got sent on a ClearCase training course.

    None of the training course workstations had working copies either, and the course provider could not make them or the server work, so the course was spent talking about what we would have seen if only ClearCase had been working.

  • (cs) in reply to Kensey
    Kensey:
    Maybe I'm slow today, but I don't get what the asset tag has to do with a network share.
    "All of it is on our shared drive" turned out to mean "I have set my computer to share [all or part of] my C: drive and it is all on there."
  • karp (unregistered) in reply to NoAstronomer
    NoAstronomer:
    Knux2:
    Hopefully the company has learned its lesson and "Won't Get Fooled Again."

    Best joke I've heard all year!

    Too bad "Won't Get Fooled Again" is by The Who.

    captha: transverbero. A verb dressed like a woman.

  • Y? (unregistered)

    Is CVS better than SourceSafe?

  • Harold von Finklestein (unregistered) in reply to Y?
    Y?:
    Is CVS better than SourceSafe?
    Mu.

    What would you prefer - a hammer made of glass, or frozen diarrhoea?

  • (cs) in reply to Y?
    Y?:
    Is CVS better than SourceSafe?
    Definitely. CVS won't fuck up your files when the disk gets full. It just won't accept any new commits. SourceSafe has a tendency to garble your files under certain circumstances.
  • Don't blame the devs - they are just the end users (unregistered) in reply to ShatteredArm
    ShatteredArm:
    Mr T:
    So, to summarise, the consultant did something sensible, then the developers did something awful because they found a sensible solution too hard to use.

    Bingo. Sounds like the consultant is the hero in this story. But this website has an obvious bias against consultants, so...

    TRWTF is that the consultant delivered something that was wholly unsuitable for the end-user audience.

    Maybe the devs did find it too hard to use. So what? The project should have included requirements gathering which got translated into project goals. To demonstrate the project had achieved its goals there should have been a thorough test pack that the devs had to step through to sign off user acceptance. If they had any difficulties during UAT then this should have triggered a proper training session to address the elements of the product that were not intuitive.

    Actually, forget my first paragraph. I now agree with those that said TRWTF was management; Management should never have allowed this consultant to deliver a badly structured project regardless of whether he was delivering a source control system or a holepunch.

  • BlackWasp (unregistered) in reply to mike
    mike:
    Big G:
    amischiefr:
    Anonymous:
    Duct tape: heat resistant tape specifically designed for ducting and other high-heat applications.

    Duck tape: magic universal waterproof anything fixer.

    Get it right guys, you don't want end up with duct tape when you really need some duck tape.

    Trolls get hungry too right? I'll feed one...

    interwebs:
    The first name for Duct Tape was DUCK. During World War II the U.S. Military needed a waterproof tape to keep the moisture out of ammunition cases. So, they enlisted the Johnson and Johnson Permacel Division to manufacture the tape. Because it was waterproof, everyone referred to it as “duck” tape (like water off a duck’s back). Military personnel discovered that the tape was good for lots more than keeping out water. They used it for Jeep repair, fixing stuff on their guns, strapping equipment to their clothing... the list is endless.

    After the War, the housing industry was booming and someone discovered that the tape was great for joining the heating and air conditioning duct work. So, the color was changed from army green to the silvery color we are familiar with today and people started to refer to it as “duct tape*.” Therefore, either name is appropriate.

    It's the same damn thing.

    Nope, there is a difference. The HVAC duct tape is more like heavy duty aluminum foil with really good adhesive. The "duck" tape won't work on ductwork. The heat will destroy it in a few months. If you need more evidence, check out both tapes at the hardware store.

    FYI: Donk tape is the tape you use to put over the mouths of pedants arguing about what to call a roll of tape.

    No, Donk Tape(R) is a brand name only. The generic term is Don't Tape. You can't just go selling Don't Tape and calling it Donk Tape. You would be risking litigation.

  • (cs) in reply to Kensey
    Kensey:
    Maybe I'm slow today, but I don't get what the asset tag has to do with a network share.
    Perhaps the asset tag was on a Zip drive that had to be plugged in? (That'd be another WTF if true, but stupidity does happen all too often.)
    Kensey:
    Unless the PCs are all named by asset tag, which is arguably one of the worse "logical" naming schemes out there since it conveys none of the info you usually care about when managing a PC (location, network segment, user, make, model, purpose...)
    The asset tag has the advantage of being unique to the device and never repeated. You can always map that to the location and all that other info using your asset management database.
    Kensey:
    The name scheme I've come to prefer for business use goes something like [division][office location][function][ID], e.g. FIN-NYC-FS-01 (finance division, NYC office, file server 01). When a user calls and tells me their network share on FIN-NYC-FS-01 is not responding, I know right away which field tech to have go kick it.
    So if some piece of kit gets reassigned (or worse still, not reassigned but just moved between offices) you've got to rename it and update everything that depends on the old name? Are you nuts?! You're mixing up identity with both attributes and roles. Far far simpler to just use a name that doesn't change when you update the place you've put it or what some people are using it for. And if you think that looking stuff up in an asset management DB is too hard, well, … words fail me.
  • littlebobbytables (unregistered)

    "So, doing nothing is better than using SourceSafe?"

    Most terminal diseases are better than Sourcesafe.

    It is mind poison.

  • Asset this (unregistered) in reply to Kensey

    The point was the asset tag itself, it's where it was. It was on the developer's tower. I.e. not a server, presumably not backed up or on a UPS.

Leave a comment on “It's Business Critical!”

Log In or post as a guest

Replying to comment #:

« Return to Article