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
Planning doesn't make for better software A Fragment by Robin Rendle www.robinrendle.com My own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it. Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me. After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64. Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way. Why Software is Slow and Shitty planningsoftwareagile