• bvs23bkv33 (unregistered)

    i know every tech to implement this at my place

  • LCrawford (unregistered)

    Rodger's machine cringed at the regression from MS SQL to Oracle, and tried to continue to use a real database instead of the cobbled-together hodge podge that is Oracle.

  • (nodebb) in reply to LCrawford

    I think Microsoft is also a little guilty of being overly protective of legacy features and language constructs. It's been 15 years now since they declared that all statements need a terminating semicolon, yet they're still not enforcing it, except for a couple of places.

  • Ryan (unregistered)

    That's the takeaway? My takeaway was to not give your developers unfettered access to production.

  • Bubba (unregistered)

    Who is this impudent woman that dares to post on remyporter.com ?!?!?

  • ooOOooGa (unregistered) in reply to Mr. TA

    Consider that the other option is to break backwards compatibility in the new version. That worked well for Python. Over 10 years later and the Python devs still have to maintain the 2.x version of Python as well as the latest Python 3.

    Works well enough for an open-source project. But when you have to pay all of the developers and insist on charging the customers, keeping backwards compatibility becomes a lot more important.

  • (nodebb) in reply to ooOOooGa

    I understand but they do have a backwards compatibility mode for this. A couple of changes in positive direction every major version is all it takes to keep the system clean in the long term, and is pretty manageable from upgradability and training perspective.

  • I can be a robot if you want me to be (unregistered) in reply to LCrawford

    You're calling MS SQL a real database?

  • Anon (unregistered) in reply to Ryan

    +1

    There types of accidents are way too easy to make, but are easy to mitigate against.

  • linepro (unregistered)

    MsSQL is just Sybase in drag.

    Now that was a real DBMs

    (ducks)

  • medievalist (unregistered)

    LCrawford is right, the true WTF is Oracle... once you've committed to a conversion effort, why not use a nice Open Source database with better security? It might you a few million dollars over the lifetime of the system.

  • DrPepper (unregistered)

    "meaning he had a copy still running on his local developer laptop, connected to the production queue". What sane business gives the developers direct access to production?

  • Barf4Eva (unregistered)

    The realWTF was this type of access to the production queue from a dev box...?

Leave a comment on “Death by Consumption”

Log In or post as a guest

Replying to comment #:

« Return to Article