[News] Mass IT Outage

[Me Atome]

Anyone buying Crowdstrike stock?

It's a risky strategy but I bet a few gamblers will.

 

[Eric the meek]

Us change mangers always were seen as an interfering bunch of busybodies stopping Trekkie wizzkids putting through their changes on the fly with impunity.

i had great reservations about automated changes that the original coding was presented to CAB ago be approved when only the Indian tekkies understood what was being shown, and then the shysters would subtly change the code before it went into production.

” so why did this automated change fail and take down our critical infrastructures “
” well you signed it off”
” so was there any changes made to the coding before it was implemented”
”no”
” are you sure”
“ yes”
” very sure”
” yes”
” so what is this line of code that wasn’t in the original change plan”
” erm…ask my supervisor”


does that sound familiar dealing with the sub continent?

I was once told on a CAB meeting not to ask a direct question to our Indian tekkies as culturally they couldn‘T lose face therefore will never give you a straight answer. This came from a senior technical manager at INFOSYS!

Not losing face sounds very familiar. My contracting years were a rich seam of entertainment.

On one project for HBOS, two Indians from Cognizant were moved in to sit amongst 6 experienced contractors including me, with the object of knowledge transfer. When their 3 month stint was over, I checked with all the others around them. Neither of them had asked anyone, one single question about the system, processes, business, nothing.

On a project for RBS, while system testing a new pension front end by the Indian software company ITD, we began to notice error messages, which appeared nowhere in the spec. In all, we came across a total of 41 new error messages, which hadn't been specified. They had made them all up. How do you even begin to tell them that this shouldn't be happening? How far back to basics do you have to go? If the spec is wrong, and you've identified an error condition that is not covered, then you raise it with the customer. You don't code round it.

Other anecdotes, including from Infosys, are also available on request.

 

[Springal]

It's a risky strategy but I bet a few gamblers will.

Inevitable drop on Friday but was hardly a bloodbath. Suggest investors & institutes aren’t to concerned about longer term impact

 

[raymondo]

Not losing face sounds very familiar. My contracting years were a rich seam of entertainment.

On one project for HBOS, two Indians from Cognizant were moved in to sit amongst 6 experienced contractors including me, with the object of knowledge transfer. When their 3 month stint was over, I checked with all the others around them. Neither of them had asked anyone, one single question about the system, processes, business, nothing.

On a project for RBS, while system testing a new pension front end by the Indian software company ITD, we began to notice error messages, which appeared nowhere in the spec. In all, we came across a total of 41 new error messages, which hadn't been specified. They had made them all up. How do you even begin to tell them that this shouldn't be happening? How far back to basics do you have to go? If the spec is wrong, and you've identified an error condition that is not covered, then you raise it with the customer. You don't code round it.

Other anecdotes, including from Infosys, are also available on request.

But they were cheap, and not on the headcount, so companies liked that. Whether or not it was (is?) cost effective was another question ...as your anecdote suggests.

 

[Washie]

Having a look at their stocks, stock prices fell by $34 the same week this happened. Monday stock prices were 377, this dropped to 343 on Thursday. This then kicked off on Friday. Did someone know?

 

[tedebear]

Not losing face sounds very familiar. My contracting years were a rich seam of entertainment.

On one project for HBOS, two Indians from Cognizant were moved in to sit amongst 6 experienced contractors including me, with the object of knowledge transfer. When their 3 month stint was over, I checked with all the others around them. Neither of them had asked anyone, one single question about the system, processes, business, nothing.

On a project for RBS, while system testing a new pension front end by the Indian software company ITD, we began to notice error messages, which appeared nowhere in the spec. In all, we came across a total of 41 new error messages, which hadn't been specified. They had made them all up. How do you even begin to tell them that this shouldn't be happening? How far back to basics do you have to go? If the spec is wrong, and you've identified an error condition that is not covered, then you raise it with the customer. You don't code round it.

Other anecdotes, including from Infosys, are also available on request.

I have a small list I could add too from Infosys including the “lower environment had different data“…type ones…

 

[Bozza]

Having a look at their stocks, stock prices fell by $34 the same week this happened. Monday stock prices were 377, this dropped to 343 on Thursday. This then kicked off on Friday. Did someone know?

Most major tech stocks, as well as the Nasdaq Composite itself, trended down over Monday to Thursday last week.

 

[Eric the meek]

I have a small list I could add too from Infosys including the “lower environment had different data“…type ones…

They sent a team of programmers (they were still called programmers in 2004) over from India, to take the jobs of two permies and two contractors here in Brighton.
The project was to maintain a myriad of standalone telco billing systems written in French PL/1, in and out of 150 DB2 tables, while fielding a daily succession of support requests from French users.

One of their questions was 'who is going to do the analysis?'. Our answer was 'you are'. Infosys had been economical with the truth with them. We had all left by the time the shit had hit the fan.

 

[Eric the meek]

I hope no-one took a punt on Crowdstrike shares on Friday.

Today, they are down another 11%.

 

[Bry Nylon]

The project was to maintain a myriad of standalone telco billing systems written in French PL/1, in and out of 150 DB2 tables, while fielding a daily succession of support requests from French users.

Travail de cinq minutes

 

[Tom Hark Preston Park]

Utter utter wankers

CrowdStrike backlash over $10 apology voucher for IT chaos

Cybersecurity firm is branded a "clown show" for gesture after an update caused widespread disruption.

www.bbc.co.uk