In certain conditions, the white walls at home take on the character of a light box. In traditional Japanese architecture the intensity of atmosphere has a lot to do with the way natural light is filtered through the shoji paper panels, suffusing the interior spaces with subdued light, calming the spirit and sharpening the senses.
In optics, a caustic is the envelope of light rays reflected or refracted by a curved surface or object, or the projection of that envelope of rays on another surface. The caustic is a curve or surface to which each of the light rays is tangent, defining a boundary of an envelope of rays as a curve of concentrated light.
A piece of milled plexiglass acting as a projecting lens; via the Computer Graphics and Geometry Lab at the École Polytechnique Fédérale de Lausanne
New milling techniques applied to glass and plexiglass panels could be used to “create windows that are also cryptic projectors, summoning ghostly images from sunlight.”
[Pauly and Bompas] hope that the technique will be used in architectural design, to create windows that mould sunlight and throw images or patterns onto walls or floors,” which, if timed, milled, and manipulated just right, could produce a slowly animated sequence of images being projected by an otherwise empty window during different times of day.
To control the shape of a caustic pattern generated by a specular or refractive surface, we need to solve the inverse problem: how can we change the surface geometry, such that incident light is redirected to produce a desired caustic image?
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.
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.
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.