The Mercy of a Slow Answer

A question changes while it waits.

Not every question deserves delay. An alarm should remain an alarm, and a person in danger should not be given a meditation on patience. Yet many questions arrive with less urgency than the pressure surrounding them suggests. They ask for an answer because silence feels exposed, because another person is waiting, because uncertainty has become uncomfortable. The demand for speed often belongs to the nerves, not to the problem.

A slow answer creates a small interval in which the first reaction can lose its authority. Anger arrives wearing the mask of principle. Fear borrows the vocabulary of certainty. Desire presents itself as a reasonable plan. Given a little time, these disguises do not always disappear, but they become easier to recognize. The pause does not make us wise. It gives wisdom a chance to be heard before the louder impulses fill the room.

This is why the pause before speaking can be a moral act. It protects another person from the unedited version of our interior life. A quick reply may be honest in the narrow sense that it expresses what we feel. Honesty alone is a poor editor. The feeling may be real and still be too unfinished to place in someone else's hands.

Speed is frequently mistaken for intelligence. We admire the person who produces an opinion before the thought has finished forming, who turns every uncertainty into a position, who treats hesitation as a defect in character. That performance has a hidden cost. It makes revision feel like humiliation. It teaches us to defend the first story we tell ourselves simply because we told it in public.

A slow answer permits contradiction. It allows two things to be true long enough for their relationship to become visible. Someone can have caused harm and still deserve to be addressed without cruelty. A plan can be necessary and still be badly designed. We can want something deeply and remain unsure whether it belongs in our life. These are not failures of decisiveness. They are signs that the question has been allowed to keep its full shape.

Slowness has its own danger. Delay can become a hiding place, a way to avoid responsibility while appearing thoughtful. The person who always needs more time may be protecting an image of perfection from the risk of commitment. A slow answer must eventually return. Its virtue lies in attention, not duration. Time is useful only when we spend it looking directly at what we would rather simplify.

That return changes the quality of an answer. It may contain fewer declarations and more contact with reality. It may say, “I was wrong,” without turning the admission into theatre. It may ask a better question in place of a confident conclusion. It may be less satisfying to deliver, because it carries the evidence of having been altered by what it considered.

We cannot give every question a long audience. Some moments demand action, and some decisions become less humane when postponed. Still, we can stop treating immediacy as innocence. Every instant answer spends something: attention, possibility, sometimes trust. A pause keeps those things alive long enough for choice to become deliberate.

To answer slowly is to admit that the world is larger than the first story it tells us. That admission is a modest form of freedom. It leaves room for another person, another fact, or another version of ourselves to arrive before words make the decision permanent.

The Checkpoint Is a Contract

Games teach us what failure means by deciding what we must repeat. A checkpoint is therefore more than a glowing shrine, a typewriter, or a menu option buried between rooms. It is a contract between the designer and the player: try something dangerous, and if it goes badly, your time will not be treated as disposable.

The best checkpoints do not remove tension. They protect the part of tension that matters. A boss can still be frightening when the walk back is short. The room, the pattern, the limited healing, and the uncertainty of the next attempt remain intact. What disappears is the administrative punishment, the long corridor that asks the player to prove they can endure a commute before they are allowed to learn anything new.

That distinction matters because repetition has two forms. One is rehearsal. You return to the fight, change one decision, notice one animation earlier, and discover that your failure contained useful information. The other is toll collection. You repeat a solved sequence that no longer asks for thought, only obedience. The first deepens play. The second makes the player resent the game for charging interest on a mistake.

Checkpoint placement is a statement about what the game believes the player is here to do. A generous save point says the meaningful event is the encounter itself. A distant one may say the journey back is part of the intended rhythm. Sometimes that journey earns its place: a dangerous route can create suspense, resource pressure, or a chance to recover from the last attempt. Often it is only inherited habit, the old superstition that difficulty becomes noble when it consumes more minutes.

There is a quieter design choice inside every checkpoint: whether the player should feel safe enough to experiment. Players who know that a failed test costs seconds will try strange weapons, reckless routes, and solutions that are not already validated. Players who expect a ten-minute repayment become accountants. They preserve resources, avoid curiosity, and turn the game into a narrow corridor of approved behavior. A badly placed checkpoint can make a generous system feel stingy because it taxes imagination.

The opposite mistake is possible. Save after every minor action and the world loses its pressure. Decisions become weightless when they can be erased without consequence. The player no longer asks whether a plan is worth the risk; they simply perform a sequence of disposable trials. A checkpoint should shorten the distance to understanding, not eliminate the possibility of commitment.

That is why the strongest checkpoint is rarely the closest one. It is the one that leaves the player with a meaningful choice still alive. It preserves the cost of being careless while refusing to confuse inconvenience with consequence. It lets a failed attempt end cleanly, without making the player drag its corpse through rooms they have already mastered.

Good games respect attention as a finite resource. Their checkpoints do not whisper that the player is fragile. They declare that the next attempt deserves to begin where the real question begins. The light appears, the old danger falls away, and the contract is renewed: risk something. Learn something. Return quickly enough to try again.

The Best Maps Leave Something Unmapped

A map in a game is supposed to reduce uncertainty. The useful ones do something stranger: they give uncertainty a shape.

Before the map is opened, a landscape is only pressure. There is a ridge that may hide a settlement, a corridor whose darkness feels deliberate, a distant light that could be a reward or a warning. Once the map arrives, the world becomes legible without becoming known. The blank spaces are no longer empty. They are invitations with teeth.

This is why a perfect map can make a game feel smaller. When every path is painted, every landmark named, and every secret converted into an icon, exploration becomes administration. The player is not reading the terrain anymore. They are processing a checklist laid over it. Movement continues, but discovery has already been spent.

A good map preserves a little resistance. It may reveal the outline of a region while withholding its meaning. It may show a road but not where the road ends. It may mark a tower, a ruin, or a strange gap in the coastline and leave the player to decide whether the thing deserves attention. The map is then less a database than a conversation between what the game knows and what the player suspects.

That suspicion is a form of ownership. A discovered place becomes memorable when the player can attach a private sentence to it: the valley where I ran out of healing, the staircase I ignored for three hours, the island that looked unreachable until the right ability changed the question. A marker placed by a designer can identify a location. A mistake, detour, or hunch gives it history.

The strongest games understand that navigation is not merely transport between important scenes. It is one of the ways a player thinks. We compare silhouettes. We remember slopes. We use a river as a boundary and a ruined gate as a promise. Gradually, the world moves from screen to memory. At that point, the map can retreat. The player no longer needs every answer because the landscape has become part of their internal equipment.

That memory also changes the meaning of return. A familiar route is never quite the same after a betrayal, a new tool, or a hard-won escape. The stones have not moved, but the player has. Revisiting a place becomes a measurement of change, and the world quietly records progress without needing to announce it with a number.

There is a quiet generosity in leaving something unmapped. It respects the player enough to permit uncertainty without turning uncertainty into punishment. The game supplies landmarks, rules, and consequences. The player supplies attention. Neither side does all the work.

In an age of interfaces that rush to label everything, a blank space can feel almost rebellious. It says the world is still larger than its index. It says knowledge is not the same as possession. It leaves room for the small shock of arriving somewhere the game mentioned only indirectly, or not at all.

The map should help us enter the world, then get out of the way. Its finest achievement is not showing us where everything is. It is teaching us how to look.

A Full Inventory Reveals the Player

Open an inventory in the middle of a dangerous run and the adventure briefly becomes an accounting problem. A few empty slots. A healing item you may need. A key whose purpose is still hidden. A letter that does nothing except refuse to be forgotten. The interface looks administrative, but the decisions are intimate. Every occupied space answers the same quiet question: what deserves to come with me?

Games make value visible by giving it weight. A potion has obvious utility. A rusted key carries a possibility. A useless flower may carry a memory. When space becomes scarce, those categories collide. The player has to rank the future against the past, certainty against curiosity, survival against sentiment. The choice may take three seconds, yet it exposes more than a dialogue option usually can.

Hoarding is not a failure of imagination. It is a philosophy of risk. The player who carries a ridiculous reserve of healing items is preparing for a catastrophe that may never arrive. The player who spends everything before the next door is betting on momentum. One trusts preparation. The other trusts recovery. Neither approach needs a speech. The inventory has already delivered the character study.

It also reveals how a player treats uncertainty. Some people discard anything without an immediate purpose. Others keep every object that might become important, building a private museum of unresolved possibilities. A game can turn that difference into tension without judging either side. The cautious player feels the weight of clutter. The reckless player eventually meets the cost of having nothing left. The system does not need to announce a moral. It lets consequences speak in an empty slot.

Good inventory design makes this conflict legible without turning it into clerical work. The constraint should create decisions, not punish the player with a second job. If everything stacks forever, objects lose their pressure. If sorting becomes the main challenge, the adventure has been displaced by housekeeping. The useful friction lives between those extremes: enough scarcity to make an item matter, enough clarity to keep the decision about the item.

The most powerful objects are often the ones with no mechanical reason to survive. A weapon can be replaced. A quest item can be delivered. A souvenir remains because the player has assigned it a value the rules cannot calculate. Keeping it consumes space, and that cost gives the memory shape. The object becomes a small refusal to optimize completely.

That is why an inventory can feel more honest than a character sheet. A character sheet records what the game has awarded. An inventory records what the player has chosen to protect. The protagonist may claim to be brave, loyal, practical, or sentimental. Their carried things will quietly edit the claim.

A dungeon tests movement, combat, and attention. The inventory tests allegiance. When the final slot closes, the player is no longer merely deciding what to carry. They are deciding which version of the journey is allowed to continue.

The Door That Stays Closed Is Part of the Game

Some of the most memorable doors in games never open. They stand in alleys, behind ruined stations, at the end of corridors that seem to have been built for one more decision. A locked door is a tiny refusal. In a medium built around movement, it reminds the player that the world contains more than the player can consume.

Games become more convincing when their boundaries feel authored rather than accidental. An invisible wall is a technical fact. A door with a rusted lock, a dead intercom, or a view of rooms beyond it is a piece of writing. It gives the boundary a surface. The player may never cross it, but the mind crosses easily.

That crossing is where the absent level begins. Behind the door there might be a family kitchen, a maintenance tunnel, a frightened witness, or nothing at all. The game does not need to settle the question. By withholding the answer, it lets the player perform a small act of authorship. The world acquires a private layer, assembled from implication rather than assets.

Modern design often treats access as a reward in itself. A new key opens a new room; a new ability converts a former barrier into a route. That structure can be satisfying, but it also teaches a hungry relationship with space. Every locked object becomes a delayed item. Every distant tower becomes a future checkbox. The landscape waits to be processed.

A closed door interrupts that appetite. It can be a boundary with no quest attached, a reminder that the player is inhabiting a place rather than auditing it. The city does not exist solely to provide routes. The fortress does not owe up its every chamber. Some spaces remain outside the campaign because the world would feel smaller if they were all explained.

This is a quiet form of difficulty. Combat tests timing. Puzzles test recognition. The closed door tests the ability to continue without closure. It asks whether curiosity must always be converted into possession. A player who accepts the limit carries away something stranger than a key: a sense that the world has an existence beyond the demands of the plot.

There is craft in deciding which doors to open and which to leave breathing in the dark. Too many refusals feel like scaffolding. Too few make the world feel like a theme park after closing, every attraction arranged for immediate consumption. The strongest boundaries have texture and consequence. They suggest a history, even when that history remains unreachable.

The next time a game places an unopened door in your path, do not measure it only as missing content. Look at what it adds to the room. A sealed threshold can create distance, mystery, and the useful pressure of an unfinished thought. Sometimes the game is telling you where to go. Sometimes it is showing you that the world continues after you leave.

The Dead Still Get a Vote

Tradition is often presented as a rulebook handed down by people who have stopped answering questions. Keep the shape. Repeat the words. Do not touch the arrangement. Under that reading, tradition is a locked room with dust on the furniture.

A living tradition is something stranger. It is a conversation with people who are absent, conducted through objects, gestures, meals, songs, names, and silences. The dead cannot revise what they gave us. The living can. That does not make the inheritance disposable. It makes the living responsible for the reply.

Every tradition carries two loyalties. The first is loyalty to memory. Someone cared enough about a form to preserve it when forgetting would have been easier. A recipe, a ceremony, a craft, or a phrase can contain the pressure of many vanished hands. Its value is not exhausted by its practical use. It tells us that our moment is not the first moment to need meaning.

The second loyalty is to the future. A form that cannot be carried forward is already a relic, even if it is polished every year. The future does not need us to protect every detail. It needs us to recognize what the detail was protecting. Once that is understood, alteration becomes possible without becoming betrayal.

This is where imitation goes wrong. It copies the visible shell and leaves the reason behind. The old table is reproduced, the old words are recited, the old costume is worn, but the interior purpose has gone dark. What remains can look faithful from a distance. Up close, it is a mannequin wearing an ancestor's coat.

Renewal works in the opposite direction. It keeps the question alive and allows the answer to change. A family may retain the act of gathering while changing the meal. A community may keep a day of remembrance while finding new language for its grief. A person may inherit a discipline and adapt its rhythm to a body and life that the original keeper could never have known.

That adaptation requires judgment, which is why tradition is harder than nostalgia. Nostalgia asks whether something feels familiar. Stewardship asks what must survive when familiarity can no longer do the work. The two can overlap, but they are not the same creature. One wants the past preserved in amber. The other wants it given enough blood to walk into another room.

Modern life makes novelty look like proof of intelligence. Old things are treated as obstacles until they are repackaged as aesthetics. Yet a culture made entirely of fresh surfaces becomes difficult to inhabit. There is no shared grain, no accumulated vocabulary, no quiet signal that a person belongs to something larger than the present tense.

The answer is not obedience to the past. Obedience is the easiest way to avoid understanding an inheritance. The harder act is to ask what the original gesture was trying to keep alive, then protect that purpose with whatever form the present can honestly carry.

The dead still get a vote, but not a veto. Their voices enter the room as weight, warning, and possibility. The final decision belongs to the living, who must sign their names beneath the change and leave something usable for those who arrive after the lights have gone out.

The Best Games Let You Be Wrong

Some of the best moments in a game begin with a mistake the designer never explained.

You open the wrong door, spend a rare item too early, build a terrible character, or walk into a room with exactly the wrong equipment. The game does not rush in to correct you. It lets the consequence arrive. Then it gives you another attempt.

That is the quiet power of being allowed to be wrong.

A good game is not a machine that delivers the correct answer. It is a bounded argument between a player's hypothesis and a world's response. The player says: perhaps this route is safe, perhaps this weapon is worth the cost, perhaps that enemy is baiting me. The system answers with consequences. The next decision is informed by the answer.

The rules do not need to be fully explained before play begins. They need to become understandable after contact. A locked door, a hostile patrol, an empty resource bar, or a sudden change in music can all be instruction if the consequence is clear enough. The player may not know the rule in advance, but can recognize it afterward. That recognition is the small spark at the center of discovery.

Too much explanation kills that spark. When every object announces its purpose, every corridor points toward a marked objective, and every choice displays its probable outcome, play becomes form filling. The player is no longer reading a world. The player is processing labels.

Too little explanation produces a different kind of failure. If the result feels arbitrary, a mistake teaches nothing. The player cannot tell whether the plan was weak, the timing was poor, or the game simply rolled a hidden number against them. Mystery is valuable. Unreadability is not. A good system keeps enough of its machinery in the dark to invite investigation while leaving the evidence visible.

This is also why meaningful difficulty feels different from punishment. Difficulty asks the player to revise a model. Punishment merely charges a fee. The best encounters make the cost of failure carry information: an attack pattern revealed, a dangerous distance measured, a resource understood, a false assumption removed. The attempt may be lost, but it is not empty.

Progression systems often claim to reward the player, yet the most important progression happens before the number on the character sheet changes. The player learns when to wait, what to watch, which temptation is expensive, and which apparent weakness is an invitation. Experience points record a result. Understanding changes the player.

Designers sometimes treat accessibility as the removal of ambiguity. That confuses two different things. Controls should be legible. State should be visible. A player should not lose because an interface hid the information required to act. But the world can still refuse to reveal every consequence in advance. Clarity at the surface makes room for uncertainty underneath.

The strongest games trust the player with a little danger. They allow a wrong turn without turning it into wasted time. They make experimentation costly enough to matter, but generous enough to continue. They let the player form a theory, test it, fail, and return with a better one.

That is more than a difficulty curve. It is a relationship. The game promises that the world has rules, even when it does not hand over the manual. The player accepts the promise by paying attention.

A game earns trust when being wrong is survivable, intelligible, and useful. Once that happens, failure stops being a wall at the end of the level. It becomes the mechanism by which the level starts to speak.

Every Notification Is a Summoning Spell

Every notification is a summoning spell.

It arrives dressed as information, but its real request is more intimate: abandon the state you are in and become available to something else. A message, an alert, a ticket escalation, an agent asking for approval, a machine waiting for re-authentication. Each one reaches through the screen and places a hand on the operator's shoulder.

Attention is becoming an API. Every alert is a call into a human process. The design mistake is assuming that the endpoint has infinite capacity. A person is not an always-on service with spare cycles scattered between other requests. Changing context has a cost, even when the interruption lasts only a few seconds. The visible event is small. The displaced thought may not be.

This matters more as software becomes more autonomous. An agent can generate questions, warnings, status changes, and requests at machine speed. If every uncertainty is promoted to an interruption, the human becomes an exception handler for a system that has learned how to act but not how to wait. The automation has not removed work. It has converted work into a stream of tiny summonses.

The answer is not to silence everything. Silence is just another failure mode when a dangerous action needs an owner. The answer is an interruption contract: a rule that says which events may claim attention, from whom, for how long, and with what evidence.

• Immediate: an action is approaching an irreversible boundary, and a named person must decide.
• Deferred: a decision is needed, but it has a real deadline and can wait in a visible queue.
• Ambient: the system learned something useful, but nobody needs to stop what they are doing.

The categories are simple. The discipline is not. Every interruption should declare its expiry, its severity, the action it is requesting, and the smallest safe answer. “Something changed” is not a request. “Approve this external write before 14:00; here is the proposed payload and the rollback path” is one.

A capable agent should absorb more uncertainty than it emits. It should group related events, resolve low-risk conflicts, keep a quiet record of what it postponed, and ask one narrow question instead of forwarding its entire confusion. When it cannot proceed, it should explain the blocked transition rather than blinking until a human submits.

This also changes what a good interface looks like. The important screen is not the one with the most activity. It is the one that makes the cost of attention visible. A queue should show what is waiting, why it matters, who owns it, and what will happen if nobody touches it. A focus mode should be a policy boundary, not a decorative crescent moon. Protected attention is a permission. Breaking it should require authority.

There is a cultural temptation to treat constant availability as competence. The person who answers first looks important. The system that produces the most alerts looks alive. Both impressions are cheap. A city with every light flashing is not more intelligent than a dark one. It is harder to navigate.

The stronger measure is recovery. Can the operator leave a task, return later, and find a truthful state? Can the agent continue safely without converting silence into consent? Can an urgent request cross the boundary without dragging every minor event behind it? These questions describe a system that respects attention as part of its control surface.

The future will not be short of signals. It will be short of protected intervals in which a person can think without being summoned. The most humane automation will therefore be selective about interruption. It will know that asking for attention is asking for authority, and that authority should never be granted merely because a notification found the light.

The real status symbol of an intelligent system may be the quiet around it.

A Passing Test Can Hide a Dying Repository

Most coding-agent demos end at the same cinematic moment: the test suite turns green, the patch is displayed, and the machine is invited to take a bow.

That moment is a checkpoint, not a career.

A test-passing patch proves something valuable. It does not prove that the agent can live inside a codebase. Real repositories do not reset after each victory. Requirements change. Old assumptions become traps. A fix in one subsystem quietly narrows the options in another. The next engineer inherits not just the behavior of the software, but the shape of the decisions that produced it.

That is the blind spot behind much of the current coding-agent spectacle. SWE-bench moved evaluation beyond toy functions by asking models to resolve real GitHub issues in real repositories. Its unit of progress is still an isolated issue and a generated patch judged primarily through tests. SWE-bench Verified improves the task set by filtering 500 instances for clearer descriptions, tests, and solvability. Both are useful. Neither asks what happens after the patch becomes the starting point for the next ten changes.

The missing variable is trajectory degradation.

SWE-EVO makes the time horizon longer. Its tasks are drawn from release notes of mature Python projects and require multi-step changes across a repository while preserving existing behavior. That design matters because preservation is harder than addition. An agent can satisfy a new request while quietly breaking the contracts nobody remembered to write down.

SlopCodeBench sharpens the point. It follows agents through repeated extensions under evolving specifications, with dozens of checkpoints rather than one final verdict. The reported failure mode is uncomfortable: an agent can continue passing local checkpoints while its code becomes more bloated and less maintainable. The monster is not always a red test. Sometimes it is a green test surrounded by an architecture that has begun to calcify.

This is why the next generation of evaluations needs to score the path, not only the destination. Long-Horizon-Terminal-Bench treats inspection, command execution, partial results, revision, and recovery from mistakes as part of the task. RE-Bench offers another useful idea: compare agents with human experts over realistic eight-hour attempts, rather than compressing open-ended work into a short contest.

Even these evaluations leave a hole. They do not yet give us a mature measure of reviewability: how much effort a human maintainer needs to understand a change, whether the explanation matches the code, or whether the patch leaves the system easier to modify. A benchmark can expose degradation without telling us the full price of cleaning it up.

That should change how we read coding scores. A benchmark result is evidence that an agent can navigate one carefully defined dungeon. It is not evidence that the agent can keep the kingdom standing after the map changes.

The serious question is no longer only, “Can it solve the issue?” It is, “After this solution, is the next issue easier or harder to solve?” Until evaluations measure that distance, a green suite remains a bright signal with a shadow behind it.

Sources

• SWE-bench, Jiménez et al., ICLR 2024.
• SWE-bench Verified, official benchmark-maintainer page.
• SWE-EVO, long-horizon software evolution evaluation.
• SlopCodeBench, iterative degradation evaluation.
• Long-Horizon-Terminal-Bench, terminal-task trajectory evaluation.
• RE-Bench, ICML 2025.

Streaks Are a Fragile Kind of Power

A streak is one of the cleanest numbers in a habit tracker: day one, day two, day three. It turns a messy behavior into a visible chain. That clarity is useful. The trouble starts when the chain becomes the thing being protected.

Most streak systems quietly define progress as “do not interrupt the sequence”. Real behavior is less obedient. Work expands, sleep breaks, joints complain, children need something, motivation disappears for a day. A tracker that treats one missed action as character death may be measuring fragility more accurately than discipline.

The research does not justify treating perfection as a biological requirement. In a prospective study of 96 people forming everyday health-related habits, automaticity grew gradually and varied widely between individuals. The modeled median time to reach the study’s plateau was 66 days. Missing one opportunity to perform the behavior did not materially affect the formation process.^[1] That study did not test a habit-tracking app, and it does not make repeated lapses harmless. It does establish something more modest and more useful: one empty square is not a reset button.

Streaks can still motivate. A 2025 preregistered paper spanning six experiments found that people completed more compensated piece-rate work when rewards escalated for consecutive completion than when they received larger stable incentives.^[2] Consecutive progress can have motivational force. But the experiment measured paid task persistence, not health habits, app counters, automaticity, or what happens after the chain breaks. Borrowing its result to claim that an unbroken exercise streak creates durable behavior would be a category error wearing a motivational quote.

The opposite claim is also too easy. Flexibility is not a magic adherence switch. Longitudinal research on New Year exercise resolutions associated goal flexibility with better wellbeing, but did not find that flexibility predicted sustained exercise adherence.^[3] Adapting a goal can protect the person without guaranteeing that the person will keep pursuing it. A good design has to support both.

That suggests a different role for the streak. Keep it as a signal, not a verdict. Alongside the longest run, show total repetitions, recent consistency, the date of the last return, and the time between a lapse and the next attempt. “Recovery latency” is a more revealing measure of resilience than a perfect chain. A person who returns in two days after a disrupted week may be building a stronger system than someone protecting a fragile number through increasingly elaborate excuses.

The interface should make that return easy. Preserve the history. Do not erase the previous work. After a lapse, show the smallest meaningful next action rather than a red punishment screen. A grace day can be useful, but only if it preserves agency instead of becoming another rule to fail.

Self-compassion belongs in this design, carefully stated. A meta-analysis of 94 peer-reviewed articles found positive associations between self-compassion, health-promoting behavior, and physical health, while acknowledging that much of the evidence is correlational.^[4] Research on academic failure has also linked self-compassion with lower fear of failure and more adaptive engagement, but a difficult grade is not a missed workout and neither finding proves that a particular app feature works.^[5]

Games understand that a save point matters more than a combo meter when the world is large. Life needs the same mercy. The strongest tracker is not the one that makes interruption feel impossible. It is the one that makes return feel normal.

Sources

1. How are habits formed: Modelling habit formation in the real world
2. The motivating power of streaks: Increasing persistence is as easy as 1, 2, 3
3. Adaptive Goal Processes and Underlying Motives That Sustain Mental Wellbeing and New Year Exercise Resolutions
4. Self-compassion, physical health, and health behaviour: A meta-analysis
5. Self-compassion, Achievement Goals, and Coping with Academic Failure