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
Building is never a straight line You might think that Mario 64 was built with tickets and sprints, but, according to interviews, there was no master plan, only the principles that the game should feel good and be fun. They started with just Mario in a small room, and tuned his animations and physics until he felt nice and responsive. After that, the levels were also created as they went, with the designers, developers, and director going back and forth using sketches and prototypes. Building like this is never a straight line. Ideas and code get left on the cutting room floor because part of innovation is questioning whether what you made should exist. The process is cyclical and iterative, looking something like this. Pirijan Ketheswaran, Why Software is Slow and Shitty pketh.org Follow the funEngineers who love their work agileiteration