Urgent.News

What's breaking now, across thousands of outlets.

Tech

A confidence number your model reports is not a measurement

A confidence number your model reports is not a measurement The prompt line is almost universal: Answer the question, and also report your confidence as a number between 0 and 1. The model obliges. {"answer": "...", "confidence": 0.92} comes back, and somewhere downstream the code does the obvious thing: if result [ " confidence " ] > 0.8 : apply ( result [ " answer " ]) # auto-accept else :…

A confidence value generated by a model is not a genuine measurement. It is produced alongside the answer during the same forward pass, without any reference to the actual outcome. Measured numbers, on the other hand, are obtained by recording the number and the corresponding result, then comparing them in a database. This distinction is not merely semantic; it is crucial for how the number behaves and what can be derived from it.

Simply asking the model to be more calibrated does not address the fundamental issue, as it only alters the distribution of reported numbers without establishing the necessary recorded outcome. To determine whether you are dealing with a decorative confidence number or a measured probability, examine the shape of the distribution.

Decorative numbers tend to be high and narrow, showing little change when the problem becomes harder. Measured numbers, however, fluctuate more depending on the difficulty and the actual evidence involved. One practical way to distinguish between the two is to pose the same question with different prompts and observe the change in the confidence value.

Measured numbers will adjust based on the difficulty, while decorative numbers will remain relatively constant. A more reliable method is to check if the logs contain the outcome column. If they do not, the number is merely a stylistic choice rather than a verified probability. To improve the situation, make the judgement-making process a separate component with a contract, and log each decision along with its confidence value, inputs, and the action taken.

This allows for tracking the per-band hit rates and ensures that the confidence numbers are based on actual outcomes rather than just sounding convincing.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

"In Betrieb" Is Not "Free". Live Connector Status Across Five European Countries.

Every European country now publishes where its public charge points are. That was the easy half, and the Alternative Fuels Infrastructure Regulation is the reason it happened: since April 2024…

  • EU mandates machine-readable data for public EV charging stations since April 2024.
  • Germany's registry shows 154,210 active charging records but only 116,422 with availability status.

[$] Vendor hooks in the Android kernel

Since Android's inception, the kernels it has used have diverged significantly from the mainline. While many of those differences have been resolved over time, and the move to the generic kernel image…

Your coding agent is bad at Docker, and it isn't the agent's fault

I let a coding agent run my local stack for a few months. It writes the compose file, brings the services up, reads the logs, fixes the bug, and checks the fix worked. It's good at most of that.

  • Coding agent struggled with Docker interface designed for humans
  • Workarounds improved agent performance by reducing wasted turns

Failover beyond DNS

So you've built a service and it's running in the cloud. It sits in a Kubernetes cluster, it's designed for high availability, and every component has a replica.

  • Web-Engine Sentry experienced DNS fault disruption on October 20, 2025
  • Decentralized endpoints across domains and DNS providers for failover
  • Sentry SDK acts as gateway to available service endpoints

More from Thursday 15 October →