After working through this course I did implement some changes to my existing CRUD application at the grocery store. I was able to write some cleaner and much shorter functions and subroutines, as well as break apart certain functionalities for reuse across several of my existing functions and subroutines. This was nice because, of course, when you need to make a change you have only one place to make the change. I came to learn that this is what maintaining legacy code would be like, and how much of an undertaking it can be to actually refactor it while preserving functionality.

There was only so much I could do in order to implement many changes, because the whole project was still largely by my own initiative. I wasn't still at the grocery to refactor that project so much as I was to support my replacement buyer in the day-to-day of running the department as well as the use of the application. While I would often spend time on that project at home, or here and there at work, I ultimately had to leave it in working order. Also, the scale was small enough that more performance upgrades were approaching diminishing returns; I had already gotten it to run subroutines inside of 15 seconds, that had originally taken close to two minutes.