The December 2022 issue of IEEE Spectrum is here!

Close bar

Australia's Myki Woes Continue

New Transport Minister Will Have His Hands Full

1 min read
Australia's Myki Woes Continue

The on-going problems with the Myki smartcard ticketing system claimed its first politician, Public Transport Secretary Lynne Kosky. She resigned on the 17th of January, saying that she needed to spend more time with her family and that the Myki problems had nothing to do with it.

Ahem, sure, I believe that.

The new Public Transport Minister Martin Pakula will have his hands full trying to turn things around.

For instance, recent press reports say that one in ten Myki users are likely being charged higher fares than they should. In addition, one in ten Melbourne train stations do not have facilities to top off the smartcards, including many of the busiest stations.  Others Myki customers are finding that even if they have the facilities, after trying to add credit to their Myki cards, it doesn't show up on their card's account.

Still others customers are using the Myki cards to take tram journeys, which they are not supposed to do. The reason that passengers are being told not to use their Myki card on trams is that the level of accuracy is not up to the minimum 95% accuracy rate.

However, as David Heath at ITWirepointed out, a 95% reliability rate means that about once every two weeks an average train commuter will have a problem with their Myki card. 

Given there are 350,000 train journeys per day made by Melbourne commuters, if a majority use Myki smartcards that have even a 2% error rate, things could get ugly.

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