|
Originally Posted by word302
(Post 3992085)
I highly doubt Crew Access runs on the same servers as the company’s operating software.
we’d be easy #3 and 6.5% profit sharing if it wasn’t for the IT meltdowns now we are #4 and a mesly 3% due to the company’s inability to have woking IT infrastructure. Their incompetence cost all us thousands of dollars on our PBP |
Originally Posted by Jetlikespeed
(Post 3992097)
let’s not put anything past them after 2 massive IT failures and a smaller one last month where people could not log into their Alaska air mileage accounts
we’d be easy #3 and 6.5% profit sharing if it wasn’t for the IT meltdowns now we are #4 and a mesly 3% due to the company’s inability to have woking IT infrastructure. Their incompetence cost all us thousands of dollars on our PBP |
Originally Posted by PetRock
(Post 3992214)
An operational force we have zero control over no less.
|
Originally Posted by WYSIWYG
(Post 3993662)
Can not believe that heads didn’t roll, especially after the second IT meltdown and millions of dollars lost !
|
Originally Posted by WYSIWYG
(Post 3993662)
Can not believe that heads didn’t roll, especially after the second IT meltdown and millions of dollars lost !
That's very bad news for the IT leadership, basically they are not trusted. I'm assuming there will be some turnover there, but you have to be careful about how you terminate critical IT people lol... better to ease them out on mutually agreeable terms. If you just have security escort them out the front door, they might forget to give you that extra bit-level encryption key they put on the main hard-drive array :eek: IT staff is like IT hardware... if you operate with thin backups (I assume they do) you need to be very careful about disruption. Tech world is full of stories along those lines. Best one was a dude at startup who began as a contractor building their core systems, during which time he licensed to the company some code that he had developed previously and owned as IP. The license continued for many years, for a trivial amount that accounting handled automatically. Eventually the company got big and they hired him as a full time employee. Management changed and they lost visibility on the fact that this guy owned a key foundation of their system. He had it setup to require a license key update on some periodicity, which he had been taking care of all along. They eventually fired him under contentious circumstances and hustled him out the door. Then their systems stopped working when the license didn't get updated. They had to pay the guy tens of millions, way more than it was normally worth, because the alternatives would have been to rebuild their code from scratch, or try to sue him which would take years if they even won. |
Originally Posted by rickair7777
(Post 3993715)
They brought in outside IT oversight afterwards.
That's very bad news for the IT leadership, basically they are not trusted. I'm assuming there will be some turnover there, but you have to be careful about how you terminate critical IT people lol... better to ease them out on mutually agreeable terms. If you just have security escort them out the front door, they might forget to give you that extra bit-level encryption key they put on the main hard-drive array :eek: IT staff is like IT hardware... if you operate with thin backups (I assume they do) you need to be very careful about disruption. Tech world is full of stories along those lines. Best one was a dude at startup who began as a contractor building their core systems, during which time he licensed to the company some code that he had developed previously and owned as IP. The license continued for many years, for a trivial amount that accounting handled automatically. Eventually the company got big and they hired him as a full time employee. Management changed and they lost visibility on the fact that this guy owned a key foundation of their system. He had it setup to require a license key update on some periodicity, which he had been taking care of all along. They eventually fired him under contentious circumstances and hustled him out the door. Then their systems stopped working when the license didn't get updated. They had to pay the guy tens of millions, way more than it was normally worth, because the alternatives would have been to rebuild their code from scratch, or try to sue him which would take years if they even won. |
Originally Posted by MrBogardi
(Post 3993884)
Isn’t that what caused one of the IT issues at ASA or HA? Laid off IT people?
|
Originally Posted by rickair7777
(Post 3993715)
Tech world is full of stories along those lines. Best one was a dude at startup who began as a contractor building their core systems, during which time he licensed to the company some code that he had developed previously and owned as IP. The license continued for many years, for a trivial amount that accounting handled automatically. Eventually the company got big and they hired him as a full time employee.
Management changed and they lost visibility on the fact that this guy owned a key foundation of their system. He had it setup to require a license key update on some periodicity, which he had been taking care of all along. They eventually fired him under contentious circumstances and hustled him out the door. Then their systems stopped working when the license didn't get updated. They had to pay the guy tens of millions, way more than it was normally worth, because the alternatives would have been to rebuild their code from scratch, or try to sue him which would take years if they even won. https://imgs.xkcd.com/comics/dependency.png |
| All times are GMT -8. The time now is 05:52 PM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands