Tempacc78534

5 ms·

1. 1.▲
   by Tempacc78534 8y ago

   It would way cheaper for them to verify their code than to probably follow these standards but bureaucracies are bureaucracies. Also, a little nitpicking in your write up but you should have also talked about type systems. They carry the sp
2. 2.▲
   by Tempacc78534 8y ago

   Not True. Agile Dev (according to me) means you are trying to specify what the customer want as you develop your code and not specify it right in the beginning. You can make changes to the specs when you are figuring things out. Also, you d
3. 3.▲
   by Tempacc78534 8y ago

   It's a cost benefit analysis, if the failure costs you more than verifying it then you will verify it. Since cost of verification is currently high, if you are not losing millions due to failure it doesn't make sense to verify you
4. 4.▲
   by Tempacc78534 8y ago

   You are right in general where the cost of failing is not that high, but consider software on flights, a pacemaker or (the best example everyone in FM quotes) a space mission. The cost of a small bug can cost you huge money/lifes. In t
5. 5.▲
   by Tempacc78534 8y ago

   The solution is to write partial specs. For example, if your client wants a piece of code which doesn't crash and sends a message over the network. You can write 2 partial specs i.e. 1) it doesn't crash 2) it sends a message over