Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Meeting with Steve to go over ecommerce stuff. Trying to debug some code on sub inventory attributes. Got stuck on some checkboxes that wouldn't work or were having issues. Trying lots of stuff. Multiple attempts. We'll have to come back to that.

Phone call with Dave Forbis. He was asking a number of questions. Lots of questions about social media connections and API's, on demand print stuff, and banks that we have integrated with (for pulling back deposits and expenses to help with bank reconciliation stuff). We also talked about old projects for campaign tracking and GPS tracking. He was looking around and trying to get things lined up. Good call.

Emails and reviewing tons of PDF files from Hamid, for the business functions, on the presentation gallery.

Original meeting was going to be at 1 pm. Both of us were late. I totally forgot about it until I checked my email. We ended up meeting at 2 pm. Spent some time meeting with Dave from Headset to try to debug some of the API sockets for a mutual client. Live debugging with Dave. Then he jumped off and I kept going. Finally got it figured out. It ended up being the URL address that was slightly off.

Meeting with Dave and Paul from visionmax.com

- Dave - they do a lot of kiosk work, mobile, web, etc. Some kind of a protected environment (usually full screen) and interfacing with some sort of kiosk or hardware unit.

- We need a bridge and/or proxy type environment - it is tough to go from web directly to hardware - we need a bridge or proxy type level

- Local installed code that allows for hardware interactions

- Browsers are clamping down on access to outside pieces and parties.

- They are seeing more and more need to play along SSL's on both web, local proxy, and middle ware interfaces. Certificates are needed on all side. They need to match.

- These guys have already done the integration with the PayPod unit. That is half of the way to the full goal.

- Dealing with money, there is tons of validation, who does what, and protecting from possible hacks.

- They, are out a couple of months (timelines). They took a good 3-4 months to build out the original pieces (middle ware) and then maintenance and other iterations based on that. They have been at this for about 10 years.

- There is an IP (intellectual property) aspect to this relationship.

- Http payload as XML or JSON - back and forth transactions. This could be for web, mobile, or hybrid type interfaces.

- Offer is open, they can point us in a good direction and we could do the development, or we could figure out a license type agreement and use their products and libraries.

Emails and reviewing the summaries document. Sent the new internal questionnaire summaries to a few people. Trying to get the word out. Phone call with Dave - new client from 2:30 to 3 pm. I took some notes and will be passing on some info to Sean to help schedule a demo and do some follow-up. Somewhat of a sales call. Good meeting!

Talking and working with Shari O. over the phone and on a GoToMeeting session. We were dealing with email accounts and email users.

From Shari O. - "We are like family and we take care of each other" - meaning the adilas family.

Helping Bryan with some questions. I also swapped out the older meet some of the team graphic on the contact us page with a newer graphic that didn't have Dave Forbis and Bryan Dayton's numbers. More generic.

Made a call out to Dave Forbis, project manager. Spent some time updating some black box code for Scott Jolley dealing with invoices and tax breakdowns and showing customer loyalty points.

Nobody was on the morning meeting today, so I spent some time going over some older notes and goals. Super fun and I could get lost out in that realm for quite some time. Here were a few of the places that I spent some time today.

I re-read and lightly edited notes from Steve and I's brainstorming and business plan meeting last night - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4574

Research from the developer's notebook on core concepts - https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=core%20concepts - I then did a local web browser search for the words "core concepts" and read the entries accordingly. Spent quite a bit of time here.

I would love to re-pick-up on this brainstorming doc - clear back from 2014 (part of an adilas training class with Shannon, Cheryl, Dave Forbis, and my self) - tons of cool ideas and concepts. https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=3681

Other core concepts that we have learned over the years - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=1190

This may sound old... but there was a ton of work done on fleshing out the adilas core concepts in 2013. If you want, you could go to the developer's notebook and do a search for core concepts and filter the date range to 1/1/13 to 12/31/13 and get some great ideas. I ran out of time, I would have loved to have done more.

Getting started and getting all caught up. Steve had some files that needed to be merged in. Wayne popped in and helped to answer some more questions on the transition to AWS. See attached for the latest notes. We are calling that transition document done, at least for now.

Working on merging in code for Steve. Also got a call from Calvin Chipman and we chatted about some things. Lots of moving pieces. Steve and I got back to the code merging and while we were working, we were chatting about some of the great people that we have and get to work with. That is awesome. We would love to do another training event, here soon. Even if it ends up just training our own team, it is worth it.

Dave Forbis called in and I chatted with him for bit. He is on the outside edge, but he could be a great asset when the time comes. He has a number of customer relationship and project management skills that could really play into the mix, if the conditions were right. Great potential.

Working on customer tax category settings out in ecommerce land.

Jumped on with Dave and we went over some progress and details about the assisted living stuff. Dave is gathering information and creating flow charts, ideas, and mapping things out. He showed me some of his new charts and graphics. See element of time # 4147 in the shop for notes from our meeting. We are trying to gather all of the pieces that are relative to that project on that element of time. Here is a link:

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4147

Meeting with Dave Forbis and going over his assisted living flow chart stuff. He has posted 3 different flow charts to date. We spent a good hour and I took a number of notes on what he is thinking and where things are going. Dave has been working on ideas, concepts, how data will flow in/out and interact between the facilities and adilas. Great stuff. See the element of time # 4147 here in the shop.

Shannon jumped on just before 3 pm. She listened in as Dave and I were talking and chatting. Once we were done, we talked about getting some of the adilas developers up and on the adilas market or in the adilas world (marketplace stuff). That is great place to start. There is already a huge demand for that service.

Around 4 to 4:15 pm - Janna popped in and we covered some WordPress stuff and some small tasks that she is going to do. She is a technical writer and will be helping us with content and making sure things are good to go there. This was the first time that she virtually met both Shannon and I. We told her that eventually, we would have her helping Shannon and I on the adilas user guide.

The last part of the session was actually going through and working on the adilas user guide. We did a small session and were recording some notes to help us document each of the players and what they do and/or may do. Nice little work session. Shannon and I rescheduled for next week to continue chipping away at our internal projects. Good stuff.

- Tons of emails and light tech support from things over the Thanksgiving weekend.

- Brandon and Steve talking about updates on people - we were talking about Shannon, Russell, and Dave Forbis.

- Alan popped in and had some questions about his new projects. He is working on discounts on my cart favorite buttons.

- We lightly talked about vertical (business verticals or industry-specific) templates and settings. Make it easy to cater to specific verticals.

- Talking about system stats and storing that info in a daily watcher or feeder type table. We also talked about queued back end services that run on daily routines. We also talked about pulling reports and monitoring growth and changes.

- We were also talking about "rules" or standards per vertical (industry). Each industry is different, and thus may need some general rules based on the type of industry that they are. Basing the pricing off of processing and storage vs charging for the code. Some users may or may not be using certain features and/or modules. This discussion ended up going into questions about what do we want to do with the adilas databases (make it bigger and better or break it up into small faster pieces). This is still an active discussion and we are trying to gather pros and cons of both.

- Alan was talking about vertical and horizontal scaling - add more and more servers (distributed or cluster model) vs single server and up the capacity and resources. This lead into a small discussion on back-ups, redundancy, and disaster recovery options. Currently, we are doing somewhat of a modified horizontal scaling method.

- Steve had some questions about the API socket level and what that load may be and/or take?

- Alan had some ideas on risk mitigation and how to help our clients even do their own risk mitigation processes. Lots of talk about what are the vulnerabilities and how do you treat, track, and deal with those vulnerabilities. It always tends to come back to an analysis of what is the threat and how much do I care, need, want, and/or require? Talks about server up time and reliability. What maters most and what are we willing to pay for and/or spend?

- We would love to show all of the corporations (virtual worlds) what their stats are and what we (as adilas) are carrying and helping them out with. That helps us show a benefit and advantage for those who use adilas.

- We lightly talked about an offline adilas mode and allowing a user to use the main web system, if a problem, they could use a local copy, and then sync up things later on. This sounds awesome, but it could be a huge project and could be riddled with loop holes and gotcha's. Possible, but hard to tell what the real costs are and/or would be.

- The technology wave and what is here, coming, and already gone (outdated). We are constantly riding those waves and making decisions. Alan lives down there in Arizona and could maybe pop in and check things out with the actual server farm. We could even branch out and spread out our exposure to other server farms.

- We could update older servers to help with stability and up time. We could upgrade to using solid state drives, bigger processors, more RAM memory, and updated server and software packages. That could be a great upgrade for the time being. We also talked about optimizing our existing servers by tweaking settings and such (performance tuning).

- We may end up needing some new training on how to configure and upgrade the things that we need. This is just a possibility, but there is an upcoming ColdFusion summit convention coming up in April 9-10, in Washington, DC. Just looking at ideas and options. Our goal is to get the most out of what we can by either upgrading to the newest models and/or versions and getting the proper training needed to make it dance and sing. ColdFusion is allowing more and more scripting languages and is gaining some momentum.

- There was some small talk about upgrading from Windows servers to Linux servers. Wayne is the one that knows a lot there. Lots of possibilities.

- Some new shortcuts and getting up to speed. Alan was showing us some coding shortcuts. Params, is defined, and quick conditional processing. Things like a turnary operator (one line true or false if statement - switch), elvis operator (reference something and it is able to self-define if it doesn't exist but will use a real value if it exists - less breaking code for things that are undefined).

- There are many paths that we could take and would work. Let's make a plan and then work that plan.

- What we do is not easy. There are so many moving parts and pieces. As we build, we keep finding that it comes back down to more and more permissions and settings. Subs of subs. Eventually, it could become simple if you get enough sub pieces built into the mix. Kinda crazy.

- We are also seeing more and more needs for bulk tools and such.

- We are also seeing that people are really looking for a system that could do almost everything with both global tweaks (per business vertical) and also granular control (permissions, settings, etc.). Almost a wish list of sorts.

- As we get out, in the field, we may end up adding some icing here and there. Maybe even some icing per business vertical.

- On black box stuff - what if we had a list of what happens and/or what black box code is running? We may need to use some kind of technology to help us monitor and/or use what black box code that is out there. Maybe a way to notify our developers, consultants, and even our users what code they are using.

- Small concepts - creating an adilas fracture account - future concept once we get a few of the other pieces in place. This was an idea from Steve, clear back in 6/22/17. We would basically, allow the normal or classic adilas to keep going, and then start building out the adilas fracture accounts. Everything would be broken up into tiny modular controls but would also have bulk tools, templates, and industry specific defaults to help play the game. This subject could take up volumes, as far as other ideas and concepts that we would like to include. Super cool idea and future project.

- Steve would like to see us work on breaking out users from the systems... They, the user pools, exist and can interact as needed but they become their own entity - Imagine pools of professional (adilas community members and power users) users that could work for other companies as needed. Separate users and systems, even more than what they currently are. Steve has some good ideas on that. Kinda like a marketplace for features and functions as well as power users, employees, and people talent. Fun ideas.

Steve and I - meet with Dave Forbis to talk about marketing and direction

- Touching base

- Get an invoice from Dave

- Talk about marketing ideas and how to help generate funds - Dave has designed an email flyer... he would like to help test the waters and send it out to some of our adilas users. This is a direct campaign to point people to a specific adilas community funded project.

- Assisted living stuff - we would like to create a play site (corp 478 on data 0 - sunrise estates - assisted living) - Dave comes from that world - what is the dream - what is the most basic level and how can we solve those problems.

- Small game plan to help and work with Dave - see attached for some new docs and planning.

- Dave was a consultant, helping in the assisted living environment. He and his company were called in to help fix the major problems. His goal was to be in front of the curve vs being behind the scenes.

- Currently, there are a number of assisting living software packages but they are all very expensive. We could come in and provide a great product at a monthly rate with no contract.

Dave Forbis called and we talked about some marketing ideas. We setup a meeting for tomorrow to talk with both Steve and I. One of the things that he would like to do is help push some of the community funded projects as an alternate funding source. He created a small flyer that could be emailed around to help generate awareness. We talked about some things and even went in and made some small changes on the actual element of time for the reoccurring invoice automation project. I will attach the mock-up as documentation. It is not done yet, but it is at least a start.

Other notes - Here is the link directly to the reoccurring invoice automation project - https://data0.adilas.biz/top_secret/community_funded_projects.cfm?projects=1355 

- Read over the page and update some of the verbage. Small tweaks. Also, we talked about a quote from Steve, just the other day. It was "Choose your solution and then invest in your solution."

- I thought that it would be good to have the contribute button wired to point to the URL above. Also, it might be good to put the URL (web address) in plain English so that they could copy and paste it into a browser.

- If we are going to be asking people to contribute, we need to show the advantages and benefits of what they would be getting. In Steve's words, if we are asking for $10,000, we need to give them a $30,000 reason.

On the morning meeting with the guys. We had both Wayne and Calvin pop in briefly. Most of the morning session, Dustin and I were working on his code to auto increment these huge RFID tag numbers. Basically, you start with a huge 24 digit and/or character tag and then increment just the tail end. It has tons of zeros, alpha/numeric values, and an incremental portion. We spent a lot of time going over the sub loops and loops within loops. We got it and it seems to be working great.

Around 11 am (ish), Steve was showing us some cartoons about a dog. Anyways, Kat, Danny's wife, was telling Danny (one of our sales guys and label developers) that adilas was kinda like a dog. You tell it to go and do something, and it tries to go and do it. Anyways, Danny took this idea and worked with a guy from his church and came up with some fun cartoon dog images. Really fun. The artist's name is Naters Art from the Salida, CO area. Adilas is the word Salida spelled backwards. Kinda fun. Anyways, Naters came up with some great images of this dog, rolling over, with a bone, searching, and tilting it's head. The developers on the morning meeting were saying that they could see some of these images being used as icons while waiting, searching, success messages, error messages, info messages, etc. Lots of good laughs. See attached for a screen shot.

11 am -  meeting with Gene Spaulding with the SAL Management Group. GoToMeeting

We started out the demo and meeting with letting Gene show us around in his spreadsheets and what was connected to what. Really cool and he has taken things to a huge and super deep level. Steve and Gene were able to briefly talk about how both of them started at the spreadsheet level and then eventually grew out of that and into a database type technology like adilas. Good stuff.

One of the main pages that they had was titled - Census and Roster - who is where and what is what (simplified operational and accounting data). This fed the rest of the reports and pages.

Steve - what would be mission critical for you guys? They answered that it was the census and roster reports (getting data into the system). Simple screen to gather that information and then disperse it as needed.

They do have a 3rd party that does all of the onboarding platform stuff. All the paperwork, contract stuff, legal stuff, etc.

They have looked at some of the big huge platform applications out there... they are kinda looking for something smaller and maybe more custom. We did a demo and I think it went pretty well. I had Dave Forbis and Steve on the call with me. They had a controller and head manager on the call. Good back and forth and we had some fun.

Working on some image concepts that Dave Forbis sent over. See attached for some fun new images of the cart and the horse (horse and cart) and how that analogy relates to operations and accounting.

Phone call with Dave Forbis to go over progress on the concept drawings. We talked about ideas and where we want it to go. We came up with an idea to try to mix older scratch graphics with real graphics to give things a flavor of concepting and/or iterations (cycle of putting things out there and then refining them as we go). We are hoping that by showing both types of graphics, it will allow people to contribute and see that things are in a constant state of development. Basically, like allowing people to come as they are vs having to be in a white shirt and a tie - heck, we'll allow you to come in your PJ's, if you want. Approachable learning model.

Lots of ideas and potential there. See Element of time id # 4147 for some flow charts and ideas

On the morning meeting with the guys. One of the first topics of the day was a client's system stats and how to monitor who is big, small, or somewhere in between? We have a few small reports, but we really need to beef that area up and make it more available and visible. We would love to do some visual stats, like the new invoice homepage that Alan made. The difference would be that instead of just invoice and sales data, it would be corporation (world) or location level stats and data. That would be really cool. We went into one of the servers and checked around. The data 0 box had over 1,000+ unique logins yesterday. The corporation in question had over 55 unique users yesterday make and/or modify an invoice. That same company had over 110 unique users affect an invoice in the month of October. We would like to make those kind of stats available and ready for viewing. It helps with decisions and what not.

As we were talking about shared hosting plans, we had the idea of creating an in-depth news and update with information about shared hosting plans (standard adilas accounts), semi-dedicated plans (limited number per server), and fully or full dedicated plans (private server boxes or cluster). We also made a note that some of that info may go well in our ecommerce pages and section. Basically, let the companies decide if they want to upgrade and what not. Show the features, advantages, and benefits of what we have to offer.

Along with that discussion, we had some talks about how fast things are changing all around us... think of technology in general, software packages, servers, hardware, and even versions of existing products. Everything keeps advancing. It becomes a maintenance balance to keep up with things.

Steve wanted to be fair and look at upgrades and maintenance from both sides. What are the clients wanting and/or expecting (their side)? What are we wanting and/or expecting (from our side)? Where do we meet in the middle and who pays for what? Great questions.

We also talked about the fear of selling and making the sale. Sometimes it is scary to virtually rock the boat. This was mostly on my part, but I was expressing that sometimes my angle and strategy is very open and doesn't commit and/or over commit on certain things. Each person needs to be their own style. Later in the day, I was challenged to write a big email to open the door to a client about getting on their own box. It made me think of a quote from Spencer Johnson's, "Who Moved My Cheese" book about dealing with change. It says - "What would I do if I weren't afraid?" That is a good question to ask. It is even more fun to ask yourself that question and then actually go do it. Difficult but fun.

Historically speaking, we are seeing things such as the data 0 server. It was setup in 2011 or 2012, it is on a 2008 server, it uses older versions of ColdFusion (coding environment) and older versions of the MySQL database. That conversation moved us to talk about older technology like fax numbers and other older hold-overs and such. It is amazing as it comes down to a form of maintenance and upkeep. Lots of the new things are going to faster processors, solid state drives, and up to date versions of both software and hardware.

A quote from Steve - "Lessons in time". It is amazing what we have learned over time and by trial and error. We keep learning as we go.

Towards the end of the session, I helped merge in some new code from Bryan. His code was dealing with show/hide option for 2nd vendor/payee tied to PO's. After merging code and pushing things up, he went in and did some live testing. After that, I helped get Steve's latest code branch merged into the master code repository. His code is currently all in custom pages and mostly dealing with the cannabis vertical. He's got some good things going. On that note, he would love to turn over his code work and swap it out for more sales work. He is really good at that.

I worked on some feedback for Dave Forbis and a new graphic that he sent to me. See attached for a copy of the new graphics.

Eric popped in and we setup some bigger blocks of time to work on his special account tracking projects. As we were talking, Eric was talking about project management and the "risk factor" within project management and risk management. He is excited that our current project will help other pieces and clients, but it not dependent upon other pieces in the system. Our goal is to get that section finished and launched by end of the year. That would be awesome.

This is an observation, but there is a growing need to keep breaking things into smaller and smaller pieces. Eric had questions, just today, about how to show/hide fields, change names and aliases, etc. We have a mini project that was done and created for the customers add/edit page, but it doesn't go any further than that. We really need to break each section into smaller pieces and have group settings, page settings, and personal settings. That seems to be a growing need. Along with that, we also see a future need to sub divide the permissions into virtual functions within the functions themselves. It is crazy to see how deep those fractures are and will be heading in the future. Crazy customizable levels.

On a GoToMeeting session with Dave Forbis. We spent the first little while and talked about ideas for the billboard sites. See element of time # 4108 for more info. We went over Dave's ideas for the sales (quick interest catchers), principles (why), and the features (what). He wanted me to pick 3 from each category. We talked about things and made some decisions.

We then switched gears and talked about Campaign Rise (custom wire job project). They still need some automation and also some training. Dave asked some great questions and I tried to answer them to the best of my knowledge. Dave is willing to help us go get funding and monies for certain projects. We talked about how Steve used to do that and did an awesome job. Currently, he is doing more development work and working on the backend engine vs out front doing sales and talking with clients. We may need to help switch that around. Steve was able to single handed fund and keep the entire adilas shop going. He is really good at that kind of stuff.

One of the places that Dave wants to help out is with automating the reoccurring invoices. They already exist and auto queue themselves up, they just don't auto run themselves. We talked about adding a new setting per reoccurring that allows for manual process (default) or auto create process. We also talked about how the actual money part of that is whole other project and deals with three separate systems (adilas, credit card gateways, and bank or finance institutions). We have to mix and blend all of the pieces.

Light research on some of the ideas that Dave Forbis was pushing up dealing with billboard sites and marketing ideas. I then spent the rest of the block updating server settings and security stuff. Email updates to a few key people.

Prepped a bunch of things for Dave. Sent an email off to he and Steve to cover some of the topics we talked about this morning. Back on the sales tax project and code review stuff.

On the morning meeting with Josh and Alan. We went over a few new changes from yesterday. Alan reported on his work with Bryan and making a new black box database table (custom table - specific just for that client). Alan and I talked about some naming conventions and how all new black box database tables will have "bb_" to start the table name. For example: bb_53_some_table_name.

We spent a little bit of time going over some new needs for quantity and weight multipliers. Alan and I decided to add two new fields to get things into real numeric values. Currently, some of the people are using some of the existing fields, but those fields are strings or varchars (text based) fields vs real numeric fields. Alan will be making some changes. We know that this project will have two phases. The first one will be to add the new fields and then match-up what ever values we can. The other part of this is going through hundreds of other reports and top cart mini's (gram counters) and Metrc API reporting (state tracking stuff) and flipping the older text based logic into real numeric values and real math. We will be using a value of 1 in the numeric weight field as a default. 1 times anything is the same number. If they want to change that ratio, they will at least have a spot (numeric field) where to do it.

I then started to work on the sales tax project and bringing up all of the black box code to match the master code files (checking for new changes on the custom tax fields 6-10 and other dynamic naming). As a side note... Custom is awesome, but there is a flip side to that... It takes quite a bit of maintenance to keep things up to date if you are changing core pieces.

I spent some time reviewing some notes and info that Dave Forbis gathered up dealing with Stripe (online merchant processing and credit card gateway). See element of time # 4095 for some notes and links. After that, I got on a call with Dave and we went over a few things. We have four different topics that we will be looking into next. They are:

1. Reviewing some older things (tons of white boarding and graphics that were done by Dave from a couple years back) - The goal here is to circle through and pick-up anything that still has merit.

2. Start working on some billboard type sites. These are small websites that have a smaller focus and virtually point people and users to the bigger adilas application. These are things like world building, data assembly line stuff, new school accounting, 3D models for world building and digital story telling. Dave and I were also talking about some concepts that adilas is built upon that are either core and/or we've pushed pretty far. Dave was saying that we could create mini Ted Talk type videos and/or graphics. Get people thinking and talking. Use those pieces to point things back to adilas and what we are doing. Some great marketing ideas.

3. Currently, the adilas platform has a very high concentration of MMJ or Cannabis related industries. Maybe get a list of other kinds of companies that are using the system and show some of the diversity with how and what they are using in the adilas platform model.

4. Dave would like a list of the different domain names that we have and where we would like to focus on building small billboard type sites. I will get this together and send it to him. In a way, we are lightly playing the digital real estate game and trying to setup small little claims. Those claims have two fold purposes... One, they will become virtual billboard sites pointing to adilas and the core concepts that we are built on. Two, they will provide prior art - which makes it so that others can't copyright, trademark, and/or patent - intellectual property stuff. It basically strengthens and protects the main core of what we are trying to do. Good stuff.

Steve and I were meeting with Dave Forbis. There are some outstanding invoices that are owed to one of our internal developers (trying to get a custom project pushed through). We offered Dave to help cover those invoices and he will be doing work for adilas to help cover those costs. As a side note, this isn't a problem, this is actually a solution and a deal of sorts to help cover and advance all parties. Making lemon aid.

- We want to protect the developers and make sure that we draw a line in the sand and say... we need to renegotiate payment and work from this point forward (help to draw that line in the sand).

- Our clients need to grab and push forward their own dreams. We can't build out their dream from them without their help and input (ideas and funding). It has to be a two-way street.

- This particular project (the one that got forced through) hit right in the middle of a really hard transition between the adilas shop and somewhat of dissolving things and bringing all projects back under the main adilas account and/or allowing independent developers to run with their own projects.

- We have a need on the merchant processing level. We already have some deeper options available. We are looking to create a shallow and/or super easy solution to round things out... Our first assignment for Dave would be to figure out - what it takes to hook up with Stripe (online merchant processing gateway)? Could we be a re-seller of that? What would that look like? Do we need to certify on certain things? How can we help make this easy for our clients? What are the rates? What are the commissions? What are the requirements? What pages do we need to put into adilas to make it a turn key solution? etc. Basically, let's take this one pain point (easy merchant processing) and get it going. Yee haw.

Bryan and I jumped on the GoToMeeting session. Bryan had a bunch of files that needed to be merged into the master branch. We merged in the eXPO ecommerce white label code (300+ files). Bryan is still testing some stuff, but he needed to put up some of the code on a live server to show it and test it in a live scenario. No one really knows it is there, and you have to specifically turn it on, but at least he has some live testing things to play with.

We spent a little bit of time going over the adilas user group project. This is where we will let our user group vote on where we spend some of our money and where to focus our efforts based on weighted votes and funding. Good stuff. Anyways, Bryan showed me where he is at on that project and we made a few decisions on look and feel, flow, and direction.

I had a small phone call with Dave Forbis and talked about some project management stuff. We might be circling back around on some things.

After that, I went back in and recorded some notes from the day. As a side note, I'm really grateful for our team. They are all pushing on things and it is helping to get things done, where Steve and I by ourselves, couldn't have accomplished as much. I'm excited about that.

-You can choose! So, do it! Make the things happen that you want.

-You cna't barrow time like you can money . . .

-What is your level? Stick to it.

-Put a load on that you can manage.

-Learn to say "no". Nope and i'm Sorry, not right now,ect.

-What do we want to be as a company? Big. Small. Medium.

-Too many things going . . . life, work, hobbies, ect.

-"I've wanted out for years" . . . Am I planning something? What is it? Am I secretly working towards something? Patterns and justifcation.

 -Talk to the big guy upstairs - he knows.

-What do I want to do in order to stay?

-Instead of . . . "I want out" . . . what if it was "I want in" . . . there is what that would look like.

-What would you do to change it?

-What is the ideal?

-Find the balance

-maintenance

-building

-dreaming

-helping others training

-Virtually burn it down 

-If it all died or got destroyed, where would I be? Am I ok with that? Am I ok?

-Time allocations

Adilas time

me time

dev time

training time

fun

team - who are they?

-Cut down but keep somebody close - you need some help.

-Abundant model . . . lots of good choices - just like Sunday Dinner.

-It is okay to make tough choices . . . Do it and stick to it . . 

            HOURS

- ( 9:00 - 12:00 ) Steve and I custom v.s. standard, new projects v.s. older, maintenance v.s. building, etc. 

-Working on a data migration between servers for customers.

- ( 12:00 - 1:15 ) Bryan and planning out menu boards - brainstorming and trying to help him.

- ( 1:30 - 3:30 ) Russell and a session on changes and choices.

- ( 4:00 - 5:15 ) Meeting with Dave Forbis down town logan. Talking about developers, plans, and projects. 30 miles.

-Setup Dave Forbis with a custom email - for sending invoices.

- ( 9-12 ) GoToMeeting, work session with Nick and Steve. Emails, phone calls and follow-ups. Worked on the flexible custom logic black box option. Testing and getting things ready.

- ( 12-1:30 ) GoToMeeting with Bryan going over the live doc and RTping out results. Small bug fixes and going over some new projects - took a call from Calvin during this  session.

- ( 12:30 -1 ) Phone call with Calvin. Talking  about getting Sub inventory out to the API socket level.

- (  1:45-3 ) GoToMeeting with Nick. Finished up the custom logic black box and showed Nick how it could work. Answered some questions to help him with black box stuff.

- ( 3-5 ) GoToMeeting with Steve. Added in Sub inventory to an auto create page he is building. He gets info from a state system through API socket calls and then we allow our system to catch-up and build matching inventory records on the fly.

- (5-5:15 ) Helping Bryan get some advice on an auto - mated API sigh-up project. We went over scope and rough budgets.

- ( 9-12 ) GoTomeeting and getting ready to push and merge new files - 200+ files. Got files up on data O.

- ( 12-12:45 ) GoToMeeting with Bryan going over CSU output for a client - queary stuff.

- ( 12:45-1:15 ) Phone call with Calvin going over questions.

- ( 1:30-5:15 ) GoToMeeting session with Steve. Adding PO line items to a custom page to tie state inventory items to adilas inventory items. Building out custom page login . Phone call whith Dave Forbis about some upcoming projects.

-Make reoccurining elements of time.

-Demo time build it out for GPS stuffz

-thresholds and numbers based off of numbers

-Inventory levels and thresholds 

-New page and do it per location

-Notify them when a threshold is hit or passed

-time based

-API socket connection to Push the reports

-EOT #1014 in adilas community funded Projects

-Extra service and functions

-Text or emails alerts

-Max and min levels 

-Between adilas customers and do feeds and feeders

-(Hours)

-(1:00 - 4:00)Go to meeting with Alan and doing Exports to excel 

-(4:05 - 5:15)Go to meeting with Bryan - doing a custom quote on a dashboard and summary page.

-(5:15 - 6:00)Phone call with Dave Forbis - going over inventory thresholds, max and min levels,ecta.. API socket connections and general business stuff.

-Bid out and teach about feature creep, make it a good deal.

-Focus on the positive

-Corp template

-Location templates

- Payee templates

-Black box the whole system

-Fix the CCG project for Bryan and Dave Forbis.

-Two know holes on add/edit flex grid and custom settings and add/edit customer/clients and the custom settings.

-Project QUEUE and who is claiming what projects

-Open up the project management to all parties

-Bryan really likes the PM model

-Team has shrunk and some of the developers are doing their own

-Subsized

-More will be coming

-Teach our customers about our processes ( internal and external ) 

-Things take time and need to go through a process.

-Let them shop around and get who they want to do the job

-Recipes/Builds for quotes and project

-Prep,research, and quote

-Project Management and planning

-Code writing and development

-Help files/videos

-Code sign-off

-Testing and deployment

                                                                MEETING WITH DAVE FORBIS

-Capturing info 

-easy

-harder ones

-Lack of process

-categorizing the depth of the projects

-Project QUEUE

-Fall back on processes

-Planning with a purpose

-Compound concepts

-Dreams,goals,tasks, revelation, commandments and obedience

-Dollars off for in-line discounts

-Solidifying processes

-Optimizing flow

-Look at the optimal or the dream and then go from there

-Clients and personalities

-Miss - deliver on projects

-Multiple pressing levels

-Speed and turn overs

-Fall back on procedures

-Customer service

-Quality control 

-Competition and limits

                                TEAM BUILDING

-Forming

-Storming

-Norming performing 

-add some new personal settings for elements of time homepage.

-add a new horizontal time slot view for elements of time. This would be people down then left side and time across the top.

-(5:00 - 5:15)Recording notes and getting organized.

-(5:15 - 5:45)uploading files and running API updates for Chris Dunsey.

-(9:30 am - 8:30 pm)Logan, see E of T for details - Daniel, Nick, Bryan, and I were white boarding and brainstorming on Beaver Mountain and lessons/class based eCommerce and staffing flow. Kris came and helped - meeting with will on application universe plus world levels.

-Signing off on code with Bryan on his consolidated receivables and consolidated payables - Quotes with Dave and Louisa - working with Garrett on sub inventory. Long day but good stuff.

-(9:30 pm - 10:00 pm)Went to my parents house and helped them get set up on a new adilas system for and industrial recycling business. They ave great helpers and cheerleaders. I am so blessed.

-( Planning for code projects)

-What server?

-what corp id?

-other special id numbers?

-need to keep track of what files are being altered, added, or deleted?

-what are the differences between test and live.

-whats your to do list.

(END planning for code projects)

-with Bryan what branch are you?

-How can you renew this?

-what's your plan?

-technical aspects?

-what would make it move dynamic?

-what is your budget and how will you spemd that?

-What goals?

-possible problems/

-expand options?

-wish list?

(TIME)

-(9:45 - 11:15)Logan - worked with Daniel on some project planning. See Element of time number 194 in the adilas shop. Good notes. 30 miles

-(11:15 - 12-:00_ working with Bryan on some project planning. More good notes. See element of time number 195 in the adilas shop.

-on the adilas GPS core...add some basic stats on the graphical home pages and sub home pages.

-(12:00 - 6:15)phone calls, tech support, and helping guys with their projects. worked with Dave, Russell, Bryan,Daniel and Alan. Dave and Russell were talking about elements of time and I got to chime in and share some vision about watchers, feeders, automated financials, and history of elements of time. I had fun rolling things back and talking about the why behind the interactive map, 3D financials, world building, and how elements of time is somewhat of a precursor for other sections.

-(9:15 - 10:00 PM) paying bills and recording expenses.

10:00 - 6:00 Went into Logan. Daniel, Bryan,Dave, Bank with Bryan - see elements of time  - 30 miles.

9:00 - 10:00 Work with Daniel on data import for the Green Door. Metro.

 5:00 - 5:15  Recording hours,notes,ideas.

5:15 - 5:45 Working on the web make payment page for safe harbor,Problems with the checkout process.

 9:30 - 11:00 Went into Logan - trying to track down an error in the shipping and FedEx logic. Getting lost a bit.

-Go back to paper and figure things out.

11:00 - 12:30 Working more on ecommerce shipping and getting things ready to go. I ended up commenting out the FedEx shipping code and posting files online. I need to go back to the drawing board and get a plan. Called and left a message for Keats at Safe Harbor that FedEx shipping was disabled. Posted some new files online.

12:30 - 1:45 Working with Bryan on doing column counts on the view cart page for a black box that he is working on. We had problems with new code for sub inventory. trying to bring things up to speed.

2:00 - 3:00 Went over to Icon Health and Fitness to do an inventory tracking demo. Dave Forbis and I went to the demo. The people who wanted to see things were the running shoe department called Altra Running shoes. We got a small tour of the admin offices and found a conference room. We did the demo and answered questions. It was kinda short, but I hope it did the job. It was hard to read the guys we were demoing. I couldn't tell if they liked it or disliked it. Kinda of interesting.Dave and I talked about a bunch of things on the way back to the office.

3:00 - 4:00 Helped Bryan and Daniel Swainston on their bulk populate PDF project. Basically they have 6 PDF documents that need to be saved per person. Kinda a fun project. I also worked with Dave  Forbis on some quotes for dynamic money types and error logs for clients. I also worked with Alan on his project for switching between Flash and HTML for my cart favorite buttons. Alan is doing a great job and it is easy to follow his thought pattern and notes. All of my guys are doing much better as they start writing down notes and planning things out. I've been impressed. 30 miles.

- Quick note, Bryan has really been making some leaps and bounds lately in his programming knowledge.

- Things change all the time - root and anchor yourself in the concepts and doctrine, they will stay the same. The processes and procedures will change as needed. Make sure that you are anchored and rooted deep enough.