4 ms·

> Any conversation at all about how to avoid the legal issues/being sued out of existence? I share your concern, but maybe just sort, uh, :) worry about that

by sown 13y ago

> Any conversation at all about how to avoid the legal issues/being sued out of existence? I share your concern, but maybe just sort, uh, :) worry about that part later? It could prove to be fatal but it'll be neat to at least see? I mean, at least quick enough to get a prototype together and then later-on the avionics level of code auditing would take place. I've worked with former and current avionics engineers before, whom worked with Ada on fighter aircraft or civilian jets. It seems like a few lines of code per day is typical.

HeyLaughingBoy 13y ago
A point of reference here before the onslaught of "they must be crappy coders if they're that slow" remarks begins. A few LOC/day rate is generally accepted to be the overall rate of development from Requirements through Final Verification/Validation. That is, you may write a product of 10kloc in just a few months of coding, but the entire software aspects of the project actually took about 2.5 years to complete. I don't do avionics (though it sounds like more fun. Greener grass on that side, etc...), but this is the way we measure LOC in medical devices. To your other point, well, that's easy to say until the people killed are your loved ones. No company that plans to stay in business (or its officers out of jail) can afford to be blase about killing its customers.
- sown 13y ago
  > A few LOC/day rate is generally accepted to be the overall rate of development from Requirements through Final Verification/Validation. That is, you may write a product of 10kloc in just a few months of coding, but the entire software aspects of the project actually took about 2.5 years to complete. I probably should have mentioned that in my original post. :) Yes, they do lots of verification and auditing for any kind of code like that. This includes things like NASA TDRSS, space shuttle fuel flow regulators, etc. The sort of thing where people might die if an exception isn't caught. They don't necessarily want super-creative worker types itching to break rules, even if the system they are working on is indeed new and perhaps revolutionary. Things like the F35 JSF, etc.

by sown 13y ago

HeyLaughingBoy 13y ago

A point of reference here before the onslaught of "they must be crappy coders if they're that slow" remarks begins. A few LOC/day rate is generally accepted to be the overall rate of development from Requirements through Final Verification/Validation. That is, you may write a product of 10kloc in just a few months of coding, but the entire software aspects of the project actually took about 2.5 years to complete. I don't do avionics (though it sounds like more fun. Greener grass on that side, etc...), but this is the way we measure LOC in medical devices. To your other point, well, that's easy to say until the people killed are your loved ones. No company that plans to stay in business (or its officers out of jail) can afford to be blase about killing its customers.

sown 13y ago
> A few LOC/day rate is generally accepted to be the overall rate of development from Requirements through Final Verification/Validation. That is, you may write a product of 10kloc in just a few months of coding, but the entire software aspects of the project actually took about 2.5 years to complete. I probably should have mentioned that in my original post. :) Yes, they do lots of verification and auditing for any kind of code like that. This includes things like NASA TDRSS, space shuttle fuel flow regulators, etc. The sort of thing where people might die if an exception isn't caught. They don't necessarily want super-creative worker types itching to break rules, even if the system they are working on is indeed new and perhaps revolutionary. Things like the F35 JSF, etc.