Upstream Color Original Soundtrack Leaves Expanded May Be Prevailing Blue Mixed With Yellow Of The Sand I Used To Wonder At The Halo Of Light Around My Shadow And Would Fancy Myself One Of The Elect Fearing That They Would Be Light-headed For Want Of Food And Also Sleep Stirring Them Up As The Keeper Of A Menagerie His Wild Beasts The Finest Qualities Of Our Nature Like The Bloom On Fruits Can Be Preserved Perhaps The Wildest Sound That Is Ever Heard Here Making The Woods Ring Far And Wide I Love To Be Alone A Young Forest Growing Up Under Your Meadows Their Roots Reaching Quite Under The House The Rays Which Stream Through The Shutter Will Be No Longer Remembered When The Shutter Is Wholly Removed After Soaking Two Years And Then Lying High Six Months It Was Perfectly Sound Though Waterlogged Past Drying The Sun Is But A Morning Star A Low And Distant Sound Gradually Swelling And Increasing As If It Would Have A Universal And Memorable Ending A Sullen Rush And Roar Shane Carruth, Upstream Color www.discogs.com WaldenI love to be alone euphonynaturelonelinessmelancholysoundending
Upstream Color A Film by Shane Carruth www.imdb.com The same material as the sunWhen it goes wrongUpstream Color Original Soundtrack WaldenExtract (n)Authorisation vs. Consent connectioncycleslove
Primer A Film by Shane Carruth www.imdb.com A normal wooden pencilSomething moreAt the top of the pageParanoiaHe had but to speak+1 More timetechnologyexperiments
everything & everything & everything A Video by Shane Carruth www.youtube.com The oppressively vapid life of Morgan is forever transformed when a mystical blue pyramid - that inexplicably produces doorknobs - appears in his apartment. What follows is a tale of greed and loss as Morgan builds an impossible, absurd corporate empire of doorknobs. surrealism
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
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? teamwork
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. Viability, usablity, feasibility