11–20 of 79 posts
> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
And they will refer to this, 'well-researched piece by a 'reputable news source.
Let's see if I am right, will check in in 2-3 weeks...
> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
I think that's the case for most things where people who are not complete subject matter experts write about something. A lot of our own conversations about things are probably quite inaccurate in a lot of details.
In this particular case the author may even have asked back but what is the author going to do if he/she gets fed inaccurate information? I think the only blatant inaccuracy is the reference to DevOps, otherwise the description of agile is pretty OK too me.
I hope people won't fall into the usual trap where some inaccuracies in some media leads them into reading much less accurate but more extreme media which is something you often see in politics.
> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
Also, what became apparent with Apollo – though it is not how it worked – is that it is better to define your system up front to minimise errors, rather than producing a bunch of code that then has to be corrected with patches on patches.
Source: https://www.theguardian.com/technology/2019/jul/13/margaret-...
> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
Is it really that bad for a general readership? I'd like to see automated testing in there. And maybe incrementally improving products. But to someone who doesn't know and doesn't care about the details of software development, it seems to capture the basic gist.
Remove the reference to "DevOps", and you have a concise enough explanation of "so-called agile software development" and a cleaner paragraph overall:
> One solution favored by Winter during his recent tenure was agile development, a popular software engineering methodology used for quickly testing and evaluating features for new products.
(Since software teams in the U.S. government, such as 18F, also use agile dev these days, so it's not particularly relevant to point out its popularity in the "private sector")
US is miles ahead...someone have the courage to level.
It's true that the F35 seems a little beefy, compared to other aircrafts.
A single engine is quite bad for survivability.
While I can admit that vertical liftoff can be an asset if you want to respond quickly to an attack without building airstrips every 50km, it's hard to really justify building so many aircrafts with a airframe shape that allows VTOL. VTOL is a tough compromise on aircraft.
Having an aircraft that can play several roles is not a good idea. Regrouping roles is a good idea, but regrouping them all into only one is really not a good engineering decision.
That's like deciding to design a pen-lighter-laser-pointer-usb-drive-knife-screwdriver into a single device. It sounds cool, but in the end, it's better to see what can go together and what should not.
Unless the F35 has a next gen radar which allows it to see enemy aircrafts from farther, it will be bad at dogfights.
> One solution favored by Winter during his recent tenure was so-called agile software development. His vision for “continuous capability development and delivery” resembles DevOps, a popular method in the private sector for quickly testing and evaluating features for new products. Coders generate software upgrades or patches in a matter of days or weeks, pass them along to users to test and then push out the update…
The current title I'm seeing is "Inside America’s Dysfunctional Trillion-Dollar Fighter-Jet Program" which seems misleading as well; it's more of a history of press releases. Doesn't look like they interviewed anyone actually working on it aside from the fellow in charge if that.
https://www.defensenews.com/air/2019/06/12/the-pentagon-is-b...
Note that the posted article is a NYT Magazine piece, which has different editorial style and convention from the newspaper. Typically, a story this long wouldn't be written by a non-staffer in the newspaper. But it's not uncommon for the magazine to commission a writer who has written a notable article for a different publication to generalize and elaborate on it for the NYT Magazine.