On the morning meeting with the guys. We started out with Wayne asking questions about payee/users and how they can and do criss-cross and how they can cross between corps. We talked about options and why we did what we did. We got in to migrating parts, items, and PO line items. We then has some conversation about splitting up databases, indexing, and other processes that could either optimize the data processing and data retrieval process.

Calvin and Alan popped in, they were working on labels on the content server. Alan helped Calvin wrap some of his code in a try and a catch. It was awesome and he was able to push the cfcatch variable. That allowed us to figure out what we needed to do to fix it. Super cool.

Steve and Alan - "We break things and then we fix them." Fun little saying.

Alan would like to rework the forgot password project. He wants to rework the security and how that process would work. He would like to beef things up a bit and make it more bomb proof.

Alan would also like to work with Wayne on breaking code into smaller blocks and working in a more MVC (model view controller) type model. Basically, making baby steps and making things into a more object oriented code base. Alan was talking about encapsulating and modularizing functions, data, and components. Lots of code reuse and minimal duplication. Question - Build new or build on what you have? We are leaning towards refactoring existing code vs re-writing new code. Adilas' goal is build as if for years.

We were talking about sub inventory and taking that whole new level and pushing it out into an object oriented model. We also talked about implementing Wayne's testing framework along the way with the new changes. The goal is trying to limit the number of times we are re-writing the same thing. We want to reuse code as much as possible. We talked about strengthening our foundation so that it could handle more weight and also allow for flexibility and fracturing, which will still occur, no mater what we do.

Light talks about black box code and who pays to keep it updated. There seems to be two different levels. There are critical updates and non critical (optional) updates. We need to figure out a standard procedure to deal with custom code and black box code. Sometimes, if we have a problem and we are forced to think about it, we can usually come up with a pretty good solution. If we wait too long, we are forced into emergency surgery and sometimes that is not the best approach. We want to be pro-active on our approach and on our development.

Steve and I were talking about some hanging projects... One is the invoice due dates and watching for outstanding receivables (David and Shari O. really need this). This was a Russell project that only got half baked. We need to finish it up. The goal there is for us internally, to be able to see what companies owe what and what the dating is. Then once it gets to a certain level, we could prompt for payment and/or be able to shut things off.

We also talked about how it takes a whole village to raise the upcoming generation. We are really trying to build the adilas community and adilas family. We have many talented persons who are playing the game along with us.