From a software engineering view: Lots of rebuilding the wheel, now with Internet Explorer dependencies. Large tech firms are more and more bureaucratic rather than innovative. Startups slurp up VC funding for the next 200 or so unicorn investments. NVIDIA is THE ENTIRE S&P 500 at this rate with SERIOUS "Peak of Inflated Expectations" valuation. Elon Musk.
All the while the majority of the job is fixing the mistakes of the past, of yourself and of some code monkey in 2003. There's this theory that code replicates the structure of the design team. When that team spans an entire corporate hierarchy with SCRUM standups every 2.5 milliseconds, you wonder if you could do the equivalent of the ending of Office Space to the codebase.
I'm sorry, I'm just... anyway, a sage piece of advice. For the love of all that is holy, write requirements BEFORE doing validation for Aerospace applications, and DO NOT OUTSOURCE THE REQUIREMENTS WRITING. That is all.
Both because they are the ultimate tools in maneuvering a terrible, terrible development environment. For reference, Sigasi Studio costs 2,000$ PER YEAR, and it still doesn't work for our dev environment!
Let me paint a picture: Corporate job that won't let you download anything except whatever you can smuggle through a git checkout. It took a month to convince IT to download vim 9.0 on the server. The programming language? VHDL and SystemVerilog and UVM. Horrible language support that relies on proprietary compilers/simulators, and always the ones you aren't using. The one you are using is so obtuse that it has literally 50 configuration files for a single project. All of it is run with a janky python script with half of the flags not working. LSP support is out of the question since it dynamically pulls files from god knows where with at least 10 layers of ../ relative pathing.
All I can do on vim is
ctrl+p for fuzzy file finding and a massive blacklist of intermediate files to ignore,
a custom :Make command with custom errorformat that you can navigate through,
Universal Ctags with per library indexes to reference those far off files,
and a fuckton of grepping for when Go To Definition (ctrl+]) grabs the wrong location.
Vim's autocomplete is almost always good enough. If my laundry list of plugins break, I can literally fix them on the spot and even submit the merge request on github. If you take into consideration all of this configuration and learning effort, I still save hours of navigating through the hundreds of files I have to essentially reverse engineer. My coworkers are all electrical engineers and it shows They're using godforsaken nedit with no syntax highlighting...