When I sit down to write a blog about Development, I try to think of something that isn’t going to make people cringe.  Let’s face it, the idea of reading a few paragraphs describing Agile Theory and Program Code workflows isn’t something that have most people on the edge of their seats. However, what I have found is that the process in which we decide on what gets put into these workflows is a better use of your reading time. 

I have been writing code since I was in middle school and I will not date myself by saying what I was writing code on. Well alright, it was a Commodore 64. I know, sounds ancient right? Point is, writing code is the easy part. If I know exactly what I want I can sit down and make it happen with some good ol’ fashioned hard work and a lot of energy drinks. But what if you don’t know exactly what the program should do, or you don’t know if there is a better way? 

The hardest part of development is understanding the needs of the industry and making sure you write a program that meets those needs in the best possible way. Again, it is simple to do things one way with tunnel vision because you believe that is how everyone will want it. But you would be wrong. I have been with Data Age for nearly 20 years and we have always tried to develop a program that can work many different ways to meet the needs of many different businesses. That is the hard part!  We never assume to know what is best for our clients unless we ask, over and over again. The input from over 5,000 pawn shops has been a vital part of how we move forward and develop our software and we will continue to reach out to make the best decisions that work for this ever changing landscape. So don’t be surprised if you get a call or e-mail from me asking what you think about our latest ideas. I love to hear what you have to say. See, that wasn’t too nerdy.