The notion of a thermal optimum persists There is an underlying assumption that the best thermal environment never needs to be noticed, and that once an objectively "comfortable" thermal environment has been provided, all of our thermal needs will have been met. The use of all of our extremely sophisticated environmental control systems is directed to this one end—to produce standard comfort zone conditions. Lisa Heschong, Thermal Delight in Architecture heatcomfortenvironmentux
Interlocking "The art world is highly invested in the idea that you can take an object and set it in a room, and the internal relationships will be so strong and so meaningful that all the kinds of change that take place on the object as a result of its being in a new environment will not critically affect our perception of the object. If that is the given assumption, then the object can be moved from one environment to another without its being critically altered, which then gives rise to the illusion that it can be moved from culture to culture, that it has the ability to transcend its cultural specificity, which in turn gives rise to the ultimate illusion that the object can transcend time. Because what is being claimed is that there exist certain objects isolated and meaningful enough to be transcendent, that they have the power to go on and on, that they are, as it were, timeless. "Well, one of the things that I was becoming involved in at that point in playing artist was the growing suspicion that this breaking down of the edge, the idea of the painting's moving into its environment, was putting the whole heightened rationale of the art object into doubt. There is simply no real separation line, only an intellectual one, between the object and its time environment. They are completely interlocking: nothing can exist in the world independent of all the other things in the world." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees Deep Interlock contextchangeenvironmentobjects
Little sense of season The real world of technology denies the existence and the reality of nature. For instance, there is little sense of season as one walks through a North American or western European supermarket. Just as there is a little sense of season, there is little sense of climate. Everything possible is done to equalize the ambiance – to construct and environment that is warm in the winter, cool in the summer. Ursula M. Franklin, The Real World of Technology naturecyclesenvironment
The receiving end At times it helps to rephrase an observation in line with a perspective from the receiving end of technology. When my colleagues in the field of cold-water engineering speak of "ice-infested waters", I am tempted to think of "rig-infested oceans". Language is a fine barometer of values and priorities. As such it deserves careful attention. Ursula M. Franklin, The Real World of Technology valuesenvironmentlanguage
Walden A Book by Henry David Thoreau The quality of the dayI went to the woodsI love to be aloneQuiet desperationA new wearer of clothes+2 More Upstream ColorThoreau 2.0Upstream Color Original Soundtrack naturesolitudeenvironmentlabor
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