Basic Qualifications: • Bachelor's degree in Engineering, Computer Science or related technical focus. • Experience in COMM and Navigation. • Avionics experience • Experience with aircraft operations. • Microsoft Office I love the MS Office req at the end. "Yes, we see you've got a BS in engineering, you're an expert at avionics and COMM control systems, but do you know anything about MS Word?"
You're reading the job description all wrong...you've got to think like a hiring manager in the defense industry to make any sense of it, i.e. reverse qualification priorities and the actual job you'll be hired to perform will become crystal clear.
Lockheed has an opening for engineers with VAX experience for the F22
131–140 of 330 posts
Re: Lockheed has an opening for engineers with VAX experience for the F22
#132Earlier quoted context omitted.
The way that the fine article was worded, it seems that the engineering team knew that they needed approximately 1.5M LOC before they has started. How could they have known that? Or is it simply poorly worded? > The ATF Team planned to develop approximately 1.5 million source lines of code, across more than 20 software development companies located throughout the U.S., Canada, and Europe.
There is a school of thought that says rather than look at the requirements and make your best guess at the amount of work needed to implement them, you will get more accurate results by making your best guess at the number of lines of code required, then using a formula to estimate the amount of work needed to write that many lines of code. I personally am not convinced this is really more accurate, but it does have…
Re: Lockheed has an opening for engineers with VAX experience for the F22
#133Earlier quoted context omitted.
More like: "We ended up hiring the guy most competent at MS Word at the expense of everything else, because out of the five requirements it was the only one the managers doing the interview knew anything about". "Johnson! We're promoting you to head technical flight operations. We can't believe the level of your MS Word skills!" "Senator, we have no idea why the F-22 inexplicably crashed. That software was designed b…
More like: The guy that designed the flight control surfaces of the F-22 did so using an elaborate Excel spreadsheet powered by 4,000 lines of uncommented VBA filled with aerodynamics equations, and he retired 3 years ago.
Re: Lockheed has an opening for engineers with VAX experience for the F22
#134Modern is relative. F-22's first flight was 1997. F-35 development started in 1992, first flight of X-35 was 2000 and F-35's first flight was 2006. There is absolutely noting wrong with using old technology. Being modern just for the sake of being modern is wasteful.
Re: Lockheed has an opening for engineers with VAX experience for the F22
#135So a couple of the comments here have been mentioning the high pay of people with specialties like this in the context of LM and other defense contractors. My impression from Glassdoor and general conversation with software developers has been the DCs pay pretty low for software in general compared to FAANG or even other engineering companies. Is it true that people with obscure specialties at places like LM can comm…
Back in the early 2000s I know of some J2EE architects that pulled $200k as defense contractors once they got a Sun certification. The certification and diploma mill market in the US is driven squarely by big federally funded institutions that value paper over experience because they don’t know how to measure ability any better than SV Leetcode questions would assess.
Of defense contractors I’ve seen pay tables for in the DC area, LM and Raytheon paid worse for senior engineers than slightly smaller, more specialized companies but they certainly had a lot more overhead and administrative positions available that were possible to reach just by having a PhD even if it’s not related to engineering or STEM in general at all (political science obviously makes sense here as valuable, for example).
But under DHS you can hit $200k+ as a contractor for anything that has “cyber” attached to its name these days. But for the most part, the high payout days for software engineers in defense are over which is what led me to leaving the DC area years ago to stick with better pay and work environment with private sector. A TS is a pain and the pay bump is a joke compared to RSUs. I’ll take leetcode grinding for months to get a stack of RSUs and marketable engineering skills over the demonstrably useless charade of the DoD security theater practices with none of the employment benefits besides some smug, self-assured sense of patriotism.
Most of the higher paid contractors in DoD aren’t engineers - they’ve usually been intelligence officer trainers and skilled and experienced warfighters (well past $400k, much of it untaxed).
Re: Lockheed has an opening for engineers with VAX experience for the F22
#136Basic Qualifications: • Bachelor's degree in Engineering, Computer Science or related technical focus. • Experience in COMM and Navigation. • Avionics experience • Experience with aircraft operations. • Microsoft Office I love the MS Office req at the end. "Yes, we see you've got a BS in engineering, you're an expert at avionics and COMM control systems, but do you know anything about MS Word?"
It indicates that writing and editing thousands of pages of documentation will be contractually required. Word proficiency can save a lot of pain for everyone on that team.
Re: Lockheed has an opening for engineers with VAX experience for the F22
#137Basic Qualifications: • Bachelor's degree in Engineering, Computer Science or related technical focus. • Experience in COMM and Navigation. • Avionics experience • Experience with aircraft operations. • Microsoft Office I love the MS Office req at the end. "Yes, we see you've got a BS in engineering, you're an expert at avionics and COMM control systems, but do you know anything about MS Word?"
• Matlab and MS Excel experience is a plus.
The req has been open since July of last year.
Re: Lockheed has an opening for engineers with VAX experience for the F22
#138I had a job maintaining fortran code on an openVMS OS running on itanium hardware. Itanium was intel's failed attempt at a 64bit architecture and that's the platform VMS decided to port to. That made hardware expensive and as of recently obsolete (i think hp discontinued that integrity line of servers) VMS doesn't natively support TCP/IP, because it predates it. The VMS communication protocol was called decnet. So yo…
1. RE: FORTRAN. VAX FORTRAN was the most awesome implementation of FORTRAN ever. FORTRAN because these systems didn't have much RAM and CPU power was limited. FORTRAN went into the background for a while when the C fad began in the early 1980s; however, academics cringed at C for reasons that the industry would eventually learn "the hard way" and FORTRAN came back along with a government knee-jerk reaction called Ada and a pile of 4GLs starting with DATATRIEVE --up until processors and RAM allowed for more productive use of more powerful "safe" language systems (Java, C#, Python, Swift).
2. RE: ITANIUM. DEC created VAX/VMS for the break-thru 32-bit VAX-11 architecture and then ported it to its break-thru 64-bit Alpha architecture and rebranded it as OpenVMS. The Alpha chip was really powerful, but it was produced only by DEC's Hudson chip plant (which also produced the StrongARM chip whose descendants are in all of the smartphones). To address the customer need for a second supplier for that chip, DEC began to shop around the Alpha architecture to other semiconductor manufacturers. One of those was Intel --which decided not to become a second source and a little while later, announced the Pentium series that revived its ALL BUT DEAD x86 architecture using patented concepts found only in DEC's Alpha chip. There was a lawsuit and the settlement was that Intel would buy the Alpha chip and Hudson plant. This resulted in the Itanium architecture, which the then owner of DEC (HP) decided to embrace for OpenVMS and its other HP operating systems. As the Pentium chip gained momentum, Intel realized it would be more profitable to use the tech to make X86_64 architecture. Meanwhile, Microsoft, which was all but ready to dump the ALL BUT DEAD x86 architecture (in favor of MIPS and PowerPC), pivoted with Windows NT and released full support for X86_64. Considering that Windows NT was developed by the original computer scientists behind VMS and considering the dominance of Windows on the desktop and the low cost of X86_64 hardware (due to economies of scale), it was no surprise that Itanium fell out of favor, and OpenVMS along with it (though there were many heroic efforts to "rescue" OpenVMS from that dead architecture, HP had no real interest --at least not in time).
3. RE: VMS TCP/IP. This cracked me up. I wrote one of the first TCP/IP stacks for VAX/VMS on a VAX-11/780 using InterLAN hardware. You are correct that VMS pre-dates TCP/IP --but dude it was only by like 1-2 years! VMS was uses with XNS/ITP (upon which TCP/IP was based). TCP/IP is le grand garbage --as the entire planet knows now and DEC had bet heavily on something called OSI to replace DECnet. But some f'n jack head named Vincent Cerf created an async implementation for TCP/IP that allowed the bazillion Windows PC to hop on the Internet (what could go wrong) and that quickly became Microsoft RAS which destroyed the universe quickly. All of the stable and secure networking systems died. Bill Gates was interviewed at one point and responded to a question about what the biggest unexpected development had been with a dumb look saying he had failed to predict the sudden end of distance-and-time based pricing for data communications. So now, dude in St. Petersburg can show off his genetic superiority by hacking the microcode in the Intel Ethernet controllers in your laptop from 8,000 miles away at virtually no cost. Enjoy!
4. VMS knowledge are hackers. This is among the most outrageous comment I've read on the Internet. VMS was all about structure and discipline. If you weren't a computer scientist (or college student) you weren't even getting a job working on one! What you probably observed had nothing to do with VMS but just maintaining legacy code in general.
5. RE: "interesting". VMS was the most powerful operating system ever created well into the modern era. You can imagine that the guys creating Windows NT at Microsoft (who previously developed VMS for DEC back East) were not being allowed to create the true successor to VMS --the idea was to get something working on small cheap PCs that would be sold to all of the small businesses, not on continuing to perfect the product of 30 years of engineering (as VMS descended from their prior RSX11 and RT11 operating systems) as they had been doing first to the 78032 "chip" and later to the Alpha processors. I think around 2015, Windows, Linux and MacOS finally began to pull away from where VMS was (back in 1990). One can only imagine how powerful VMS would have become when run on something like the MacPro 7,1 that Apple announced.
In conclusion, true industry leaders, many of whom did not support VMS back in the day (because they were forced to embrace crummy UNIX System 3, V and BSD "hacks" for lack of access to the incredible DEC engineering resources), will tell you that VMS (and TCP/IP) are stories of lost art that severely setback the pace of mankind's development. The reasons are many: Bill Gates' well known BS, Vincent Cerf's destructive efforts to advance PPP, alleged theft of intellectual property by Intel that set off the downward spiral of DEC, skyrocketing memory prices due to market manipulation and Carly "That Face" Fiorina.
Consider yoh-self schooled.
Re: Lockheed has an opening for engineers with VAX experience for the F22
#139I had a job maintaining fortran code on an openVMS OS running on itanium hardware. Itanium was intel's failed attempt at a 64bit architecture and that's the platform VMS decided to port to. That made hardware expensive and as of recently obsolete (i think hp discontinued that integrity line of servers) VMS doesn't natively support TCP/IP, because it predates it. The VMS communication protocol was called decnet. So yo…
VMS had some really nice features - mostly forgotten now that it's all 'nix, all the time.
You know, I should apply for that Lockheed job just to get shutdown for being in my 50s and not having touched a VAX since my 30s (because, you know, it's changed so much since then rofl)