Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

redhat.com

Post reply on HN
Print view View original

31–40 of 107 posts

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#31

Post by dar7 »

checktheorder wrote: post #8
ThreeFx wrote: post #2

Am I reading this correctly as Kuberetes-powered fighter jets? That's certainly not going to shoot anyone in the foot...

I was thinking more along the lines of removing features to simplify maintenance, Gnome 3 style. "Good news, General. We've found a way to lower maintenance costs in the cockpit systems by 10% if we removed this thing here on the blueprints, so we've already gone ahead with that change." "But that's the emergency ejection system!" "Yes, and our data indicates that it's almost never used. It doesn't really make sense…

Red Hat's new D-BUS service Fighter-Kit and systemd-missiled will address these shortcomings.

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#32

Post by smileysteve »

vemv wrote: post #20

Scrum has been a catastrophe to the software industry (argued elsewhere countless times) - I don't want to imagine the consequences it can have for jet figthers. For such environments you definitely want to have no deadlines at all, to have a special focus on well-defined requirements, and in software quality. That investment should be marginal compared to hardware costs. And in fact, by going more slowly, you end up…

> when you enjoy zero tech debt and an excellent foundation.

This implies that you plan exactly when and where tech debt is accumulating or found. The scrum argument is that by iterating and releasing, you find out where unexpected tech debt is more rapidly; and you go back and fix it.

One way that #AgileIsDead happens is when products disregard the tech debt for features even as it becomes apparent.

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#33

Post by dharmab »

checktheorder wrote: post #13
ohaideredevs wrote: post #7

"The Lockheed Martin F-22 Raptor is one of the world’s premier fighter jets, thanks to its unique combination of stealth, speed, agility, and situational awareness." A huge understatement. It's the only true 5th gen that's tailored for performance, rather than cost savings (ala the F-35). The others are completely unproven (Chinese) or both unproven and in extremely limited quantities, while not providing true stealt…

>cost savings (ala the F-35) What.

Yup, that was the original goal of the F-35. The idea was that by sharing parts across multiple variants and across multiple militaries, the F-35 would be a cheaper fighter than the F-22 that could scale to a larger fleet.

It's not totally crazy on the face of it- The expensive but undefeated F-15 and the relatively cheaper F-16 successfully pulled it off in the 20th century.

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#34

Post by heavenlyblue »

freehunter wrote: post #26
walrus01 wrote: post #12

what the hell is DevSecOps? I've been doing network security for twenty years, so I know what that is, this just sounds like some marketing and sales people started mashing buzzwords together.

DevOps is mashing development and operations together. But that ignores security, often putting security reviews after the code has been deployed or at least after it's done being written, which necessitates re-work. DevSecOps makes sure security is a part of the development and operations work. Yes it's a re-wording of an existing concept. No, it is not a new idea. Yes, it is important enough to call it out because…

What is the size of the company when CISO, on average - exists as part of the company?

I know Google has security teams, but what about the smallest company that has one?

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#35

Post by scarejunba »

vemv wrote: post #20

Scrum has been a catastrophe to the software industry (argued elsewhere countless times) - I don't want to imagine the consequences it can have for jet figthers. For such environments you definitely want to have no deadlines at all, to have a special focus on well-defined requirements, and in software quality. That investment should be marginal compared to hardware costs. And in fact, by going more slowly, you end up…

Iteration speed and quality are directly related, not inversely. Iterative development allows exploring software design considerations fast which means you get to actually good software instead of getting it right the first time.

Fast iteration means you can kill ugly design. Slow iteration means you get stuck with a design choice because you discovered its flaws too late.

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#36

Post by consumer451 »

ohaideredevs wrote: post #7

"The Lockheed Martin F-22 Raptor is one of the world’s premier fighter jets, thanks to its unique combination of stealth, speed, agility, and situational awareness." A huge understatement. It's the only true 5th gen that's tailored for performance, rather than cost savings (ala the F-35). The others are completely unproven (Chinese) or both unproven and in extremely limited quantities, while not providing true stealt…

I’m not a huge fan of obscene military spending, but the cancellation[0] of F-22 production must be one of the most boneheaded decisions I’ve seen in US military procurement. I must add the caveat that I have no security clearance so there may be other factors.

[0] https://en.wikipedia.org/wiki/Lockheed_Martin_F-22_Raptor

> Service officials had originally planned to buy a total of 750 ATFs. In 2009, the program was cut to 187 operational production aircraft...

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#37

Post by twiggie »

vemv wrote: post #20

Scrum has been a catastrophe to the software industry (argued elsewhere countless times) - I don't want to imagine the consequences it can have for jet figthers. For such environments you definitely want to have no deadlines at all, to have a special focus on well-defined requirements, and in software quality. That investment should be marginal compared to hardware costs. And in fact, by going more slowly, you end up…

You can't have no deadlines at all. The world is moving forward. Military rivals are building their own planes.

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#38

Post by vemv »

smileysteve wrote: post #32
vemv wrote: post #20

Scrum has been a catastrophe to the software industry (argued elsewhere countless times) - I don't want to imagine the consequences it can have for jet figthers. For such environments you definitely want to have no deadlines at all, to have a special focus on well-defined requirements, and in software quality. That investment should be marginal compared to hardware costs. And in fact, by going more slowly, you end up…

> when you enjoy zero tech debt and an excellent foundation. This implies that you plan exactly when and where tech debt is accumulating or found. The scrum argument is that by iterating and releasing, you find out where unexpected tech debt is more rapidly; and you go back and fix it. One way that #AgileIsDead happens is when products disregard the tech debt for features even as it becomes apparent.

Interesting, I hadn't heard of tech debt being something so subjective/invisible that it just creeps in and you have to discover it.

(I'm open to be convinced)

Generally I have witnessed tech debt as something pretty blatant and obvious - generally it's detected in the code review process. Sometimes it's big faults being introduced, more often it's small faults leading to 'death by a thousand cuts'.

My current policy is to allow zero tech debt, following the "no broken windows" principle. https://pragprog.com/the-pragmatic-programmer/extracts/softw... That involves a greater investment in code reviews.

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#39

Post by walrus01 »

m_b wrote: post #24
walrus01 wrote: post #14

Earlier quoted context omitted.

I don't think you can realistically expect anybody in the world, of any political ideology, to not use something that is GPL/BSD/LGPL/Apache/whatever licensed, if you've published the source code to the Internet. I would be entirely unsurprised to find north korean telecoms/state government agencies using centos or debian. In fact if you google "north korea linux" you'll find that they already created their own weird…

Thanks for lecturing me about licensing, as a contributor I already know that. Isn’t it allowed to go further that sources access, what’s written on a piece of paper, and caring about ethics? Does OSS contributors really needs to be so alienated?

I honestly don't know what you expect, if you want to find some way to force autocratic regimes somewhere in the world to not use source code that's published to the open internet. If you discover some way to bend north korea to your will, please let us know.

Re: Lockheed Martin Taps Red Hat to Accelerate F-22 Raptor Upgrades

#40

Post by vemv »

twiggie wrote: post #37
vemv wrote: post #20

Scrum has been a catastrophe to the software industry (argued elsewhere countless times) - I don't want to imagine the consequences it can have for jet figthers. For such environments you definitely want to have no deadlines at all, to have a special focus on well-defined requirements, and in software quality. That investment should be marginal compared to hardware costs. And in fact, by going more slowly, you end up…

You can't have no deadlines at all. The world is moving forward. Military rivals are building their own planes.

Would you rather have a bug-free fighter delivered in 2021 or a buggy fighter in 2020?

Especially considering that many codebases are expected to have a shelf life of 5-10 years.

IME working deadline-lessly doesn't mean you're suddenly knee-deep in a metaprogramming rabbithole. You just do the same stuff, stress-free.

Post reply on HN