Personalization on Programmer.ie: Modern AI programming

The Personal Experience

Thu, 01 Oct 2026 09:00:00 +0100

A few weeks into using the Radar, Iris notices that it behaves differently from the first day. Library updates no longer interrupt her. Papers arrive with the conclusion first and the method behind a click. Comparisons come as tables. Possible contradictions of her protocol arrive with the evidence attached, never as bare verdicts. Most of these changes are welcome. But when she asks why a particular item was presented that way, the answer is difficult to reconstruct. One rule came from something she explicitly said. Another may have come from a repeated action the system observed. A third may be a conclusion the system drew from that action. All three can change a view, but they do not have the same authority.

There Is No Universal Best Interface

Thu, 01 Oct 2026 09:00:00 +0100

The previous chapter ended with a temptation. Iris’s behaviour leaves traces. In the constructed session, she opens tables more often than prose, expands mathematical detail and leaves some diagrams unopened. A system with memory could turn these events into a convenient description: this person is a certain kind of reader. It could then serve that supposed type everywhere, without asking again. But the trace does not record what alternatives were available, why she opened each view, or whether she performed better afterwards. The classification would already be claiming more than the observation showed.

From Observation to Policy

Thu, 01 Oct 2026 09:00:00 +0100

Memory can be right and still make the present wrong

In March, Iris tells the system something important about a payments service.

The old replication path is gone, she explains. Production writes now go through quorum path B. She is describing the architecture for the incident review that afternoon, not issuing a permanent instruction about how the service will work. The statement has a speaker, a subject, a scope and a time. Those details will matter more than the sentence alone.

The Person Changes During the Day

Thu, 01 Oct 2026 09:00:00 +0100

Iris opens the system on her phone before an architecture review and says: I have five minutes before the meeting. Just tell me what can break. She is asking for a different first view. She is not withdrawing her interest in the implementation, and she is not authorising the system to guess what she can safely ignore. Five minutes is her stated time budget for this one encounter. It is not a measure of her attention span, and it is not a standing preference for short answers.

Sometimes the Best Interface Adds Friction

Thu, 01 Oct 2026 09:00:00 +0100

At the start of an evening study session, Iris says: For this session, I want to finish this paper first. Remind me before I open another one. Twenty minutes later, a new result arrives through a standing subscription that alerts her to papers matching her interests. The alert is only a candidate for her attention, not an instruction to abandon the paper. Chapter 20’s rules for when alerts may interrupt still govern whether it should appear now. When Iris finds the result in the reading tool and chooses to open it, a second question arises: may the interface place a reminder in the path of that action?

Protection That Travels

Thu, 01 Oct 2026 09:00:00 +0100

Iris has asked her reading tool to remind her before she opens another paper. She has separately authorised a temporary change to its recommendation view while she studies. Those permissions are local to the reading tool. They do not automatically apply to her news or video services, even when all three recognise the same account. When she moves to another service, its usual recommendations return.

She now makes a distinct request: For this evening’s study, keep new consensus-research recommendations out of the recommendation feeds in these two services. Leave search and direct opening available. End the rule when I finish the paper or end study, and no later than eight this evening. She reviews the named destinations, the feeds affected and the exceptions before accepting. A different service, a broader topic filter or a longer lifetime would require a different decision.

What the System Believes About You Must Be Visible

Thu, 01 Oct 2026 09:00:00 +0100

Iris opens a talk about a consensus algorithm she has not used. The channel shows its steps and a diagram, but folds the section that introduces the algorithm’s failure assumptions. She asks why. The answer is: Consensus foundations treated as already known, inferred from earlier architecture reviews. The explanation is plausible. That is precisely the danger: plausibility is not a record of which belief actually caused the omission.

Iris knows the field. But knowing the field does not establish that she knows this algorithm’s assumptions, and knowing them would not make them optional when they qualify a result she is being shown. The first defect is the unsupported extension from one protocol to another. The second is a preservation failure: even a genuinely expert reader needs the scope of the claim. A better explanation alone would not repair either defect; the view has to be checked before the assumption can be hidden.

The Personal AI

Thu, 01 Oct 2026 09:00:00 +0100

At twenty past nine, Iris begins an architecture review. The channel already holds a standing policy that Iris declared, observations from earlier reviews, and a provisional inference about derivations. It can also create a temporary view and apply two narrowly authorised boundaries. All of these mechanisms now coexist, but coexistence is not a reason to consult all of them. This is a constructed session, not a report of a person using the complete system.