While I was working as a Student Utilities Assistant, I had a weekly responsibility of keeping a database up-to-date with all the hundreds of monthly energy bills a campus gets. We had documents containing instructions for all of the places and times of the month to check, and the database itself was quite helpful with keeping track of the data it already had. However, because I started working there when the workers who built the database were all gone, I eventually noticed that over 500 bills from years in the past had never been added to the database.
During my last few months working there, in between training my successor, I constructed my own strategy for finding all the missing files whose data were still accessible. The database had a section that pointed out which had bills missing information, so I created placeholder data points to mark the missing information first. Through this, I had a company, account, and date-based catalog of what bills in the past were missing, and used that to search every company account I needed to. Also, along the way, I discovered over 650 bills had an incorrect or missing start date (because of either a missing bill, or because they were a first bill in a monthly routine), and using the same placeholder strategy, I fixed those too just in time.
All in all, I consider being an engineer about having insight, communal and individual, about functional designs. I built up communal insight on how to keep the energy database up-to-date first. From there, I had the individual insight needed to fix mistakes that the creators of the database had not figured out.
------------------------------
Alexander Granato A.M.ASCE
Student
Bexley OH
granato.3@...------------------------------