You Might Fail the Exam You Studied So Hard For Because of a Pencil

Sanni Shazily — Tue, 01 Sep 2026 18:43:43 +0000

And it might have nothing to do with whether you knew the answers.

This article was inspired last Friday.

I was writing my last exam as a sophomore, staring at an OMR sheet, when I changed one of my answers.

I had shaded B.

Then I became convinced B was wrong.

So I erased it, shaded D, looked at the paper and moved on.

Except the old B wasn't completely gone.

You could still see it if you looked closely.

And that got me thinking.

What does the machine see?

Not what I see. Not what I intended. What actually happens when that sheet eventually goes through the scanner?

I went looking for the answer.

And OMR is a little more interesting than the instructions on the back of the answer sheet make it seem.

Your eraser doesn't actually erase the past

When you erase a bubble, you're trying to make the scanner believe that the mark was never there.

But graphite doesn't simply disappear. Some of it can remain in the paper, and whether that remaining trace matters depends on how the particular OMR system interprets it.

Researchers have actually tested this with Scantron sheets. They shaded bubbles, waited different amounts of time, erased them and then ran the sheets through a Scantron OMR scanner.

The machine could still distinguish different levels of darkness in marks that had been erased. In their experiment, some relatively recent erased marks were still being detected as intermediate-strength marks, while marks that were harder to erase could remain much darker.

So when you look at an erased bubble and think,

"It's basically gone."

the machine may have a different opinion.

But that doesn't automatically mean you lose the question.

One documented Scantron system could compare multiple marks and use the darkest one as the final answer. So if your old B left a faint trace while your new D was heavily shaded, the system could still recognize D.

Other systems are stricter.

The University of Hawaiʻi's actual exam-scanning service says that incomplete erasures can result in a MULT entry in the exam data when the scanner cannot distinguish the old mark from the new one.

The machine doesn't know that you changed your mind.

It only knows what survived on the paper.

What about that tiny accidental pencil touch?

If you're shading C and your pencil barely touches D, the scanner isn't necessarily going to scream MULTIPLE ANSWERS.

OMR systems are built around thresholds. A tiny amount of graphite can remain below the level required to count as a response.

But make that accidental mark substantial enough, and you're in different territory.

Penn State's scanning guidance explicitly warns that stray marks and incomplete erasures can be interpreted as extra marks, potentially making the answer incorrect.

So there's a huge difference between a tiny graphite ghost and another visibly shaded bubble.

The machine doesn't care that one was "accidental."

It only cares whether the mark looks significant enough to count.

The mistake that worries me more

Skipping a question.

Suppose Question 41 is difficult, so you leave it blank and move to Question 42.

If you correctly put Question 42's answer on the Question 42 row, everything is fine.

But if you lose your place and start filling one row too early, something much worse can happen.

The scanner may read your answers perfectly.

Just for the wrong questions.

That's because an erased mark is a recognition problem. The system has to decide whether that faint graphite counts.

A shifted answer is a position problem. The machine already knows exactly what you marked. It simply doesn't know what you meant to mark.

Some real Scantron workflows explicitly report skipped questions as blank responses, while column or row shifts can require manual correction. Carleton University, for example, warns that a student who jumps a column can create a serious scanning problem requiring hand marking.

That's a much scarier thought.

A faint erased mark might be ignored.

A perfectly shaded answer in the wrong row can be read flawlessly.

Someone actually built a dataset for this

While researching this, I found something almost absurdly close to the question I was asking.

A research dataset called Wild-OMR, released in July 2026, contains hundreds of captures of pencil-filled answer sheets. Researchers deliberately created five sheets with scripted erasures, where they filled a wrong option, erased it, and then filled the intended answer. They then captured those physical sheets under different conditions and released the scans, annotations and OMR predictions.

So this isn't merely an exam-hall myth.

People are actually studying what happens when students do exactly what we do under pressure.

And the answer isn't simply:

"The scanner knows."

It doesn't.

It measures.

It classifies.

And sometimes it gets an ambiguous result.

Which brings me to the ultimate advice I wish every student took seriously

Be very sure before you shade.

Not because changing an answer will definitely ruin your exam. It won't.

Real systems can successfully recognize a new answer after an old one has been erased, and some systems are capable of distinguishing a strong new mark from a weak residual one.

But you've created uncertainty where there didn't need to be any.

You started with:

one answer, one bubble, one clear signal.

Then you turned it into:

old graphite + erasure + possible residue + new graphite + whatever recognition rules that particular scanner uses.

Why introduce all of that if you don't have to?

If you're genuinely unsure, think again. Check your reasoning. Compare the options. Make the decision.

Then shade.

And once you shade, leave it alone unless you have a genuinely good reason to believe you're wrong.

Because that tiny bubble you're casually filling in isn't just a circle on paper anymore.

After you hand in that sheet, it becomes data.

And the machine will never know what you meant.

It will only know what you left behind.

The App you Download Won't be the App you Use

Sanni Shazily — Mon, 31 Aug 2026 16:27:23 +0000

The future of software may be a world where there is no single version of an application.

The same app could be downloaded by a million people, yet each person could experience a fundamentally different product.

Today, we think of personalization as changing settings. Dark mode. Notifications. Language. Layout. A few preferences.

That may eventually look primitive.

The way we personalize software today could be to future software what linear regression is to modern AI: an important foundation, but a tiny fraction of what becomes possible when the system can understand intent and dynamically construct an experience around it.

The next generation of software may not ask users to adapt themselves to the way an application was designed.

It may allow the application to adapt itself to the way the user thinks.

The underlying application would still exist. Its data, infrastructure, capabilities and core purpose would remain the same. What changes is the experience layer.

A student could tell a learning platform, “Give me 15 questions at a time, let me study them in three passes, then test my recall before moving to the next set.” A business owner could tell the same platform to reorganize itself around the way they manage customers. Another user could create an entirely different workflow from the same underlying product.

The data remains the same.

The capabilities remain the same.

But the experience becomes personal.

AI could make this possible through a combination of natural-language interfaces, adaptive UI generation, personal memory and intelligent orchestration. Drag-and-drop systems could make it accessible visually. Conversational interfaces could make it accessible through plain language.

The developer would increasingly define the possibilities of the software, while the user defines the experience.

That creates a different relationship between humans and software.

Today, we ask:

“What can this application do?”

The future may ask:

“What do you want this application to become?”

And perhaps the ultimate constraint on software won’t be the interface the developer designed.

It will be the limit of what the user can imagine.

DEV Community: Sanni Shazily

You Might Fail the Exam You Studied So Hard For Because of a Pencil

The App you Download Won't be the App you Use