4 ms·
Doesn't matter how good you think are. If you write code professionally for long enough, you eventually experience an event like this first hand. It's an absolu
by h2s 13y ago
Doesn't matter how good you think are. If you write code professionally for long enough, you eventually experience an event like this first hand. It's an absolutely horrible experience for a developer.
- oconnore 13y agoBeing a professional developer is hard. That's why it's generally a high paying position, because you solve hard problems and are accountable for the results. So stop making excuses. An organization of this scale should be taking serious precautions (against code errors, bad hardware, malicious attacks, network problems, compiler bugs, cosmic ray induced bit errors, etc.) when building a credit card processor. If something truly extraordinary comes out to justify this problem, I may be sympathetic. But Occams razor suggests this was avoidable (through good process, not "I should have seen that off by one error").
- easytiger 13y agoI work in banking and when a piece of our code went down due to failing to handle load correctly during a market announcement the business was able to say they lost, in that 7 minute period ~£90k.