3 ms·
Several years ago I worked on one Lockheed project (Not the F-35, but part of another large defense program) as a subcontractor (at a Lockheed facility). The m
by jcadam 11y ago
Several years ago I worked on one Lockheed project (Not the F-35, but part of another large defense program) as a subcontractor (at a Lockheed facility). The most dated development practices imaginable. Waterfall, no source control (they brought in subversion near the very end of the project in order to meet govt requirements but only the 'architect' was allowed to commit anything (or even to use the 'svn' command)), SLOC used to measure "progress", even the office furniture looked 70s vintage. The project was one giant clusterf*k from start to finish, and I swore an oath never to work on anything involving "Lockheed" ever again.
- michael_h 11y agoI had my software installed in a Lockheed system. It was incredibly surreal - the amount of time spent assigning blame for problems was orders of magnitude more than the time spent solving problems. One of their sysads, in a meeting with the Important People, blamed my system for extremely high network and disk load. He showed graphs that spiked and plateaued a few minutes after system load, pointed at the spike, then pointed at my face and said, "It's his software that's making this whole thing slow. Get him out of here and we'll build something that actually works." I got unparalleled satisfaction when I got to say, "I haven't installed my software yet."