When it comes to smaller applications of this nature, I generally worry more about anti-patterns than I do about design patterns. That said, it’s really two sides to the same coin: the power of a design pattern for me is being familiar with them so as to recognize the less-than-obvious pros and cons of whatever solution I’m thinking of. I rarely if ever go out of my way to actually fully implement a complete design pattern (unless I actually need all the functionality); however, I have often saved myself a lot of future re-work by recognizing the path I’m on and looking at the common pitfalls or drawbacks to that solution, which I can then check against my future uses to see if it’s going to be a relevant concern for me or not. Thus, the power of a design pattern is that you can easily predict the future consequences of your current solution against your potential needs, without worrying that you might be missing some less-than-obvious caveat or special case that you haven’t considered.