A three-layered process of documentation A three-layered process of documentation: (1) First, there is the field notebook. This is where the actual numbers are recorded, together with passing observations relevant to the interpretation of these numbers. Paper is still proving more durable than electronic data. (2) The journal is a parallel record to that of the notebook—a daily account of events, thoughts, and observations. (3) Last of the three strata, then, are the publications. Traditionally, in science, these are articles in academic journals leavened with chapters in books. To be successful, a young scientist need aspire to no more than these two forms of output together with their oral versions at interminable conferences and meetings of learned societies. There came a time in my scientific development, however, when other forms of publication became important: magazines articles, and writing books. Roger Kitching, A Reflection of the Truth notetakingrecords
The value-destroying effect of arbitrary date pressure on code An Article by Gandalf Hudlow iism.org The mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™! What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™. Driving engineers to an arbitrary date is a value destroying mistake agileplanningqualitydiscovery