In my quest for expanding my culinary horizons, I have come to the realization that all my recipes exist in the form of a stack of folded papers, index cards, and miscellaneous clippings from various food packages and that all of these recipes are in no sort of order. They are not even in order by when I first made them since I shuffle them around when searching for a certain recipe which I plan to use.
While there exist solutions to this problem in the form of binders or little index card boxes, I either need to memorize recipes or have the physical medium present in order to view the recipe. Therefore, I am taking it upon myself to create website which will have the sole purpose (originally) of storing recipes.
You are probably thinking, why go to all that trouble? Well, for one, it would be a fun project for me to do in order to learn a new technology, as well as something that would have a practical purpose after its completion. As well as learning about the software life cycle from planning to deployment and maintenance. I also want to use this project as an opportunity for learning about different software management methodologies, the pros and cons of each, and the implications each style would have on a software product.
My hope is to have the site hosted for others to use as well and eventually add features, such as sending recipes between users. Because I will be planning the project on a per feature basis, I don't have a solid deployment date. My estimate is by mid-December I will have the first version ready to deploy.
Anyway, I don't expect everyone to understand the previous two paragraphs since some of it is industry jargon. However, if this is something that you would use, stay tuned for updates about the progress of this project.
