I learned years ago how important it is to shoot the same subject and location over and over again.
The practice teaches a photographer how to form deeper relationships with the subject, and better understand how the primary subject interacts with secondary elements – like the way high tide may introduce a stunning new reflection, or how a blaze of stars in a dark sky might be the missing element that lifts the image to new heights.
Revisiting a subject also serves as valuable “practice.” You cannot develop your skills in anything without a healthy (or obsessive) amount of practice. It always surprises me to find out aspiring photographers think that they can simply photograph their two-week vacations once or twice a year and come home with compelling imagery! It doesn’t work that way.
Run a single loop measuring 4.16667 miles within a single hour. Now do it again. And again. Now keep doing it – starting a new loop on the hour, regardless of how fast you finish the previous one – until there’s only one runner willing or capable of doing so. Welcome to the simple – some might say sadistic – concept of the Big Dog Backyard Ultra in Bedford County, Tennessee.
On the surface, the world of agile software development is bright, since it is now mainstream. But the reality is troubling, because much of what is done is faux-agile, disregarding agile's values and principles. The three main challenges we should focus on are: fighting the Agile Industrial Complex and its habit of imposing process upon teams, raising the importance of technical excellence, and organizing our teams around products (rather than projects).
It actually doesn't matter whether you actually have a formal retrospective. It doesn't matter whether you have four or five labels of things on your retro board, or exactly how you do the retro. What does matter is the notion of thinking about what we're doing and how we can do better, and it is the team that's doing the work that does this, that is the central thing.
Interestingly, just as software people were talking about how we need to kind of follow this very Taylorist notion as the future of software development, the manufacturing world was moving away from it. The whole notion of what was going on in a lot in manufacturing places was the people doing the work need to have much more of a say in this because they actually see what's happening.