While working in my most recent job, I was in charge of a backroom for a large retail company, and quickly realized that I could solve many issues with just a few simple programs. While I know in the spectrum of business, software or hardware changes are anything but simple, though the idea itself was relatively easy. I quickly realized that while during our inventory process that we would do most mornings, that while there was a system for the corporation to keep track of where and what was being shipped, we as the store did not have much of a hint as to what we were getting or for that matter how much of certain products we had at all. Being an intermediate programmer, I generally think in terms of programs and how I could make things better and easier, not only for myself but for everyone else on my team. The first thing for me is to get a view of the big picture of things, falling in line with the first step of the programming development cycle, Analyze. This gives me a chance to make sure that the ideas that I am coming up with are not just one of those far fetched, well if we had a stick, a match and a kangaroo type of ideas, but actually legitimate ideas that could improve our work flow. It gives me a good idea of what information you would need on both ends, being your inputs and outputs. The next step is designing my personal favorite. This is where you are fixing the problem with an algorithm, or a logical sequence of steps to solve a particular problem. I am very much a problem solver, and I truly enjoy the design phase of the PDC. It allows me the opportunity to truly think outside of the box and figure out how it is that we can get from point A to point B in the least amount of steps possible, but also while including the most amount of information as possible. Next is choosing the interface, or basically figuring out how you are going to acquire the