Work session with Shannon. She really helps me carve out time to work on some of my long term goals. If it weren't for her, I would get sucked into the main mix and other demands inside of adilas. I love it that we get to work on these things (other projects and dreams). As far as work today, we spent most of our time working on new content for the fracture buildout section of the adilas lite plan. Today we were finishing up the stuff on front-end and backend validation processes. Here is what we came up with:

//////

This validation section deals with security of the data being passed around, and/or transferred, from client to server and back again. The term client-side validation deals with checks and balances before the webpage or form is submitted. This front end, or client-side, validation can really help with the user interface and user experience (UI/UX) parts of the system. This type of validation can help catch simple mistakes, typos, or missing information before the data is sent to the server. This helps speed up the process and reduces server load. If the data doesn't pass the client-side validation checks, then the user is prompted to correct the errors before submission. This is a great way to enhance the user experience and reduce unnecessary server requests.

Server-side, or backend validation, deals with what goes on once the webpage or form leaves the user's computer and hits the server. The server is the backend brains of the application. Backend validation is responsible for checking and making sure that anything submitted is viable and can be used in the requested action. This backend validation is very secure, it can exist in multiple levels, and may even be stacked if needed. If backend validation is used, and the data doesn't pass the validation checks, then the server throws an error. Depending on how deep it is, the errors will stop the process and the desired action is not completed. One or more error messages then get passed back to the client. Error messages are required for communication with the users. However, they may lightly detract from the user experience.

The best combination is a good mix of both client-side (front end) and server-side (backend) validation. We, as a company, are already doing a lot of this mixed validation. We are currently heavier on the server-side, but both options are being used. Moving forward in the fracture buildout, we will continue to keep the server-side tight. We also plan to enhance the client-side validation to make the whole experience even smoother for our users and clients.