What do you mean you went and just fixed it!?
We need all of middle management to charge for the fix!
What isn’t a security risk? A closed source vendor supplied application that has its headquarters in the US.
You can sometimes find pockets of innovation in the defense sector, but it’s mostly filled with bureaucrats with engineer in their title.
Reliable even down to the bug behaviors...
IMO it makes more sense to communicate the expected impact of the changes, so that downstream can read a patch bump as unlikely to cause issues.
I'm sure it's important to have a stable technology to train on in the military; at the same time, I remember one of their open-days they were showing off a civilian in-flight entertainment system that was so clearly overpriced for what it was that I knew even as I saw it that I could've done better for lower unit-cost. This isn't to show off, even despite my having not yet finished secondary school at the time — my solution would've been little more than "glue laptop to chair/wall in front", as tablets weren't something people discussed much around me in the 90s — it's just that the business solution was really unimpressive.
I assume there's secret military equivalents to that public project.
[0] if you exclude the job interview at Lockheed Martin for the year in industry paid work experience part of my degree, which didn't go further than an interview
Theres a reason there's so many steps to accept hardware.
I have an old account with a bank that has hardly changed its website design in well over a decade. It's great! The information is clearly laid out in tables and everything loads super fast. Every other financial web app I'm familiar with has a much more "modern" design and is categorically worse to use. One site literally takes over a dozen clicks to get to basic information and evey single page load is slooooow.
The adversarial nature that defense companies treat our military is appalling. I'm convinced that refactoring a lot of this BS could get us way more with less $
So the only profitable way to win these contracts is offer the cheapest bid by delivering as little as possible while being in spec, and then pillaging on the change orders.
It's a method for transferring billions of dollars from public tax revenues to private companies which are cozy with the state. It has nothing to do with safety or reliability.
All other methods of stealing tax money are illegal.
ain't no one talking about tax cuts, or getting after the rich, cuz of that.
HOWEVER when your acquisition system is designed to ensure that a nuclear detonator and a LAMP application go through the same process, these kinds of “overkill” or “nonsense” requirement responses happen.
We’re long overdue for fixing the FAR and federal acquisition process, which is the root problem. The legal system and processes built over the last 50 years, and as a result the people inside it, doesn’t allow for simple and efficient differentiation between projects legally so you end up with the same hammer meets mail approach.
They mean well, and I understand how hard it can be for government agents to hold massive contractors accountable, but the purpose of a system is what it does... so we wind up with entrenched bureaucracy, and the players who don't subscribe to these approaches wind up getting outcompeted because their on-paper performance doesn't measure up. Even if they're in fact a million times easier to work with and do a great job.
Our software was part of the stack that our regulated customers were using to document their compliance. Every year or two, they would audit our development process to insure that untoward code wasn’t slipping into the release. Getting the fix into a release would have required that the bug be prioritized, fixed and qa’ed. Never became important enough. It burned me at first, but I’m not sure it was the wrong outcome.
Prior to this, I had no idea why defense projects were so expensive and slow. You have to understand, there are so many levels of negotiation, over the smallest changes imaginable. There's no such thing as "open source code" in these projects, everything is either modified off-the-shelf, or completely boutique stuff, and of course implemented in such a way that the clients (that would be us) can't just access the code themselves, or that clients can just build upon or make wrappers.
The contractor will send you their own techs or engineers - even if it's across the world - to fix the most trivial bugs. And it will take months or planning, budgeting, and what not.
In once instance, one contractor tech spotted a bug in the code, which some user had reported about - it was a one character fix, just a typo, really. So he fixed it on the spot, along with the rest of the stuff he came for.
A couple of weeks later he comes back, and reverses the bug. He had told his manager about the bug fix, and was berated for fixing in. In order to fix that bug, it had to be reported correctly, go through software update meetings, go through budgets, and the whole nine yards.
The bug was reported the correct way, and many months later he came back to fix it (again).
The whole process of specs and updates was like pulling teeth.