Off Sick Today...Got Me Thinking...

[Asher]

Originally posted by Japher
Yes.

So if there is a bug in the software exposed by a certain sequence of "inputs", so the 3 different runs, it may not be caught.

That's precisely why you get experienced specialists to write your software.

Arianne 5 went through extensive validation and testing for years when it launched. It even had a backup system incase the primary failed. The first system failed in flight due to an overflow error, so it fell to the backup. The backup had the same software, it failed too.

The result...


Japher, who developed the software at your company? Was it biochem people?

[Provost Harrison]

So you are completely infallible then Asher?

[Asher]

Not at all, but you're far more likely to get bugs when you've got amateurs with the experience and knowledge of software engineering as a Jr. High student developing critical software.

Responsible organizations get professionals with experience to write critical software.

[Japher]

So if there is a bug in the software exposed by a certain sequence of "inputs", so the 3 different runs, it may not be caught.

If there's a bug you expect your QA department to catch it during in processing and release testing. Believe it or not a good amount of product is lost to QA testing during every process run and on the final product in an amount and at a rate to ensure process consistency. I got a giant arse book on Acceptance Testing sitting on my desk to determine such things... Of course I don't understand it, QA is suppose to figure that stuff out. As well as stability to ensure shelf lifes.

Arianne 5 went through extensive validation and testing for years when it launched. It even had a backup system incase the primary failed. The first system failed in flight due to an overflow error, so it fell to the backup. The backup had the same software, it failed too.

That sucks.

Japher, who developed the software at your company? Was it biochem people?

No, the software is product of a collaboration between those who use it, those who designed the machines, and those who code it.

[Provost Harrison]

Originally posted by Asher
Not at all, but you're far more likely to get bugs when you've got amateurs with the experience and knowledge of software engineering as a Jr. High student developing critical software.

Responsible organizations get professionals with experience to write critical software.

People have to acquire experience somewhere in an in vivo environment.

[Asher]

Originally posted by Japher
No, the software is product of a collaboration between those who use it, those who designed the machines, and those who code it.

Precisely.

There are formal methods of software engineering using all 3 groups of people, and the people who use the machines or design the machines don't develop the software. They define the requirements and do acceptance testing.

[Asher]

Originally posted by Provost Harrison
People have to acquire experience somewhere in an in vivo environment.

Sure, you can start by contributing to something like Firefox and get relevant experience before you start designing critical software. Maybe get a job developing large, complex software to get your knowledge on par with a recent uni grad in software engineering, then you could do it.

[Provost Harrison]

Again, I must also remind you that I would be part of a team, remember, I said multidisciplinary? But you seem to so conveniently ignore this...I am one of the people who would have the most knowledge of what the software needs, plus my ability with computers, made me an ideal candidate for the project. I think you need to record this information down Asher before going off on one.

[Japher]

What's your problem then Asher? PH would be a good team member to a project that would design software applicable to a lab environment, would he not?

[Asher]

Originally posted by Japher
What's your problem then Asher? PH would be a good team member to a project that would design software applicable to a lab environment, would he not?

1) He mentioned he was sought after for his "IT skills"
2) He said "the position [he] was referring to would have involved development"
3) He made no effort to say he wasn't developing the software until now

[Japher]

1) If you have ever dealt with lab rats you would realize how narrow-minded they can be. Most of those guys know one thing, biology, and that is it. Having someone who would have some idea of computers would be very beneficial.

2) Yes, development. Development is a process not a result. The result may be a nice little software program, but if he asks for a program that gets titer readings and you give him a program that just measures dispensed volumes I think he'd be pretty upset. Development is a two way street.

3) You assume a lot.

[Sikander]

Originally posted by Arrian
ALL HR departments suck. It's one of the basic laws of business.

-Arrian

[C0ckney]

Originally posted by Lazarus and the Gimp


360 feedback is great, if you're like me. I have settled many scores with it.

i can well believe that tbh. :/