24 Hour Clocks
We had a production issue today whereby the client was complaining that we needed to change the schedule of a component. The component reads from a DB once an hour, at 15 minutes before the hour, and uploads the data into SAP. That data then triggers a job in SAP. The problem was, the job was taking more than 15 minutes to finish, and that caused it to fail, because it 'got confused' by the clock moving into the next day, when the 23.45 schedule ran...
Why do I have to work with people who write jobs like that? Surely, that is the type of issue that 16 year olds who are programming for their GCSE's face?











