repetition
The language itself has been weaponized
Attenuation and repetition
Long Form Study: Why Photographers Should Repeatedly Revisit a Scene
An Article by Scott ReitherI 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.
A loop eternal: Big Dog Backyard Ultra
An ArticleRun 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.
Product vs. Feature Teams
This article is certain to upset many people.
Empowered product teams
When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility
In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us.
However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap.
What went wrong?
If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong.
Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question.
And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question.