Reply to: Welcome to the corporate culture

[minestrone]

( it was an Amercian company and they let the bobs design the updation system )

[minestrone]

Are you american?

I thought the tower of babel comment would have been enough for people to deduce the bobs were in charge of releases.

I don't and never have used the word updation with sincerity.

[Project Monkey]

Last bank gig I was at I was in charge of updations for 3 applications.

Each updation would take 2 days. Really all it took was overwriting a file and running an update on the DB.

Most of the work would involve writing the standard nonsensical update document which described each code change, hunting down people that should be involved in the updation, getting them committed to it ( usually by escalation to some manager ) then getting them there on time & online to do their minor part in the whole thing.

It was like building the tower of Babel 3 times every 2 weeks.

Are you american?

[vetran]

Bobs were in charge of all releases.

don't they introduced 3 major issues in production last week.

apparently I need to split 200GB of data up into 50MB chunks because they only use sharepoint.

though apart from the accents which are very thick so that you can't understand a word, the yanks make just as bad a job of it.

[original PM]

Bobs were in charge of all releases.

They generally are about as in charge of the releases like a tramp is in charge of their bowels.

[Dallas]

audit interface - nightmare, 20-somethings, not a shave between them
programme interface - old etonian buddies, not a sign-off between them
it interface - cheap devs with zero test resource

last CR was rejected because it was in the wrong template

and we are all about agile, thank the lord I am not a permie and dont give a Shhh

[minestrone]

Updation, ******* updation?!?!

Bobs were in charge of all releases.

[original PM]

Current project is involved with automating infrastructure provisioning stuff. Our first "product" will allow users to provision a Linux virtual server in about thirty minutes. This replaces a manual process which currently takes three weeks

The days of people who exist solely to pass forms around are numbered…

Ohh yes - we have a team called Audit who love their forms

Want something done?
You have to fill in a form
Why?
Audit....

But wait we started to challenge this and we created a form asking the person who asked us to fill in a form justifying why we had to fill in a form - and get this we insisted that the answer could not be 'Audit Purposes'

Well what do you know a year down the line and the audit team are back to a manageable size and actually do useful things rather than blindly putting in long winded processes.

So it can be done.......

[NickFitz]

Current project is involved with automating infrastructure provisioning stuff. Our first "product" will allow users to provision a Linux virtual server in about thirty minutes. This replaces a manual process which currently takes three weeks

The days of people who exist solely to pass forms around are numbered…

[GlenW]

Last bank gig I was at I was in charge of updations for 3 applications.

Each updation would take 2 days. Really all it took was overwriting a file and running an update on the DB.

Most of the work would involve writing the standard nonsensical update document which described each code change, hunting down people that should be involved in the updation, getting them committed to it ( usually by escalation to some manager ) then getting them there on time & online to do their minor part in the whole thing.

It was like building the tower of Babel 3 times every 2 weeks.

Updation, ******* updation?!?!

[PerfectStorm]

Involved in this kind of bureaucracy at the moment, change at glacial pace and subject to review. Another day, another dollar.

[tomtomagain]

Last bank gig I was at I was in charge of updations for 3 applications.

Each updation would take 2 days. Really all it took was overwriting a file and running an update on the DB.

Most of the work would involve writing the standard nonsensical update document which described each code change, hunting down people that should be involved in the updation, getting them committed to it ( usually by escalation to some manager ) then getting them there on time & online to do their minor part in the whole thing.

It was like building the tower of Babel 3 times every 2 weeks.

Been there. Got the (mental) scars!

The funny thing is after a few years you start to think "I was really productive today. I got a change done."

And then you have to slap yourself and say "We only copied a file from Server A to Server B".

[minestrone]

Last bank gig I was at I was in charge of updations for 3 applications.

Each updation would take 2 days. Really all it took was overwriting a file and running an update on the DB.

Most of the work would involve writing the standard nonsensical update document which described each code change, hunting down people that should be involved in the updation, getting them committed to it ( usually by escalation to some manager ) then getting them there on time & online to do their minor part in the whole thing.

It was like building the tower of Babel 3 times every 2 weeks.

[jmo21]

The team I work for at a bank is currently on the verge of losing their production access which they have used for deployments for the last few years.

They were pretty agile in terms of getting new stuff released, but only because for whatever reason they had the access to do so. It's about to become more difficult - rightly so of course, but if it was a happy medium fine, but it probably mean a total pain in the backside.

[minestrone]

It used to be annoying, then they moved all of these 'ticket fulfillers' offshore and that was that for me.

Hunting down someone with a 50 character name in Bangalore for 2 weeks to get a login for a dev database.