Working in raking light

In a conservation studio, the first thing anyone does with a painting is turn the room lights off and bring a lamp in from the side, almost parallel to the surface. Lit from the front, the canvas is an image. Lit from the edge, it is an object: every repair, every stretcher mark, every place where somebody pressed too hard eighty years ago stands up in relief.

Nothing new has been added. The information was always there; frontal light simply flattened it out of view. Conservators call this raking light, and it is the fastest diagnostic they have.

Most design reviews are lit from the front

A logo on a white slide at 40% of the screen, centred, at the presenter's chosen size, is the frontal photograph. It shows the image. It hides the object. It cannot tell you that the counters close up at 8 mm, that the name is eleven characters longer than the layout expects in German, or that the only version anyone will ever see is stitched into a fleece in one colour.

If a system only holds together in the conditions its authors chose, it is not a system. It is a photograph of one.

So we review in the conditions we did not choose. The first application we make is always the worst one available: the embroidery, the vinyl on a curved van panel, the 360 px viewport, the fax — and yes, in one recent healthcare project, genuinely the fax. If it survives there, the flattering applications take care of themselves.

What raking light looks like on a screen

For digital work the equivalent is a short list of deliberately hostile conditions, applied before anything is signed off:

• The longest real name in the dataset, not the shortest.
• A 360 px viewport with the system font, before the webfont loads.
• The empty state, with no content at all, and the overloaded state with four times too much.
• Keyboard only, with the pointer physically unplugged.
• Reduced motion on, and the GPU disabled entirely.

None of these are edge cases in the sense of being rare. They are the ordinary conditions of a system in use, which only look like edge cases from inside a studio where everyone has a fast machine and a short test name.

The uncomfortable part

Raking light is unflattering by design, and showing a client the unflattering version of your own work in week four is a genuinely unpleasant professional habit to build. It is also the only way to be believed in week twenty, when something breaks and you have already named it.

We have never lost a project by showing the failure modes early. We have lost several by discovering them at handover, which is the same information arriving at the worst possible moment, with somebody else's name on it.