Though on surface, changes on the requirements introduced midway in the project seems not to pose any significant impact but its unexpected domino effect has greatly increased the complexity of my tasks. It was only recently agreed by the university HR and me that some work schedules like overnight security duties may require time outs that are a day after its time in. My initial version of the DTR program assumed that all time ins and outs occur on the same day, and it looks like that all I need to do is just add a time out date to the database so as to comply with the new requirement.
Unfortunately, when I added a date component to the time outs database entries, I realized in the last minute that dates were also needed to be appended on other time-based entries of the database. When multiple fields of the database are revised, so are revisions to the interface design, time log processes, and attendance reports will also be required. This inserts complexity to my already complex programming tasks, which results to the gradual sliding off course of my actual activities away from my planned blueprint.
Me programming the DTR units
But still, I have my obligations to the project, and also to my immersion study as well. There is no time to feel bad about my situation but to continue the progress of my program. I also have to keep in mind that my internship also needs lots of documentation work.
So no time to walk... run!
