• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Reply to: Found a bug ....

Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Found a bug ...."

Collapse

  • Cyberman
    replied
    Originally posted by DimPrawn View Post
    Sadly the new system allowed reporting on past data, so a like-for-like report could be produced against the old data and compared to archived reports.

    There was no way the head of dept was going to admit the reports for the last 5+ years were wrong as he was the one that approved and signed off the old system as fit for purpose.



    Then based on date selected, if for an archived report prior to the new system, invoke the older code logic. The archived reports will then match up, but for current reports the data will be the new correct version.

    Leave a comment:


  • NoddY
    replied
    Blame IT - last refuge of the rascal.

    Leave a comment:


  • DimPrawn
    replied
    Originally posted by Moscow Mule View Post
    Staggering.

    He should have got you to program a subtle date based change which would bring the reports in line over an 18 month period. Directors really would have no chance then...

    Sadly the new system allowed reporting on past data, so a like-for-like report could be produced against the old data and compared to archived reports.

    There was no way the head of dept was going to admit the reports for the last 5+ years were wrong as he was the one that approved and signed off the old system as fit for purpose.

    Leave a comment:


  • HairyArsedBloke
    replied
    Originally posted by Moscow Mule View Post
    He should have got you to program a subtle date based change which would bring the reports in line over an 18 month period. Directors really would have no chance then...
    This is the first thing that comes to my mind too. Senior management, especially the board of directors need sensitive care and feeding. However, with all these increasing level of audits and legislation such things would get me sent back to pokey.

    Leave a comment:


  • EternalOptimist
    replied
    Originally posted by DimPrawn View Post
    I have been in exactly this situation with a FTSE 100 company.

    Background.

    Board of directors of this PLC received monthly reports from old IT system for many years showing share holdings, interested parties, beneficial owners and who is buying and selling. This report was key to board level decision making.

    My team was tasked with replacing this old system with a shiny new one from scratch.

    After migrating the old data and running the new reports, the figures were very different.

    Turns out the old system had several subtle bugs that resulted in misleading reports.


    Result

    Department head was tulipting himself. There was no way he could give them the new system as they would compare with old and see the big differences on the reports.

    Therefore I was tasked with building in similar "bugs" into the new systems logic to ensure the reports matched.

    The board of directors never new.
    LOL. reminds me of this story. They had a system for info, but secretly didnt trust it

    http://www.pointpark.edu/files/mba58...twonthewar.pdf



    Leave a comment:


  • Dow Jones
    replied
    BAs = bl00dy arshes

    Don't think it was a 'coding error' (would have been easily spotted) , more like an incorrect 'business scenario' (I am referring to Moody's here). I have seen many in my time.

    Leave a comment:


  • Moscow Mule
    replied
    Originally posted by DimPrawn View Post
    I have been in exactly this situation with a FTSE 100 company.

    Background.

    Board of directors of this PLC received monthly reports from old IT system for many years showing share holdings, interested parties, beneficial owners and who is buying and selling. This report was key to board level decision making.

    My team was tasked with replacing this old system with a shiny new one from scratch.

    After migrating the old data and running the new reports, the figures were very different.

    Turns out the old system had several subtle bugs that resulted in misleading reports.


    Result

    Department head was tulipting himself. There was no way he could give them the new system as they would compare with old and see the big differences on the reports.

    Therefore I was tasked with building in similar "bugs" into the new systems logic to ensure the reports matched.

    The board of directors never new.
    Staggering.

    He should have got you to program a subtle date based change which would bring the reports in line over an 18 month period. Directors really would have no chance then...

    Leave a comment:


  • DimPrawn
    replied
    I have been in exactly this situation with a FTSE 100 company.

    Background.

    Board of directors of this PLC received monthly reports from old IT system for many years showing share holdings, interested parties, beneficial owners and who is buying and selling. This report was key to board level decision making.

    My team was tasked with replacing this old system with a shiny new one from scratch.

    After migrating the old data and running the new reports, the figures were very different.

    Turns out the old system had several subtle bugs that resulted in misleading reports.


    Result

    Department head was tulipting himself. There was no way he could give them the new system as they would compare with old and see the big differences on the reports.

    Therefore I was tasked with building in similar "bugs" into the new systems logic to ensure the reports matched.

    The board of directors never new.

    Leave a comment:


  • DiscoStu
    replied
    Originally posted by Pondlife View Post
    Find the test script that the business signed off. Print it out and frame it.
    ^ His answer was way better than mine.

    Leave a comment:


  • oracleslave
    replied
    Originally posted by HairyArsedBloke View Post

    It makes me wonder; what would the members of the congregation do if they found a bug that, when corrected, would cause major disruption to a company’s financial position or even the markets?
    Never been in that situation but I think I would provide the information to the relevant permie and then let them decide what to do with it.

    Leave a comment:


  • Pondlife
    replied
    Originally posted by HairyArsedBloke View Post
    It makes me wonder; what would the members of the congregation do if they found a bug that, when corrected, would cause major disruption to a company’s financial position or even the markets?
    Find the test script that the business signed off. Print it out and frame it.

    Leave a comment:


  • DiscoStu
    replied
    Originally posted by HairyArsedBloke View Post
    Wasn’t me this time, but I sure know how this feels.


    FT: Moody’s error gave top ratings to debt products


    It makes me wonder; what would the members of the congregation do if they found a bug that, when corrected, would cause major disruption to a company’s financial position or even the markets?
    Depends how much I disliked the dev team...

    Leave a comment:


  • HairyArsedBloke
    started a topic Found a bug ....

    Found a bug ....

    Wasn’t me this time, but I sure know how this feels.

    Internal Moody’s documents seen by the FT show that some senior staff within the credit agency knew early in 2007 that products rated the previous year had received top-notch triple A ratings and that, after a computer coding error was corrected, their ratings should have been up to four notches lower.
    FT: Moody’s error gave top ratings to debt products


    It makes me wonder; what would the members of the congregation do if they found a bug that, when corrected, would cause major disruption to a company’s financial position or even the markets?

Working...
X