News for hackers. Stuff that matters.

A comment on Department of Defense: Software Is Never Done (2019) [pdf]. Parent comment

Re:Department of Defense: Software Is Never Done (2019) [pdf] by arcbyte on Saturday January 28, 2023 @01:51PM (#34560335)
The ONLY way to get quality is through quantity. That's the key insight.
[ Parent | on HN ]
Re:Department of Defense: Software Is Never Done (2019) [pdf] by hamandcheese on Saturday January 28, 2023 @02:02PM (#34560435)
Quantity of... dollars?
[ Parent | on HN ]
Re:Department of Defense: Software Is Never Done (2019) [pdf] by no_wizard on Saturday January 28, 2023 @02:08PM (#34560496)
I’m betting releases and iteration cycles they’re tied to. The most agile place I ever worked shipped code most days of the week in some fashion. For control reasons we released Tuesday-Thursday not Mondays or Fridays. So was nearly every day something went out.

I’m including bug fixes here but nothing got stalled. We had a working iteration loop of Test -> Develop -> Test -> Review -> QA -> Release

Lots of automated checks, investment in infrastructure and good architecture made this possible. Ironically one of the smallest companies I ever worked for

[ Parent | on HN ]
Re:Department of Defense: Software Is Never Done (2019) [pdf] by xboxnolifes on Saturday January 28, 2023 @03:52PM (#34561726)
Iterations.
[ Parent | on HN ]
Re:Department of Defense: Software Is Never Done (2019) [pdf] by __MatrixMan__ on Saturday January 28, 2023 @03:31PM (#34561491)
"Breaks when you try to use it" is a quality that I can usually achieve on the first try.

Or did you mean some quality in particular?

[ Parent | on HN ]