We started out the server meeting and Cory wanted to check on the data 34 server. It was reported that it was running slow. Wayne logged in and looked around. They ordered some more RAM for the database server. Pretty cool to see how quickly they can jump on things.

Next, we started talking about a client and their balance sheet. I mentioned to Cory that we have on our wish list a report that would show known issues (bad dates, things done out of order, or other possible problems that we could detect and/or figure out). That would be so cool. As a side note, the page already exists, it just hasn't been built out yet. Definitely on our wish list for fracture. This could help all of us out and make things more transparent and visible.

Both Wayne and John are working on documenting things on the server level. It's far from done, but they showed up a 3 page document (just the start) of the outline or outline of the server layered architecture design document. Pretty cool. Starting to see that being worked on. I'm excited to see what they come up with.

The next major conversation was dealing with adilas phones, phone trees, and other forms of digital communication. We had some open discussion about do we want to keep it, who is going to support it, who is going to maintain it, and so forth. This piece is kinda flapping in the wind. We also talked about, if we want to, allocating both time and money and getting that code and/or process fully inhouse. Right now, it is a virtual 3rd party entity, even though we technically own it. The prior owner/developer is the only one who really knows what is going on inside there. We talked about different technologies that we could and would use if we brought it fully under our control or under our roof.

The reason that the adilas phones stuff got brought up was because of this document that they are building out for the system architecture and layered plans. Hopefully, we'll uncover other issues and/or dependencies that we need to look at and evaluate (spend/don't spend, maintain/don't maintain, market, pitch, let it die, etc.). We kept getting off on tangents. Cory did a great job keeping the discussion going in a good direction. Once setup, we will provide an open VPN (virtual private network) for our developers to be able to remote into the testing box to push code and make changes.

After that, we got into talking about the testing server and what our plans are for that. We have a client's data that we want to move off of a production server and put in the Amazon cold storage or Amazon Glacier. As we were talking about the testing server, Shari O. was sending questions and comments through the chat feature on the GoToMeeting account. We are making progress there and making headway.

We got into talking about insurance, coverage, errors and omissions, and general cyber security, and data breaches. We have a 3rd party integration that is pushing on us and wanting all kinds of certifications and proof of insurance coverage. Everybody but John and I had to leave to jump on other meetings or calls.

After that, John and I spent some time doing a code review on his recipe/build rework stuff. We talked about a new possible user-level setting for using the time-pickers vs an open entry time field. John likes the time-pickers. I had to take them out the other day due to a few clients complaining. That sounds like a perfect option for a user-level setting. We also went over new options for showing progress bars and helping the users know which step they are on and what is still needed to complete a certain task and/or process.

As a final comment for the meeting, John said - "The ROI (return on investment) for the testing server will be internal peace of mind." I liked that.