Major changes to the way that we do custom validation on inbound URL and FORM scope parameters. Both Wayne and John were showing me some major changes that they are working on. We used to have a thing called a custom tag. This was a crossover between a special page include and a custom function. It had one basic routine to help with all kinds of error handling and user input validation routines. We use basic error handling and validation on almost all numbers, dates, and strings.

Wayne was showing me that he was able to change literally thousands of pages by running special scripts and super deep find and replace scripts. It would have taken me weeks and weeks to do what he can do in a matter of minutes. He can bulk change things, check it, run tests, roll it back if needed, and then do it again. He can keep doing it until he gets it right. Major change in the number of pages that are affected at once. Our old custom tag validation is done (used inside of adilas code) in over eleven thousand places. Wayne can alter all eleven thousand pieces in about a minute. Crazy. I was pretty impressed.

They would like to do the same thing for other sections of code where we show error and success messages. Basically, a global change from somewhat old school if statements, include files, and abort commands into an error handling service that is more global. Some cool stuff is coming.

The two of them were showing me some advanced tools and how to use Linux shells and other advanced tools and commands. We talked about some cool things that we can do with Git (code repository and version control software). We went over some advanced Git commands. Wayne and John were talking about putting in some code snippets and handy scripts into the adilas docs and adilas server docs. These are backend style guides and notes on servers, code, layout, logic, requirements, and best practices. They are really wanting to push those pieces forward.

We got into a show and tell session dealing with slow pages and slow queries. They are monitoring those things and wanting to get in there to fix those slower pieces. We are gaining lots of good tracking and optimization tools, report, and new techniques for finding slower pieces and sections of code. That is really exciting as well, which means once we have a target (slow page or slow query), we can then try to go in and fix things, specifically. That will be awesome.

As part of their show and tell session, we got into optimizing database queries and doing custom indexing, based on needs and usage of the database tables. Light training on combined or combo level indexes, inside of the database engines. We talked about performance concepts and possible tweaks that we could make. As we keep learning these things, we are also wanting to get some internal training going on for our guys. We are hoping that some of the new and upcoming training will happen sooner than later.

Just for fun, Brandon and I were talking about when we bid on the state of Colorado Medical Cannabis program. See attached for the introduction document that was included in our bid.