Cory jumped on and had a few questions to go along with her projects and coordination stuff. We talked about a new table to store bowling pro shop drilling specs for bowling balls, figuring out where the adilas label builder project is at with Calvin, and some other small details. Going back to the adilas label builder app that Calvin made. It is currently a Windows application and we don't have any of the code. We would love to keep pushing it forward and make it into a full service web app (able to use by any of our clients). Currently, if anything needs to be tweaked and/or updated, we have to get with Calvin to get those changes made. Sometimes that is hard to find the time in his busy schedule. Because of that, we are feeling somewhat limited as to what we can do with that piece of the puzzle. We really want to get that code over on our side so that we could make changes and upgrades easier. We currently don't have a Windows developer on staff, other than Calvin, but we may need to look into different arrangements.

As part of this discussion, I think that it is important to note that many developers know that there may be maintenance on things that they build. What they don't count on, and we don't want to count on this either, is years and years worth of maintenance and upgrades. It drags out the projects. Also, it is no fun if someone else introduces something new and it breaks an older process what was working. Basically, sometimes, a new error may be introduced that affects older code making it appear that the older code was in correct. That may not be the fact, but the reality is, it breaks something going forward and there is a constant need to keep updating and doing maintenance on almost all code that gets written. Kinda like a shelf life for code. That is good to keep in mind.

Another thing that makes some of this code work hard is the number of ways things are used. That comes back to settings, configuration, and use cases. Sadly, yet kinda fun in some ways, we have users that use our products in ways we never would have imagined. That's tough to code to all of those use case scenarios. It sure keeps things interesting (good and bad).