Reply to post: Good practice

Y2K quick-fix crick? 1920s come roaring back after mystery blip at UK's vehicle licensing agency

Anonymous Coward
Anonymous Coward

Good practice

Surely it's good coding practice to allow for events that are beyond the expected lifetime of the software? In the '70s I was setting up a system for quality control logging and stats on a departmental mini in a large multinational tractor company (Skunkworks, to be frank - the mainframe boys were unaware and would have stopped us) where there was no specific date format. So I wrote one in that was Y2k compliant and also recognised 2100 as a non-leap year. No I didn't think it would still be in use then. But good coding practice is a good habit to get into. And the hardware and software was in daily use for another 12 years - does that ever happen now?

Anon to dodge the agency headhunters - I'm trying to retire from all this...

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon


Biting the hand that feeds IT © 1998–2020