• cst1992 (unregistered)

    TRWTF is the second sentence.

  • gleemonk (nodebb)

    Ah the default operation. I always manage to fuck up my new API by implementing default actions because they are convenient for the calling code. Then later when other code starts using the API, I have to worm my way around defaults that don't apply.

  • Siebel Develpoer (unregistered)

    As a highly paid Siebel consultant, I refused to accept this "Like most enterprise software packages, it’s complicated, incomprehensible, and any significant maintenance depends on very expensive consultants."

  • Nicholas "LB" Braden (github)

    That's an apt ERV.

  • Siebel Victim (unregistered) in reply to Siebel Develpoer

    You disagree with the characterization of "very expensive consultant" because sometimes you accidentally leave your clients with money, so clearly you're not expensive enough.

  • El Guaco (unregistered)

    So many layers of WTF.

    • Dev doesn't understand his own code base and the platform he is working on
    • API feature that accepts null as an argument to do something useful
    • Code doesn't implement sanity checks for search results
    • Deletion blindly accepts list of items for deletion ( the equivalent of rm -f in a database!)
    • Lack of unit testing to verify change resulted in desired behavior
    • No apparent peer review or oversight of changes
    • QA testing missed side-effect of change due to lack of regression testing
    • Management and devs ignored QA
  • Appalled (unregistered) in reply to Siebel Develpoer

    Then WHY are you so highly paid. Why can't I walk in and do it for half the price with a week of introduction. Might it be because "Like most enterprise software packages, it’s complicated and incomprehensible". If you refuse to accept that, than please tell is just WHY you are so highly paid? Just by your arrogance, I know beyond a shadow of a doubt that I'm 5 times the Coder and 10 times the System/Business Analyst that you will ever be.

  • _that_guy_ (unregistered)

    The real facepalm here Siebel. JS wasn't bad enough, so they had to make their own flavor?

  • _that_guy_ (unregistered) in reply to _that_guy_

    s/here Siebel/here is Siebel/

  • slavdude (nodebb)

    Siebel is still around? Who knew?

  • Ron Fox (google) in reply to cst1992

    Actually TRWTF is the first sentence.

  • LK (unregistered)

    My only exposure to Siebel is watching people try to update my Telstra account.

    Given how much they've all bitched about it it's no wonder i've got a poor impression :-)

  • Appalled (unregistered)

    What's worse than having a Siebel "Consultant" on site?

    Having one who's employed by Accenture.

  • Scarlet_Manuka (nodebb)

    Actually, you can do a lot of customisation in Siebel without outside help. My company uses an extensively customised Siebel system which is maintained (with regular enhancements) by an in-house group. It's very rare that we have to call in Siebel Expert Services [the official high powered tech support arm] to build stuff for us that we can't do ourselves.

  • Erik (unregistered)

    In Siebels defense, I don't think humans are able to create systems that are easy to understand AND complex. It just degrades as more and more people get involved...

    On the other hand, null is not a valid input! Why? Because all nulls are made equal, so you don't know where they came from. Was it intentional? Or is it the result of a failed operation elsewhere?

  • John Hermanson (google) in reply to slavdude

    Acquired by Oracle in 2005 and basically end-of-lifed at that point, but yeah there's still a few of us out there.

  • Me (unregistered)

    I would say that if you query with null Siebel will generate an SQL with XXX is null. At least in most versions since 2006. In an indexed id column this will probably lead to a full table scan and a poor perfomance. But should not update all items

Leave a comment on “Lines and Lines and Lines of Order Lines”

Log In or post as a guest

Replying to comment #:

« Return to Article