Tweets for Today

[mcroft]

• 13:21 "Analysis of Failure [X] indicates that changing process [Y] (as previously suggested) would prevent future failures" aka "I told you so..."

Automatically shipped by LoudTwitter

Comments

[prince-corwin.livejournal.com]

True thing number one: We have a formal policy of writing up "Lessons learned" papers or presentations after major findings or after the conclusion of major projects. These are not trivial undertakings-- major ones might be attended by several dozen engineers and managers, and even minor ones are archived for future reference. They count, in arcane ways, as "internal technical publications," for our upper level tech ladder promotions.

True thing number two: We are formally forbidden from publishing any "Lesson learned" paper whose central message boils down to, "If we had followed previously documented process, we wouldn't have been in this mess to start with."

[mcroft.livejournal.com]

It's amazing how often crisis [X] shows the real need for hobbyhorse project [Y].

But yeah, I think I finagled my way into getting to write the findings, and my findings are likely to support what I want to do.

[greeneyes-rpi.livejournal.com]

That's amusing, as many of our internal publications include references to previous work where we said the same thing. Documentation rules!