Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: TheBoy on 20 August 2018, 13:10:59
-
Gonna be a long day...
https://www.theregister.co.uk/2018/08/20/gatwick_fail/
For once, have to agree with the journo - what knob jockey decided on a non-resilient connection....
-
Probably launched as MVP :D
(Minium Viable Product - For us non-tech folk)
-
Probably launched as MVP :D
(Minium Viable Product - For us non-tech folk)
Never seen that term ever used in an project I've ever worked on, so just asked here. Software devs use it. Software devs are particularly "special", and rarely grasp the bigger picture.
We use terms like "half arsed", or "the next disaster" :P
-
Probably launched as MVP :D
(Minium Viable Product - For us non-tech folk)
Never seen that term ever used in an project I've ever worked on, so just asked here. Software devs use it. Software devs are particularly "special", and rarely grasp the bigger picture.
We use terms like "half arsed", or "the next disaster" :P
Oh I use those as well in team discussions, product like MVP. So do I, as it means I can strip half the requirements out on a new features, as not really needed.
Essentially launch with bare minimum, then use tracking/data to understanding building next feature and maybe A/B test that.
Can easily see how something like backup gets de-scoped, although I would have thought they would leave a manual entry mode / CMS mode for when the data fails.
When I used to work on Sky's Teletext stuff (iText) feeds would often fail or contain an error, I could dive in and manually change.
-
Oh I understand that in a dev environment, to cut time, because devs are notorious for not being able to meet timelines.
But this is a larger IT project, and whomever cut corners by not making a near-critical system's most unreliable component (its internet/cloud connection) non resilient should hopefully be out of a job by now.
-
Oh I understand that in a dev environment, to cut time, because devs are notorious for not being able to meet timelines.
But this is a larger IT project, and whomever cut corners by not making a near-critical system's most unreliable component (its internet/cloud connection) non resilient should hopefully be out of a job by now.
Bet they were promoted, as it saved the project money. :)
-
"So you're telling me this Cloud thing is always there?"
"Yes"
"It never goes down?"
"No, it's the cloud, isn't it, it can't go down"
"And it's secure?"
"Yeah, it's the cloud, isn't it, someone else makes it secure"
"And we don't need to worry about patching, upgrades, hardware lifetimes, warranties?"
"No, someone else takes care of all that, it's the cloud!"
"So we just move everything there?"
"Yeah, and we save billions!"
"Great. Do it. Congratulations you're now the SVP of IT."
(https://cdn-images-1.medium.com/max/1600/1*el4nHcOQdfHxzzcTC99jDw.png)
-
Much like when we moved to VOIP desk phones, when I was doing Text support. (8 years ago now!)
"So we are loosing our phones?"
"Yes, you get new VOIP ones, much better"
"What happens when network fails?"
"Network won't fail"
"But we could loose a switch or another component, what happens then"
"That won't happen"
"How can people call iText support, if the network is down and phones won't work"
"That cannot happen"
Fast forward 3 weeks, network fails. All phones go down for about 4 hours.
First call back in...
"Why did you not answer, been trying to contact you for ages?"
"How could we, phones don't ring when the network is down"
:D :D :D
-
;D ;D ;D Yep, that sounds about right.
"Network can't fail"
Much like..
"Titanic can't sink"
-
Yup. ;D ;D ;D
-
You know you are fixing a problem that should not exist, when to help resolve the issue you have to reconfigure the DNS entry on the desk phones display. :D :D ;D
-
One glitch and third world chaos is just around the corner :(
-
Off today :D
They're constantly recruiting IT people...
Be a couple more vacancies ::)
-
;D ;D ;D Yep, that sounds about right.
"Network can't fail"
Much like..
"Titanic can't sink"
When did this happen? :-\ :-\
.......and why am I always the last to know. :-\
-
They waited until you had set off in the taxi to come to the airport just so you could arrive in the midst of the carnage ::)
-
They waited until you had set off in the taxi to come to the airport just so you could arrive in the midst of the carnage ::)
He took a taxi to board the Titanic? Titanic was at the airport? Wos goin on?
-
His lordyship was complaining at being the last to find out about the days events... So I suggested that they waited to tell him... ::)
-
His lordyship was complaining at being the last to find out about the days events... So I suggested that they waited to tell him... ::)
His lordship had highlighted the part about the titanic sinking and made a funny about it .. ::)
-
Oh I understand that in a dev environment, to cut time, because devs are notorious for not being able to meet timelines.
But this is a larger IT project, and whomever cut corners by not making a near-critical system's most unreliable component (its internet/cloud connection) non resilient should hopefully be out of a job by now.
Bet they were promoted, as it saved the project money. :)
The age old saying in our company, "promoted to your level of incompetence".
When I first heard it, I thought it was amusing. The humour when I realised it was too close to the truth.
-
Shit floats ::)
-
Shit floats ::)
Sometimes ;)
-
The Gatwick Titanic aircraft project is progressing well triplex and quadruplex fly-by-wire flight control systems are so last year. Our lightweight simplex system saves on fibre optic cable weight, flight computer voting systems and redundant actuators. Those with any concerns, there aren't any, we have a proven track record of 100% reliability with our flight display boards that show these networks never fail. ::) :-[ ;D
Such a key system should be at least a dual system with different cable path routing, so Murphy's digger laying new drainage pipes can only take out one set of them at a time. ::) ::) ::)
-
Shit floats spreads ::)
Always! ;D
-
Oh I understand that in a dev environment, to cut time, because devs are notorious for not being able to meet timelines.
But this is a larger IT project, and whomever cut corners by not making a near-critical system's most unreliable component (its internet/cloud connection) non resilient should hopefully be out of a job by now.
Bet they were promoted, as it saved the project money. :)
The age old saying in our company, "promoted to your level of incompetence".
When I first heard it, I thought it was amusing. The humour when I realised it was too close to the truth.
The Peter Principle, circa 1969: https://en.wikipedia.org/wiki/Peter_principle
-
The Gatwick Titanic aircraft project is progressing well triplex and quadruplex fly-by-wire flight control systems are so last year. Our lightweight simplex system saves on fibre optic cable weight, flight computer voting systems and redundant actuators. Those with any concerns, there aren't any, we have a proven track record of 100% reliability with our flight display boards that show these networks never fail. ::) :-[ ;D
Such a key system should be at least a dual system with different cable path routing, so Murphy's digger laying new drainage pipes can only take out one set of them at a time. ::) ::) ::)
Like at a certain telecoms provider where (so the legend has it) they had all sorts of redundant links but a different Murphy decided it would be easier to bury them in the same duct. ::)
-
Like at a certain telecoms provider where (so the legend has it) they had all sorts of redundant links but a different Murphy decided it would be easier to bury them in the same duct. ::)
We had similar at one of our datacentres about 20yrs ago - diversely fed by 3 different fibres, the datacentre manager proudly told me... ...then I pissed on his bonfire by showing him that 2 went up one road together (admittedly in different ducts) to one exchange (another single point of failure), although the other was a completely separate route.
They soon rerouted one of them :D