2 ms·
That's a technical solution to a psychological and organizational problem: when there should be no CLI in production, people still use it and get used to variou
by ivan_gammel 4y ago
That's a technical solution to a psychological and organizational problem: when there should be no CLI in production, people still use it and get used to various errors and confirmations so much, that they ignore the signs of a catastrophe. Technical solutions never work in such cases.
And then there's a regulatory problem: investors trust their money to businesses which have not earned that trust, because of whatever magical thinking that exists on this market. At least the company seems to be able to return the money, but will it be sanctioned for this failure? There should be a regulatory incentive to do better next time.
- pjc50 4y ago> no CLI in production It seems like this was in the "deploy to production" stage, and there has to be some mechanism for doing that. (It also seems unnecessarily complicated; I'd appreciate a plaintext explainer of what actually went wrong)
- ivan_gammel 4y agoNormally such deployment mechanism is one standard command that picks up a tested code, enriches it with environment configuration and rolls it out. This command rarely changes and should be the same as deployment to pre-production or staging. This command is usually executed from a CI tool via a button click and requires only user credentials as an input. Any changes to production must be tested before release. They did not do it.