Welland Ontario Voter Notification Cards Fouled Up

Some 23,000 out of 24,072 discovered to be incorrect

1 min read
Welland Ontario Voter Notification Cards Fouled Up

There was a story published in the Ontario, Canada Welland Tribune that just begs for more information to be provided.

Apparently, the City of Welland bought a commercial computer program - unnamed - to help the City Clerk generate 24,072 voter notification cards containing a voter's name, home address, ward, poll number and voting location. Unfortunately, 23,000 of the cards were later found out to contain mistakes.

The City Clerk says that 600 notification cards were initially printed and verified. After that verification process, the remaining 23,472 notification cards were printed and sent out. Soon afterwards, it became apparent that nearly all of those had wrong wards or poll numbers on them, but correct voting location.

The City Clerk was quoted as saying that there was nothing wrong with the voter database or its information.

The City Clerk decided to reprint all 24,072 notification cards, this time on colored paper instead of white paper that was used originally. The white notification cards should be thrown away.

This time, the City Clerk and her staff did a random check of hundreds of notification cards and found them to be correct.

The City Clerk's office could not say how much it was going to cost to do the job twice.

Nor, apparently, did it provide any sort of detailed explanation of what happened and why.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}