Meeting notes. Steve, Brandon, Wayne, and Dustin were on the meeting. Wayne was showing Steve and I about some cool image manipulation options. The site and tools are called Thumbor - image manipulation. It was capable of pushing up an image and then running all kinds of cool tweaks to the image, on the fly. Things like cropping, scaling, specific file sizes, grayscale, colorizing filters, etc. Pretty cool. Our goal there was to talk about ways of using existing tools to eliminate how much processing we make our ColdFusion servers do. Currently, we do all of our own image manipulation and storage on a per server basis. Just some ideas and concepts at this time in the game.

After Wayne and Dustin left, Steve and I had a good discussion about where are things at and where are we headed. Both positive and potential dangerous and/or scary. Open conversation, no specific takeaways. Here are some of our notes:

- Defining strengths and weaknesses and then working on both

- Talking about the new AWS stuff - pros and cons

- The skill level difference between an adilas user who is a developer and a normal or non adilas user computer developer - there is a difference. A lot of our stuff has a culture and all kinds of cause and effect relationships attached to single decisions, setting changes, and/or wants and needs. Interesting.

- Your eductaion and expierence help you on your approach and/or your angle of attack

- Revenue is not what you get to spend

- We have a bunch of things that are partially done - finishers wanted

- We talked about the scary pieces... These are mostly the unknowns... this could be on complexity of the AWS side of things and/or the unknowns on normal operational costs (speaking of AWS stuff).

- Steve and I spent quite a bit of time on - Let's make a plan - this is huge. We really need to see what and where we are doing and going. We know that the plan changes from time to time, but we need something to help us direct this thing as we move forward.

- Scratch built vs pre-fab or mash-up options. We have been pretty spoiled and have built our own scratch built pieces for years... we can't keep up with demands if we keep that same mentality. We are being somewhat forced to start using pre-fabricated pieces, outside code libraries, and outside products to create a mash-up of sorts. As a side note, even through we like scratch built features and options, one of the adilas goals is to become an API socket option (aka a mash-up option) for other companies. We want to build out the tools and then let others (individuals, companies, and even outside 3rd parties) consume the adilas API sockets as needed.

- One of our concerns is, we spend hours and hours of our time on meetings and talking about possibilities. Technically, this is just R&D (research and development/design) stuff but it takes us away from other tasks (opportunity costs). We love it and we still need it. It comes down to a balance and a plan.

- Talking about business and the different balances needed to keep things going and in check. Steve and I talked about an emerging 3-way balance between clients, systems, and education. Each of those main topics branch into sub topics. For example: Clients may branch into sales, funding, shear numbers (how many clients), and market demands. The system side of things seems to branch into user interface, functionality, features, settings, permissions, development, and tech. The education side seems to open into documentation, ease of use, instructions, guard rails (don't let people fall off), just in time learning, and the need for good reps and consultants and other trained individuals. Very interesting. Shannon and I had a similar conversation the other day. See this link for more information: https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4506