Philippine Voting Extended At Least An Hour: E-Voting Problems Cited

Electronic Voting Problems May Not Be As Great As Predicted, However

1 min read
Philippine Voting Extended At Least An Hour: E-Voting Problems Cited

Last week, I blogged about the 76,000 electronic balloting machines scheduled to be used in the Philippines' general elections today as having "technical issues" which required all of their memory cards to be replaced at the last moment.

There were fears expressed at the time that this wasn't going to be possible, especially in rural areas of the Philippines, and this would lead to election problems today. In fact, there was a news report on New Tang Dynasty Television over the weekend that 5% of the electronic balloting devices were not tested prior to the election in rural or violence-prone areas. This represents some 3 million potential votes, the report said.

Well, it looks like those predictions were at least partially correct, as the Philippine Starreports that the Commission on Elections (Comelec) has had to extend voting by (at least) one hour because of problems with the electronic voting systems, among other issues.

The news agency Reuters is saying that widespread technical failures of the e-voting machines has not been reported, although in some polling districts voters had to vote by paper ballot because of machine malfunctions. It will likely take a couple of days to find out how many e-voting machines were taken off-line.

In a related story, given the chaos in the UK general elections last week, there are renewed calls there to use e-voting machines in the next general elections. Given the likelihood of another general election being called within a year because of the hung parliament, that would appear to be unlikely.

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
A plate of spaghetti made from code
Shira Inbar

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