RBS 'Computer Glitch'

[Scoobos]

I can add to bobspuds experiences.

At a major software house, we visited the devs offshore.
These are the creme de la creme of developers in that area.

Was reviewing some code, and saw an issue I was dealing with quite often.

Q. "What does the program do in <condition>"
A. "Ah, yes, that's invalid so the program will crash.
Q. "Why crash, why not error trap?"
A. "No one has asked for it".


And that, for me, is the problem - it's hard enough explaining requirements to devs in the same location - but you really shouldn't have to explain that CRASH is bad, error handle is OK.

[doodab]

you really shouldn't have to explain that CRASH is bad, error handle is OK.

And you probably shouldn't, or you're likely to end up with

try {
// some code
} catch (Exception e) {
log.info("Everything is A OK");
}

[Sysman]

As a shareholder in RBS I am appalled at this largesse with my money.

Is that "shareholder" as in

1. I can sell my shares if I want to
   
   OR
   
   
2. The gobmint are holding shares on my behalf?

[Diver]

Is that "shareholder" as in

1. I can sell my shares if I want to
   
   OR
   
   
2. The gobmint are holding shares on my behalf?

Or you've nicked one of their pens

[kmge]

So it seems that the dev bobs are getting cained for this, but, who at RBS signed off the change? Who was the person who put pen to paper at HQ to say "yep, happy to do a major change to our payment system".....? Have a go at the bobs all you like it's the person/change board members who said "yes" that should be up against a wall. Governance and Control. Process and Procedure. The basics seem to have been overlooked.

[Sysman]

So it seems that the dev bobs are getting cained for this, but, who at RBS signed off the change? Who was the person who put pen to paper at HQ to say "yep, happy to do a major change to our payment system".....? Have a go at the bobs all you like it's the person/change board members who said "yes" that should be up against a wall. Governance and Control. Process and Procedure. The basics seem to have been overlooked.

Which of these scenarios do you prefer?

RBS Senior Management Scenario #1:

"Our overnight batch systems run quietly and efficiently, because we have a staff of 1000+ skilled, experienced IT staff in the UK keeping it so".

RBS Senior Management Scenario #2:

"Our overnight batch systems run quietly and efficiently, so we can get rid of 1000+ expensive IT staff in the UK, and replace them by much cheapness in Chennai".

[NickFitz]

And you probably shouldn't, or you're likely to end up with

try {
// some code
} catch (Exception e) {
log.info("Everything is A OK");
}

ON ERROR RESUME NEXT

[kmge]

Which of these scenarios do you prefer?

RBS Senior Management Scenario #1:

"Our overnight batch systems run quietly and efficiently, because we have a staff of 1000+ skilled, experienced IT staff in the UK keeping it so".

RBS Senior Management Scenario #2:

"Our overnight batch systems run quietly and efficiently, so we can get rid of 1000+ expensive IT staff in the UK, and replace them by much cheapness in Chennai".

I don't mind which because I don't pay the bill. My point was, who in RBS has the Governance and Control. It doesn't matter who runs what and where. What matters is what Controls you have in place to make sure what gets done is right and when (because no matter where your work is done and by whom it will) it all goes a bit wrong it gets fixed, fast.

[bless 'em all]

So it seems that the dev bobs are getting cained for this, but, who at RBS signed off the change? Who was the person who put pen to paper at HQ to say "yep, happy to do a major change to our payment system".....? Have a go at the bobs all you like it's the person/change board members who said "yes" that should be up against a wall. Governance and Control. Process and Procedure. The basics seem to have been overlooked.

You assume they knew about it.

How many times have dev bunged through a 'little change' without going through the proper process? Never?

[MarillionFan]

ON ERROR RESUME NEXT

I knew it. That's what I use. I'm as good a programmer as Nick Fitz.