What's the deal with the Navy trainers?

Sinistar said:
I am interested in the actual thread: Unless there is firmware running in the 02 system and that FW is suspect, I think going off on coding is irrelevant.
Click to expand...
Ahhhh let the code monkeys have their fun. There's a reason we keep them locked away in dark rooms with a years supply of Red Bull. :rofl:
 
Sluggo63 said:
I'm sure that's true, but this happens to be one of my favorite "W T F?" walls falling down.
Click to expand...
I figured that one would come up. :cool: It's a fairly benign fault, all the same. I can think of a couple that had less happy outcomes. Maybe some day over some tea in a Jim Beam bottle. I'm satisfied that they're rare.

Nauga,
getting a little grim for a minute
 
Cykoguy said:
Program managers getting crapped on left and right but I am not getting panties in a wad. I have worked with engineers like PAFlyer. Their reputation always proceeds them and they rarely are sought after to move programs.
Click to expand...
I've worked both sides, Chiefy.

Funny, I've always been the guy they call when fast time to market products are dropped into the roadmap.
 
jsstevens said:
I love having people like you involved. It gets me more insight into things I may never have seen, which lets me do a better job.

But if you think software only does what it's told, you haven't written software for hardware in development. Or found any compiler bugs. Or found the race condition in a processor.

Almost all of the time it does what it's told.
Click to expand...
https://en.wikipedia.org/wiki/Pentium_FDIV_bug
 
paflyer said:
Funny, I've always been the guy they call when fast time to market products are dropped into the roadmap.
Click to expand...
Any of them have OBOGS or are you just dropping flares and chaff at this point?

Nauga,
and another ruler thread
 
I've often wondered with the OBOGGS problems wether the OBIGGS is really safing the fuel tanks:eek:

Cheers
 
GRG55 said:
I'm an engineer and see little reason to wait for things to break. We take apart things that are perfectly functional to see how they work. Of course once that objective has been met there is little incentive to waste time putting anything back together again - nothing to be learned from that. ;)

I think it started when I took apart the vacuum cleaner. I don't think Mom ever forgave me for leaving behind a pile of parts in the living room...:rolleyes:
Click to expand...

I think my most famous quote when I was in high school was, "This should work." Sometimes it did, sometimes it didn't. And given the various items around the house that I fixed simply by taking apart and putting back together again, I guess I was predestined to be an engineer. Graduated with a BSEE 42 years ago.

denverpilot said:
A rather famous (infamous) Intel screwup, yep.
Click to expand...

Which I had nothing to do with. It happened before I went to work at Intel. :)
 
X3 Skier said:
I've often wondered with the OBOGGS problems wether the OBIGGS is really safing the fuel tanks:eek:
Click to expand...
That would be bad - but the T-45 doesn't have OBIGGS. At least it didn't during my time with it.

ETA: Oops, I first read that as a crossed-lines issue, not 'just' non-inerting. :confused:

Nauga,
inert
 
Sluggo63 said:
"there are failure modes that pop up over time that engineers don't foresee when they're designing and building stuff..."

That's not a true statement? ;)
Click to expand...

True statement. I'm working with a customer on several ideas on their next generation products. Some ideas work out well, some have unforeseen issues or failure modes. So you work more iterations, R&D. Eventually, though, someone in mgmt or marketing says it's good enough, ship it!
 
You must log in or register to reply here.
Back
Top