6 ms·
Interesting, I always thought that spec-first and rigorous testing methodologies came from limitations in technology. For example without the capacity for const
by paulryanrogers 8y ago
Interesting, I always thought that spec-first and rigorous testing methodologies came from limitations in technology. For example without the capacity for constant updates software had to be as close to perfect and bug free as practical before distribution. I cannot imagine doing agile on a widely distributed software project as it is done today with games and their day-one patches.
EDIT: rephrasing for clarity
- whatshisface 8y ago>without the capacity for constant updates software had to be as close to perfect and bug free as practical before distribution In some cases, there is a downside to incorrect behavior that is worse than "oops we'll have to patch it." This category includes anything that handles money, industrial equipment, scientific data, or anything that isn't a computer game or adtech.
- prevedmedved 8y agoAdtech handles money. It's financial software that also needs to be (soft) real-time. It's harder than the usual money software.
- AstralStorm 8y agoAdtech loses income, not money. There is a vast difference. Additionally you can have rollbacks - strategy applied by many banks when things break. Funny enough, safe reverts and rollbacks require specialized up front design, it does not happen on its own. Safe automatic updates with no state loss? Same.
- lmm 8y ago> Adtech loses income, not money. There is a vast difference. Placing bids is (potentially) spending money. A bug in your adtech platform can absolutely bankrupt you in the very direct way of spending more money than you have.