There is a particular quality to the middle of July. The year is no longer new and not yet closing, the pace of work slackens without quite stopping, and a good number of the people you would normally hear from are somewhere else. Nicole Junkermann has come to treat this stretch as a kind of annual audit, though not of the sort that involves spreadsheets. It is an audit of attention. When the demands of an ordinary week fall away, what is left still asking for you? That question, she finds, sorts software more honestly than any feature list.
Most technology is designed for presence. It assumes you are there, that you will come back shortly, that the gap between one visit and the next is a problem to be solved rather than a normal part of a life. You can see the assumption in the way things behave when you step away. A quiet week produces a small pile of prompts asking whether you have forgotten something. A fortnight produces a campaign. The tool has been built by people who imagined an engaged user at a desk, and it does not know what to do with a person on a train with the phone in a bag.
The alternative is not less capable software. It is software designed for absence, which is a genuine design discipline and a harder one. A tool built for absence assumes the gap. It expects that you will leave, that you will be gone for longer than it would prefer, and that when you return you will want the situation to make sense without an apology or a tour. It holds its state. It does not punish the interval. Nicole Junkermann's view is that this is not a nicety bolted on at the end but a decision made early, in the same conversations that settle what the thing is for.
Think about what this means for the ordinary categories. A calendar that respects a break does not merely mark you as away; it behaves as though the away is real, and it lets the people around you see the shape of your absence without needing you to explain it twice. A messaging app that respects a break lets a conversation sit without implying that the silence is rudeness. A photo library that respects a break simply collects what you take and asks nothing of you until you are home and curious. A note-taking tool that respects a break is exactly where you left it, with the same half-finished thought at the top, and no suggestion that the thought has gone stale in your absence. None of that is technically demanding. It is a matter of intent.
What makes the intent rare is that the alternative is easy to measure and this is not. It is straightforward to count how often someone opens an application and to treat the number going up as progress. It is much harder to count the times a tool decided not to interrupt, and harder still to put a value on the afternoon that stayed uninterrupted as a result. So the measurable thing wins by default, not because anyone chose noise over quiet, but because noise leaves a mark on a dashboard and quiet does not. Nicole Junkermann has watched this dynamic play out often enough to think it explains more bad product behaviour than any real appetite for it.
There is a test she keeps for this, and mid-July is when it can actually be run. Leave for two weeks. Come back. Ask, of each tool, one question: did it need me, or did it merely want me? The difference is usually obvious the moment you look. A tool that needed you has a genuine backlog waiting, work that could not proceed without a decision only you could make, and it presents that backlog plainly. A tool that wanted you has manufactured a reason to be reopened. The first is doing its job. The second is doing its own marketing, using your attention as the budget.
The rewarding part of the test is how often things pass. A great deal of software is quietly well behaved and never gets credit for it, because good behaviour is invisible by construction. The tools that kept their place over a fortnight, that let the fortnight be a fortnight, are doing something genuinely difficult, and the reward for doing it well is that nobody notices. Nicole Junkermann thinks this is worth saying out loud occasionally, if only because the people who build calm things rarely hear that anyone spotted the calm.
The habit runs on from there into how she reads the rest of the year. A team that thought carefully about what happens when a person disappears for two weeks has almost certainly thought carefully about other things too. Designing for absence requires imagining a user who is not enthusiastic, not fluent, and not available, which is to say a real one. It is a form of respect that shows up in the code long before it shows up in the copy, and it tends to travel with other good instincts, the same ones explored in the notes on human skills and in the earlier reflection on calm summer tools.
None of this argues for doing less with technology. The point is nearly the opposite. The tools worth keeping are frequently the ones doing the most work, because work done properly in the background is precisely what buys the quiet. A system that handles the routine without narrating it is more capable than one that asks permission at every step, not less. Capability and clamour are separate axes, and it is easy to mistake the second for the first when the second is the only one you can see.
So the mid-July note is a short one. The best thing a piece of software can do this fortnight is let you forget it exists, and be unremarkable when you come back. That is not a low bar dressed up as a virtue. It is a real standard, met by fewer tools than you would hope, and worth noticing in the ones that clear it. Nicole Junkermann will carry the list of those that did into the second half of the year, where it will be more useful than any amount of enthusiasm gathered in a busier month. The reading list and the shorter tech notes pick the thread up from there.