Every so often I stumble across a cache of outdated notes that offer a peek into the problems my mind worked on at some point. These notes are dated, colour coded, and replete with check marks in tiny boxes denoting accomplishments. Items without check marks are either crossed out with a reason written to the side or copied to a new page where they are then completed. What I find interesting about these notes is the opportunity to re-examine the decisions made or work performed with a little bit of hindsight to see what worked and what needed refinement later.
Today’s notes were from May of this year when I was working on performance optimizations for 10Cv5. There were sketches outlining how the database would need to be altered and how triggers would be used to simplify the writing activities from the API. The structures that allow the system to be as performant as they are today were all written there on paper and only one had seen any sort of tweak after deployment. All in all, the concept was solid. I wish all of my development work could be as successful.
Generally my day-to-day notes are destroyed at the end of each week to ensure that any sensitive data from the day job or clients is not lying about. However, sometimes a handful of pages are found buried in a bookshelf or in a shoulder bag I had used at the office. Having this opportunity to reflect on what worked and what didn’t allows me to see where my skills may have improved over time and where I make repeated mistakes. I should probably stop destroying 10C-related notes just so that I have a reference point to look at in the future when writing some documentation about my systems.