Be A (Re)Visitor An Article by Rob Walker robwalker.substack.com I was thinking about this not long ago while reading in Petapixel an essay by a photographer named Scott Reither, “Long Form Study: Why Photographers Should Repeatedly Revisit A Scene.” In it, he described photographing one particular stretch of beach, over and over, throughout his career. Of course that landscape has changed over time, and of course he’s had moments when he felt he’d captured the same territory so many times there was nothing left to see. But there was always something more to see — maybe because of a change in Reither’s life, rather than in the physical environment. seeingchangephotography
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Frederick P. Brooks, Jr., The Design of Design Requirements proliferationA Plea for Lean Software features