new | ask | show | jobs
thangalin 4 hours ago  [ - ]

From 1996:

https://www.eng.auburn.edu/~kchang/comp6710/readings/They%20...

"There is the software. And then there are the databases beneath the software, two enormous databases, encyclopedic in their comprehensiveness. One is the history of the code itself -- with every line annotated, showing every time it was changed, why it was changed, when it was changed, what the purpose of the change was, what specifications documents detail the change. Everything that happens to the program is recorded in its master history. The genealogy of every line of code -- the reason it is the way it is -- is instantly available to everyone."

danhite 3 hours ago  [ - ]

also from ^ article on Lockheed Martin Corp space shuttle software group ...

  Importantly, the group avoids blaming people for errors. 
  The process assumes blame - and it's the process that is 
  analyzed to discover why and how an error got through. 

  At the same time, accountability is a team concept: 
  no one person is ever solely responsible for writing or 
  inspecting code. "You don't get punished for making errors," 
  says Marjorie Seiter, a senior member of the technical staff. 
  "If I make a mistake, and others reviewed my work, then I'm
  not alone. I'm not being blamed for this."