51–60 of 107 posts
This is pretty hilarious. So some consultants swooped in, there was 8 weeks of training, and now everything is going to go back to how it was. Source: seen more than one of these external “transformation” efforts. “ Through an eight-week Red Hat Open Innovation Labs residency, Lockheed Martin Aeronautics replaced the waterfall development process it used for F-22 Raptor upgrades with an agile methodology and DevSecOp…
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…
Earlier quoted context omitted.
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…
> My current policy is to allow zero tech debt I was in an office that had such a policy - it didn't go well. Perhaps it's a matter of definition, because: > I hadn't heard of tech debt being something so subjective/invisible that it just creeps in and you have to discover it. Tech debt is _inevitable_. Any decision will eventually be debt - rot begins before the code is even finalized. Focusing on avoiding short ter…
I think you are describing tech debt of the "unavoidable" kind. My efforts tend to be focused on the avoidable kind.
Definitionally, no methodology makes the unavoidable avoidable?
Now, let's say you get to that dreaded point - requirements have changed, dependencies have changed, the industry landscape has changed. Which codebase will be easier to adapt - the debty one or the zero-avoidable-debt one?
"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…
Earlier quoted context omitted.
>cost savings (ala the F-35) What.
It was supposed to be the next generation F-16. The lightweight single engine jack of all trades fighter that could be exported to other countries to help defray development costs. There was even a notion that you could use the same plane across all branches of the military so the same supply chain could be used for all three and you could build them in higher quantities to spread the development costs over more airc…
Sounds rather like the Space Transportation System. During design, it went from a compact inexpensive passenger shuttle with modest payload capability, to a complete pig of a ship. And all because the Air Force contributed cash on the condition that it be capable of classified high-payload-pass missions to polar orbits.
It is nothing short of a tragedy that fully-reusable compact shuttles with flyback boosters (like the Rockwell P333) lost out to the disposable-booster design that was eventually built.
Earlier quoted context omitted.
Nothing saves money like designing your airplane by saying yes to every persons idea in the conference room!
Insert Pentagon Wars Scene Here
This is pretty hilarious. So some consultants swooped in, there was 8 weeks of training, and now everything is going to go back to how it was. Source: seen more than one of these external “transformation” efforts. “ Through an eight-week Red Hat Open Innovation Labs residency, Lockheed Martin Aeronautics replaced the waterfall development process it used for F-22 Raptor upgrades with an agile methodology and DevSecOp…
This is pretty hilarious. So some consultants swooped in, there was 8 weeks of training, and now everything is going to go back to how it was. Source: seen more than one of these external “transformation” efforts. “ Through an eight-week Red Hat Open Innovation Labs residency, Lockheed Martin Aeronautics replaced the waterfall development process it used for F-22 Raptor upgrades with an agile methodology and DevSecOp…
“Colonel, instead of requirements you’ll call them user stories.”
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?
Earlier quoted context omitted.
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…
> My current policy is to allow zero tech debt I was in an office that had such a policy - it didn't go well. Perhaps it's a matter of definition, because: > I hadn't heard of tech debt being something so subjective/invisible that it just creeps in and you have to discover it. Tech debt is _inevitable_. Any decision will eventually be debt - rot begins before the code is even finalized. Focusing on avoiding short ter…
Can you expand on what you mean by this?