Originally posted by DGXSER
View Post
The last ten years that I worked, I did pretty much either design/build projects, or projects on the local military bases. A lot more latitude than you'll find on most so-called 'fully engineered' projects. To be successful, you learn quickly that there isn't just 'one way', but every project has to be looked at separately. The base projects were usually the most challenging, as either they didn't really know what they wanted, or if they thought they did, they had some moron who insisted on 'his way' that usually wouldn't work (the Army Corps of Engineers are famous for this). Best way to handle those were to go limp on them, make sure everyone understood that I was doing exactly what was asked (and having it documented; critically important), then when it went to crap, the inevitable blame would attach to right person.
The thing that always bemused me the most about working on the bases was the basic job priorities were reversed from what you'd find in the non-federal sector. Anywhere but there, they were: 1. Code (until it passes it's not done)2. Functionality 3. Appearance. On base, it was just the opposite. There, appearance was king and the trick was giving them that without compromising the other two any more than needed. Code didn't matter much to them (but it did to me), as they'd pass almost anything if it looked the way they wanted. I mentioned this to one of the better inspectors one day, and he got a startled look on his face, but after thinking about it for a minute admitted that he'd never looked at it that way but I was right. Scary, eh?
'78E original owner
Comment