VARC Practice Set 3

For a long time, sleep was understood mainly as rest: a period in which the body and brain, worn out by the day, simply switched off. Research over the past few decades has overturned this picture. The sleeping brain is busy, and much of its activity appears to concern memory. Experiences encoded during the day are replayed, strengthened and reorganised at night, in a process researchers call consolidation.

Evidence comes from several directions. In rats, neurons in the hippocampus that fire in a particular sequence as the animal runs a maze fire in the same sequence during subsequent sleep, as if the route were being rehearsed. In humans, people who learn a list of word pairs or a motor skill and then sleep tend to perform better on later tests than those who spend the same interval awake. Some studies have even found that sleep helps people extract hidden rules from what they learned—noticing a shortcut in a task that they had not consciously spotted while awake.

Different stages of sleep may contribute differently. Deep, slow-wave sleep, more common early in the night, has been linked to the consolidation of facts and events. Rapid-eye-movement sleep, which dominates the hours before waking, has been associated with emotional memory and with the integration of new information into existing knowledge. If this division is right, cutting a night short does not simply reduce sleep by a proportion; it disproportionately removes the stage that is concentrated at its end.

Caution is needed. Many studies are small, effects vary across tasks, and it is difficult to separate the benefits of sleep from the harms of sleep deprivation. Still, the implications are significant for students who sacrifice sleep to study. The hours given up may be precisely the ones in which the studying would have been made to stick.

For centuries before steamships, trade across the Indian Ocean was governed by the wind. The monsoon blows from the south-west for part of the year and from the north-east for another part, and sailors learned to time their voyages accordingly: east from Arabia and East Africa towards India in one season, west again in the other. A merchant who missed the season might wait months for the wind to turn.

This rhythm shaped more than shipping schedules. Because traders often had to spend months in foreign ports waiting for the return wind, they formed communities abroad, married locally and built networks of trust that spanned the ocean. Port cities from Kilwa to Calicut to Malacca became cosmopolitan places where many languages were spoken and where credit could be extended to a stranger on the strength of family and religious connections.

The system was decentralised. No single empire controlled the Indian Ocean before the sixteenth century; rulers of port cities generally sought to attract merchants with low taxes and security rather than to monopolise trade by force. When Portuguese fleets arrived and tried to control the trade through armed passes and fortified bases, they disrupted this arrangement, but they did not replace it. Much commerce simply moved to ports beyond their reach.

Historians have drawn different lessons from this history. Some see in it an early form of globalisation that flourished without a dominant power, a reminder that open exchange does not require an imperial guarantor. Others caution against romanticising it: the monsoon world included slavery, piracy and exploitation, and its openness depended on rulers whose interests happened, for a time, to favour it.

Why do people travel great distances to look at broken buildings? A ruined abbey or a crumbling temple is, on any practical measure, a failure: it no longer keeps out the rain or serves the purpose for which it was built. Yet ruins have attracted painters, poets and tourists for centuries, and some eighteenth-century landowners went so far as to build fake ruins in their gardens.

One explanation is that ruins make time visible. A new building conceals its age; a ruin displays it, in weathered stone and fallen arches. Standing before it, the viewer senses both the ambition of those who built it and the forces that undid it. The pleasure is mixed with melancholy, since the ruin reminds us that our own works will share its fate. Writers of the Romantic period valued precisely this mixture, which they distinguished from simple beauty.

A second explanation concerns imagination. A complete building tells the viewer what it is; a ruin leaves gaps that the viewer must fill. The missing roof invites us to picture it; the empty niche suggests a vanished statue. In this sense a ruin is unfinished in a way that engages the mind, much as a sketch can be more evocative than a finished painting.

Both explanations face an awkward fact: many celebrated ruins have been extensively stabilised and partly rebuilt. Walls are reinforced, loose stones are fixed in place and vegetation is cleared. The ruin that visitors admire is often a carefully maintained arrangement, preserving the appearance of decay while preventing further decay. Some critics find this dishonest. Others reply that every encounter with the past is mediated, and that a managed ruin is no more artificial than a museum.

For delivery riders and ride-hailing drivers, the boss is often an app. Software assigns tasks, sets routes, calculates pay and evaluates performance through customer ratings and acceptance rates. Companies describe this as flexibility: workers choose when to log on and are free from the petty tyrannies of a supervisor. Many workers do value the freedom to set their own hours.

But the freedom has limits that are not always visible. Pay rates can change without notice, and the formulas behind them are rarely disclosed. A driver who declines too many requests may find that fewer arrive. Workers can be deactivated—in effect dismissed—on the basis of ratings or automated flags, sometimes with little explanation and no human to appeal to. Control has not disappeared; it has been embedded in code.

This form of management also shifts risk. Because platform workers are usually classified as independent contractors, they bear the costs of vehicles, fuel and insurance, and they are paid only for completed tasks, not for time spent waiting. When demand is low, the platform loses little; the worker loses the hours spent waiting. Courts in several countries have begun to question whether workers who are so closely directed by software can really be called independent.

Defenders of the platforms argue that stricter rules would raise prices, reduce the number of jobs and destroy the flexibility workers value. Critics respond that flexibility and protection are not opposites: workers could keep control over their hours while gaining transparency about pay and a right to contest deactivation. The debate is partly about economics and partly about a question older than any app—how much power one party to a contract should hold over the other.