This week, I will be writing a reflection on the “Reading List” pattern. This pattern addresses developers who are proficient in their first language but feel that the amount of knowledge to be learned about the language is growing at a faster rate than they can acquire it. I chose this pattern because I have been visiting book stores to shop for software development literature. While I feel proficient in a language, I have yet to encounter this worry of an expanding knowledge-base that I’ll never fully acquire. I do, however, plan to begin putting a reading list together as I continue preparing for my internship in the summer. Regardless, Oshineye and Hoover provide sound advice on how to manage the books you plan to read and how to reflect on your past reading habits.
Their first piece of advice, ofcourse, it to create a list of the books you plan to read. This is useful in that it allows you to plan out a kind of strategy that will allow you to learn incrementally and notice patterns, trends, and gaps. As a side note, they also suggest that you make your reading list public to open the possibility of receiving suggestions for future reading while also allowing others to follow the same plan you did. They recommend that you treat your reading list as a priority queue, as it will help you realize that some of the books on your list might actually not be worth reading. To initially create your list, choose books that will broadly cover the area that you are studying, and then subsequently drill down on individual topics as you filter out the ones you find most important or interesting. I found these tips helpful and will likely use them when I head to the bookstore soon.
They conclude the pattern by describing the kind of action you can take to begin implementing this pattern in your own life. They recommend listing the books you are currently reading in a text file, and then progressively update the list as time goes on. As long as you maintain the text file, you will be implementing the pattern. I began my list today, with Clean Code and Apprenticeship Patterns being first and second in the queue.