3 ms·
I would think that depends on the type of commercial software - if, for example, it's used in a large bank where faulty software could screw up a few million cu
by stingblue 6y ago
I would think that depends on the type of commercial software - if, for example, it's used in a large bank where faulty software could screw up a few million customer accounts - anyone who rolls the dice with that will soon be jobless. THAT software (application, OS, utilities, etc.) is usually VERY well tested.
- BlargMcLarg 6y agoEven there, you can make the software work and be secure, and still get away with loads of maddening practices and making software that just barely does what it does, waiting for the customer to fund a feature. Is it a smart business move? Debatable (I'd argue overdelivering on a SaaS product also helps bring in new customers). From a moral standpoint, I find it incredibly difficult to justify penny pinching and filling hours with malpractices and bureaucracy. And for what it is worth: personal experience tells, a lot of customers are quite accepting of faulty software, as long as the damage can be reverted and minimized. Even those in finance. Wouldn't be the first time I see people casually solve a bug that caused millions worth of damage.