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.

Emails, paying bills, reviewing notes from over the weekend. Planning for a meeting with Steve. Reread some great poems that have a great message. Click this link to see the poems (on a different entry from a couple of years ago). Pushing up videos to a new folder inside of google drive.

Translating from post-it notes on 1/11/26

- Sunday morning - I was shaving, getting ready for church. I had a flood of ideas come into my head.

- We go for it on 4th down (football analogy)

- Reinforce the team - goal 1

- Goal 2 - We make sure that keeps working (meaning goal 1)

- Morning meeting at 9:30 am (get some communication stuff going on)

- Let people (our team) run... minimal on the micromanagement

- We focus on people... there will always be more projects and features

- CSS on forms for classic looking forms in the snow owl theme

- Look and feel to snow owl - help fix internal and existing pages look good

- Training - could be internal training, AI training, or external training

- Presentation Gallery - Keep pushing on that project

- Images for the adilas lite plan and the investment opportunities

- Abby - Talk to Steve about getting her involved

- Work with the design team - Chuck, Piper, Sarah

- Move key videos to Google Drive vs on the content server. It just can't serve them up quick enough.

- On the AI Agent - Use what we have - Set it up so that it tells people "I'm good at nav" - Polish the 350 existing prompts and tools.

- Suzi - Step-by-steps - small documents with information and instructions. She is really good at that.

- Sean and Cory - General Training

- Prepare for 100+ new accounts - What would that take?

- Open things up!!!

- If needed, we have others who can help - Dustin, Eric, and John. There are others as well.

- Shannon - She has been such a great helper to me

- Let Alan lead out - Help him succeed. He can do so much more than code.

- Get out of the way

- Leverage debt - put all of the adilas shop or adilas lite stuff into adilas as real payables - bring it out of hiding - true costs and costing

- Co-owner Advocate - possible new title, if needed

- Mini bank accounts for each person and/or department - help the team feel safe, supported, and funded

- Be in someone's corner - believe in them

- Overcoming fear - Satan wants us to run and hide

- Simple 1-pagers (one-pagers) - at a glance

Meeting with Russell. Doing some prep work on an older mock-up for a new invoice homepage that Russell had done, years ago. Dusting off the page and lightly revamping some of the mock-up in Adobe XD. Our goal is to make a page that has data, graphs, and uses Ajax and jQuery to run on a single page without any page refreshes. Should be a fun project. Lots of experimenting and decision making, all in Adobe XD vs coding it out. Good stuff.

Yogen Fruz Projects:

Completed:

1. Ability for the Browser on the FranPOS to access the adilas SAAS. (Suzi)
2. Setup test system with all items and buttons. (Suzi)
3. Reconfigure and add settings to POS environment. (Brandon)
4. Beverage and inventory labels (Stephen)
5. Research on Menu Boards (Stephen)
6. Setup e-commerce (Suzi)
7. Live test transactions in Canada for 2 days (Suzi)
8. Clover processing integration (Alan)
9. Live pilot in Canada (Sean and Brandon)
10. Icon Report for Eric's store(s) (Stephen)
11. Gift and Loyalty (Brandon)

In Progress

1. Gift and Loyalty (Brandon) - done
2. New hardware testing (Stephen)
3. Website discussion (Dustin)
4. Enterprise scaling (Alan)
5. Small update to the Icon App Report (Charles)

Future Projects (Included or Co-Funded)

1. Menu Board (Stephen)
2. Website (Charles / Dustin)
3. Delivery API (Alan)
4. Additional Reporting (Brandon)
5. Canadian nomenclature, such as State being called Providence, and Zip Code being changed to Postal Code (Settings)

Steve and I jumped on a GoToMeetign session. We rand a database update for Dustin and some new code that he had made. We merged in the new code to master. We then spent some time talking about other needed database changes. Wayne has been proposing a datasource update. That is one of the needed steps. We also discussed other database changes that are needed on the actual database and some of the primary keys. We need to switch out the auto number primary keys with unique combo primary keys. That will allow us to move databases and corporations (worlds) around more easily. Bulk and mass migration needs for some of our clients. Including bulk copy of certain pieces and sections within the system (items, buttons, photos, settings, logic, discounts, etc.). Talking over things and ideas. We will have to take the time and figure out tasks and processes.

Meeting with Dustin to help point him in good ways on the ecommerce stuff. We talked photos, paths, options, black box take overs (custom pages), and where to look and how to help build some custom pages. Short but good meeting.

Quick meeting and helping Dustin get started with custom web page settings for doing client facing websites for adilas clients. Good meeting. We also chatted and talked about some other projects and things. He showed me some of his photography (new macros) and other beautiful shots. Fun meeting.

Looking into custom web pages built by one of our developers back in 2023. These custom pages are for our clients out in the shop area or public web presence area (client portal area or ecommerce area). Pages like home, about us, etc. Sent out some emails to both Will and Dustin (developers) to make sure we were all on the same page.

Developer meeting - We were calling it our "pause and pivot" meeting. I started out and we talked about some of the new development that we have done. There are some cool pieces and projects that have been pushed out recently. We then rolled into an MVP wish list for ship A (small project list that we would like to get done). We then talked about the crunch that we are in (financial and cash flow stuff). It's not super bad but we are struggling a bit. We have spent huge amounts on client acquisition stuff. Trying to make people happy. It gets super expensive.

Alan did a small slide show and presented on some things. Alan did a great job. We had some open question and answer stuff. Dustin had some questions about maintenance budgets. See attached for Alan's PowerPoint. He started out with the 4D's, where we fail or fall short. We then talked about some cycles and how we plan on breaking those cycles.

Steve talked to the guys for a bit and then we wrapped it up. Quote from Steve "What you think about, you bring about." Not sure where he got it, but I liked it.

Basically, the plan is to pause and pivot, meaning, we will stop development projects for a bit until we can get caught up. The developers will do direct client work and custom code so as to relieve the burden from adilas. We are going to help them get projects and also help them with oversite, consulting, project management, and code sign-off. Another big goal that we have is to define ourselves a little bit more vs just going wherever the wind blow. This is both in people, roles, expectations, and development efforts.

Meeting with Dustin, Alan, Bryan Dayton, and Brian Mowris to go over the CardPointe merchant processing integration stuff. We chatted, got caught up, and ended up doing some tech support and code changes to the services. We changed ULR's (web addresses), help files, etc. It really helped to have all of the guys on the call to get the coders, the deployment persons, and the outside rep to make it all happen.

Just making a note about the need for good communication and good documentation (help and developer help). We spent hours today, not our fault, chasing assumptions from emails back in March. Finally, we got everyone connected and on the same page (ish) and we are making progress. We didn't get the help that we needed, nor the direction (from the outside party). We thought that we were done and all of the sudden, they want us to do a bunch of other pieces and validation testing (sub process). It took our guys, a new live account, and the outside rep to bring this all together. The test account was working perfectly. However, the transition between test and live got a little bit bumpy. No problem, we'll get it all fixed up. Just making a note on what we are learning.

New cart navigation tweaks. Added some new buttons and light navigation changes (window targeting). Looking into working on a mini header and mini footer. Met with Dustin to go over the new changes that we have made. I got to look at his new shopping cart and he got to look at mine. We may end up swapping out some pieces and borrowing from each other's designs. Both are new shopping carts inside of adilas. That's great.

Meeting with Bryan. Going over golf club (image a country club) type business options and how to use adilas to help with certain tasks. Things like scheduling tee times, tons of restaurant type needs, etc. Bryan was asking all kinds of questions. We have all of the tools, they just need to be tweaked a bit. Eventually, our meeting got into a who knows what type conversation. For example: So and so knows about this part, and so and so knows about this other part, etc. No one knows all of it. I was telling Bryan about some custom work we did for a Mexican Burrito place and how we were using ecommerce to help them place their orders with certain choices. I know that Sean and Dustin know about tons of other stuff. Alan has helped with other setups and custom code. Steve, Shari O., and Cory all know other things.

We talked about normal cart stuff, delivery, fulfillment stuff, custom webpages, and setting up custom skins or custom flow processes. I ended up doing some consulting, talking to Bryan about custom skins, and setting up a demo site. It takes effort to configure the tools. Once set up, the flow is much easier. Ideally, we would like to gather up all of the knowledge and put it in one place for use by others who want or need it.

Quick meeting with Bryan to fix an error. It was the same error that Dustin was having. We made a quick fix and I told him that I would get back with him on the resolution.

Jumped on a meeting with both Dustin and Will. They had not met so we did some quick introductions. We then talked about a new method/function that was introduced and was causing some issues. We pitched some ideas and Will is going to make a few changes. We ended up getting into some deeper underlying code stuff. We think we have a plan, and we will get it all figured out.

I got a text from Dustin saying that he was on another meeting with a client. So, I did some emails and then switched over to the bulk clear customer loyalty points project. I'm working on creating forms for both the classic theme and the snow owl theme (look and feel stuff). After a bit, I got a text from Dustin and we jumped on a Zoom meeting. We are trying to fix an error that got introduced by another developer. We decided to setup a meeting with the other developer and pitch some ideas.

Merging in code for Will for a custom website project on data 16. Including some new ecommerce files and settings. Working with Dustin on some custom error messages. Looking into a small error message on his branch but not showing up on the master code branch. Found some possible errors with another developer's code that was affecting Dustin's project.

Recording notes from 11/27 to 11/28.

Working with Bryan. He had met with Dustin and they came up with some ideas. We did a small session with Bryan telling me what to do and how to do it. That way we could push it up live to test it with a bigger record set. Bryan doesn't have access to push things up to the servers yet. We tested and tested. We decided to go a totally different route. I gave him some new marching orders and a really simple mini plan. He's going to start working in that direction. The other way had too many unknowns.

Dustin and I met up to go over his new integrated side menu cart page. We spent lots of time on screen resolution, layout options, anchors, refresh rates, and user interface topics. Good work session. We did lots of drawing, zooming in/out, and making some plans. After that, we talked about merging code, resolving conflicts, Git, the bash window, and bit bucket stuff (code repository).

Screenshots and prep work to help Dustin out with his new integrated side menu shopping cart. Coming up with ideas and sending him an email with ideas. We then chatted on the phone for a bit.

Working with Bryan on saving large files as CSV files. We were talking about session variables inside of the CFC's (ColdFusion components) and best practices. Bryan is going to rework some stuff and get back with me.

On the phone with Eric. We were going over 2 main topics. One was his new code for both EMV/Chip reader credit card transactions and normal swipe or manual entry credit card transactions. He has a branch that he wants me to look over. The other major topic was dealing with an import for a client that had customer info and customer loyalty points from a different system.

After working with Eric, I tried to track down a possible bug with scanning a sub inventory package or sub inventory number. It ended up being a setting that prompts for a specific sub weight. I turned it off and the sub barcode scanning worked great. We wanted it to skip that extra step. Just had to flip the right setting. No code changes took place. I reported back to Steve, Cory, and Dustin.

Quick 20 minute meeting with Cory to go over projects and priorities. I then got on a phone call with Steve. We were going over general stuff, sales, demos, meetings, and new shopping cart stuff. Steve requested that I keep pushing on stuff and also help out with Dustin, Eric, Bryan, and Will. I wrote a few things down in my notes to follow-up on with the guys.

Emails and going over a new state level document for selling trailers in Texas (TX 130-U). Going to be working on that project later today.

Shopping cart meeting with Cory, Steve, and Dustin. I gave them a small demo of my new mini scan cart. Dustin is working on taking that code and making it into his own little cart, specific for a single client. Eventually we will use it for other clients, but right now, it is being developed for a single client. After the main meeting, Dustin and I stayed on to go over some other stuff and to make a small to do list. Pushed up some code to fix a small misspelling.

Quick phone call with Eric going over USAePay stuff and merchant processing options. At some future point, we may need better documentation and/or a hardware specialist on our team.

Meeting with Dustin to go over things. We started out on GoToMeeting and then switched over to Zoom. He had a list of questions. We jumped in and helped him setup his own new shopping cart. We may alter the name, but it will be called something like the integrated side menu cart. It's kinda custom but may be used by other people later on. I'm hoping that our little session will end up saving him tons of time so that he can hit his deadline. Good stuff!

After we got all of his new cart stuff under control, we switched over and talked about FTP (file transfer protocol) stuff. I showed him around, got him info, and we did some light training. He's going to work with Wayne and our hosting company to get everything else all setup. Good session.

Merged and pushed up some code for Dustin. Emails to the race director for the Bear 100. Looking at notes on Otter.ai from our earlier meeting with Pete. Phone call with Steve to go over the meeting.

Looking at code with Dustin. We ended up grabbing some older stable code and comparing it to the new code to see what changed. We were looking for a missing div tag (containers, rows, columns, etc.).

Great internal training event. John was running the show today. We had Brandon, John, Danny, Eric, Alan, Dustin, and Bryan on the meeting with us. We were going over the adilas docs (online style guide and code snippets), light review, going over conventions, components, and other style guide stuff. John was encouraging the developers to use the docs and play around with things. As a side note, John has also started some adilas server docs (major backend stuff) as well.

Lots of good discussions. Topics ranged from docker stuff, older code, bootstrap versions, and sign-off guides for development and frontend GUI stuff (GUI is for graphical user interfaces or UI/UX user interfaces and user experiences). We had some good practice sessions and John had prepped some code with some flags where he wanted us to work and change things.

It was great for all of the guys to be on the meeting. I did snap a screenshot of some of the webcams (see attached). We talked about using data 0 as the starting point or standard for a number of things. Especially if we wanted to duplicate and/or use the same things over and over again. The conversation then led over to talking about the future and where we are heading. We spent some time talking about the new framework and being able to swap out dependencies and what not.

One of the last things for the normal training session was a discussion about requests for future training and crossover training. Here is the quick list, not in any specific order.

Future Training Session Ideas
- Cfscript
- Javascript/JQuery
- Back End (Models, Services, DAOs)
- API's - Internal API sockets and external API sockets
- Ajax
- Testing
- Custom CSS & Print CSS

After everybody else left, John and I did a small review of the training session. We were chatting about options and feedback. John and I may start with some CSS and theme stuff (planning for the future). See attached for 3 different videos that we did from the training session. Great event.

Zoom meeting with Cory, Kelly, Steve, and I. Going over plans for sub inventory reporting. I took a number of notes. See below.

- Kelly did some prep work and had a small spreadsheet- Here is the link: Web link

- Some of the report settings need to be at the user level vs the corp or global level- for example: the new advanced part search settings. They are controllable at the corp level but not at an individual user level. We are seeing a need for deeper levels of control, per user.

- She, Kelly, found a good report (that still needs some tweaking)- advanced invoice sub line search for all item categories. The current report shows and does some sub attribute grouping (text based off of the names).

- Kelly thinks that a limit of a 31-day month (whatever the range) would work for now. For both PO line items and invoice line items. If they want to pull info per item category, no date range limit. If they want everything or "all" we limit it to a month or 31 days.

- Ideally, she would like grouped output for PO's, invoices, and items. That's where subs play (currently).

- Steve is working on some sub inventory reports right now.

- We have a currently working model in the advanced invoice sub line search. If the part category of "All" is selected, the actual search page shows all possible sub attributes as filters. We then pass that list of combined attributes over to the results page. The results page then loops over the combined list and fills out what it can. We may be able to use some of these pieces.

- As a side note, we actually looked over some code for the working model to see how it was switching, grouping, and pulling the data. For now, we may take that code and push it over to other sections as a patch and/or band-aid of sorts.

- The sub reports need all of the main line item details plus the sub information. Currently, the sub reports are only showing the sub details. Kelly wants all of the data out of the system. Cory wants to be careful not to get in trouble if we add a bunch of new columns (past history with clients complaining - changing their reports or exports).

- The reports homepage is kinda messy- We may need to rework that page to make it look better.

- We need sub attribute information on its own, parent attribute information on its own, and mixed sub and parent attribute information together. Along with this... We need these same reports for PO's, invoices, and items in inventory. We need all of these pieces. Consistency across those reports.

- Kelly is sort of stuck- helping out the clients. She is pulling tons of reports and piecing them together. She is looking for some time savings and better reporting, out of the system or out of the box vs having to pull things and piece them together.

- Up next, once we have the good reporting that we need, we can build in bulk update tools where you can see it, fix it, repull the report. Export it as needed. We need the visual representation of the data first (good reporting). The other features and tools will come later.

- Steve, Dustin, and Alan are going to be working on some bulk tools for subs.

- Be able to export beginning inventory, ending inventory, and what is in between. That's the goal.

- Kelly likes the super invoice line item search/report. Could we add on a bit there? That might be nice. We talked about creating a super sub invoice line item search (same as above with subs). Maybe a link to that new page from the bottom of the advanced invoice search page (maybe at the top as well).

- At the end of the meeting, Kelly was asking what we needed to get going. She is going to build out a spreadsheet with columns and instructions per column for us to use as a reference. That should really help. We will pass this on to the correct developer to help them know what is wanted and needed.

On the server meeting with Wayne, John, Cory, and myself. Sean and Eric popped in for a bit as well. We were talking about email servers, merging in code, and making plans for pushing up new pages. Eric joined and Wayne merged in his code for the global item catalog - enterprise stuff. Once that happened, I pulled the branch down on my local box and was clicking around to see if there were any errors. Looked good.

Small code merge for Dustin. Then working with Wayne on his ColdBox framework stuff. We talked about users, payees, vendors, multiple corps, and memory and session management stuff. Small Q&A with Wayne and John about the framework, plans, and how we will handle certain pieces of the puzzle. Light plans for the future (wish list stuff). After that, John and I spent a little bit of time talking about internal education and training for our developers.

Phone call with Shari O. touching base on budgets, tech support questions, and a new project for a client. The client has reached out to both Shari O. and Cory - trying to double dip and push their project through.

Shari O. had a question about the adilas phones stuff. We looked at the page and there was some code that tried to show a sub or outside website that was not in a secured SSL (https) site. We made some tweaks and pushed up the code. Kind of a temporary quick fix.

Wayne, John, Cory, Shari O., and I were on the meeting. They were talking about a client and their servers needs. They (our client) may be closing some of their locations down but want to keep other ones active. Light back and forth on whether or not any server specs needed to be changed on that server. There was also a conversation about the need for more tech support. Both on our side and on the server side (the hosting company). Often we don't need help, but when we do, it is kind of painful.

Cory had a list and was checking on different projects. Good dialog and good back and forth. Wayne may be moving on and working less in the next few months. He is wanting to be more of a part time or fully retired. We need to get plans in place to figure out who is going to be taking over that role and what documentation and knowledge needs to be transferred over. We talked briefly about Dustin maybe wanting to help with servers and also looking at existing knowledge levels. Do we want to bring up one of our own guys and/or hire it out to someone else with more knowledge? Great questions.

Wayne was talking about options for virtually building a new ship. This has been a discussion and topic for years. Do we keep building and tweaking what we have or do we rewrite things and try to go all new (code, architecture, design, etc.). There are pros and cons to both approaches. Due to current budgets, we have to stay with fixing what we have vs building all new. That can be painful as well and takes a lot of time. Wayne was talking about doing a sample project and seeing what kind of time it might take to move the existing adilas structure over or under a new standard framework. There are a number of unknowns, but worth looking into.

Towards the end, John and Cory were talking about look and feel stuff. Also, Wayne and John will continue to work on some outlines and plans for the system architecture stuff. Making progress on most fonts. We'll take it!

Touching base with Sean. John jumped on and was updating the printable expense/receipts to show verified payments. I merged in some code for Dustin and then started working through emails. John jumped off to work with Wayne on server documentation stuff. I spent the rest of the time recording notes from yesterday (3/21/23).

Quick meeting with Bryan. We were going over some progress on his AJAX code for selecting items to do bookings and reservations. He got with Dustin and the two of them made some good progress (code wise). They also used some ChatGPT to get some ideas and answers (open AI - artificial intelligence). Making progress.

Pushed up some files for Dustin. Working on the duplicate recipe page. Back working on the line items. Prepping to go live, even though it isn't done yet. Pushed up code and sent an email out with the update info to Steve, Cory, and Kelly.

Emails, phone call with Eric about bulk tools, enterprise item catalog features, and storing user selections in the session scope. Merged in some code for Dustin. Reviewed some documentation from Bryan on the Digitech payment solution. Paid some bills.

Both a pro and a con - there are so many custom integrations that we have done, nobody knows all of them. Sean and spent 45 minutes going over credit card gateway problems, issues, and options. This could be how credit cards get entered into the system (manual keyed, swiped, or chip reader and other hardware options) or how each gateway acts or reacts (different variables, paths, and requirements).

I'm going to request some documentation from Eric, Alan, and Bryan. They have all worked on different merchant processing integrations within adilas. We need to help and gather some of that documentation up for tech support and our sales team. That is much needed information. Otherwise, we are somewhat blind as each integration is so different.

Dustin jumped on the meeting, and I helped him get pointed in the right direction on a required file for doing QR codes. Cory had an icon app email issue and we looked into it for a bit. There seems to be a duplicate number in the email settings. We also chatted with John about the chooser and choose more interfaces. John and Cory were going over changes to the chooser. Lots of different opinions - some like numbered, others like alphabetical, and some want to be able to search.

Once again, nobody knows all of the pieces. That creates a mystery of sorts. Also, it is hard to pick things up (projects) after the fact. Without the knowledge of what was going on and what was requested, some of the pieces, by themselves, don't make much sense. It's all part of a bigger puzzle.

Research on investing and a company that invests in SaaS type models (software as a service). Pushed up some code for Dustin. Recording notes. Phone call with Shari O. and doing email stuff. General to do list stuff. Looking up adilas videos on YouTube and adilas university.

Emails, paying bills, updating credit card on file info, recording notes, and pushed up some code for Dustin. Random little projects.

It was just Steve and I on the morning meeting for the first 20 or so minutes. We were talking about getting people started and getting things going and helping them to get up and running. Here are a few other random notes from our meeting.

- At some point, we would like to circle back around and get back to the vendor logs or payee/vendor logs project. Basically, this would be similar to the customer logs but for both vendors and employees (users). Steve started this project but it got put on the shelf as other things came up. We need to circle back around, when possible.

- On the chooser page, what if we allowed every possible page. That could be really cool. This is where a user gets to choose what they want to use for their default homepage.

- Steve was asking about settings and how we wanted to organize things. I told him that we have at least four known levels for settings that we know of, right now. They are: corp-wide settings (at the world or corporation level), group level settings (any of the 12 main player groups or sections that we have a homepage for that section), page level settings (currently using the slide out drawer on the right of the snow owl themed pages to show page level settings), and user settings or personal settings. At some future point, we may want to build out a master settings page that showed where everything is and/or is located. We have things spread all around right now. This may be a project for fracture - future project.

- The whole thing of adilas seems to be a pyramid or stacked layered application. There are tons of different levels that build on top of each other.

- The magic seems to come from progress and ideas. We do something, someone else sees it, adds to it, requests something, we build it out and/or add to it, and it starts all over again. Like a giant snowball or idea farm.

- One of the huge foundations seems to be settings and permissions. We are also seeing that these two key foundational pieces tend to split, fracture, or break into subs. Almost an infinite level of control and customization. Very interesting.

- Sean and John popped in and gave us some updates and reports. Dustin and Kelly also joined for a little bit. Their general vibe or message was - that people need help (generally) and if we can help, we are able to slide into place. It could be data entry, tools, functionality, systems, normalizing data, sales tax, inventory management and controls, financials, etc.

- My observation from today's meeting - it seems like all of the team is playing well together and helping to get things done. No way, one person could get all of this stuff done and handled, as it is going along and happening. I'm super grateful!

- John was showing us an update on the chooser page to help users select, view, and setup their default homepages. He is making good progress there. More good changes coming in the look and feel department. Good stuff!

John and Steve were on the meeting going over the chooser page and graphic options. We kept going back to ways of limiting things down by selections and/or settings. We have a lot and sometimes it gets hard to sort through things. Sean was asking about email stuff and what we need to do there. That is still somewhat of a mystery with some unknowns. We went back to talking with John about the look and feel changes that are here and/or coming down the pipeline. There is no way to get it all done at once. We will have to allow for different rounds and being willing to circle back around again and again. All part of the process and that's ok.

We talked about being able to search and filter different options. John is going to be working on adding things to the adilas docs. Dustin reached out and had me push some code for him. Quick phone call (mini server meeting) with Wayne. He was not in the office and was out doing stuff with his family. We'll reconnect next week and push more on the email stuff.

Dustin popped in and had some questions for both Steve and myself. We talked quite a bit about email stuff. That is a hot topic right now. It got a little bit heated and crazy. I'm trying but some of this stuff is over my head and somewhat out of my hands. Lots of pressure, both internally and from our clients.

We were supposed to get on a server meeting, but Wayne wasn't able to make it. I spent the next hour from 10-11 am rolling back about 38 files from pointing to the adilas content server back to the older adilas university site, where we had the old email API functionality stuff.

This is a side note, but sometimes I really wish that they (our team) would ask someone else to do it. I don't like being the fix it guy. That's a lot of pressure. Not my favorite thing, for sure.

We started out the server meeting. Those who were on the meeting started out by reviewing the last meeting (morning sales meeting). We then jumped in and started going over server-based topics. The first main server topic was email stuff. We are going to be using or trying to use the adilas content server to send it out vs the adilas university site. The old adilas university site is on a shared environment and is an older server. We are going to see if we can get more up time and new features by using one of our fully dedicated servers.

Next we spent some time talking about data 0 and maybe updating or upping the CPU count and RAM memory. We talked about Hostek and the customer support that we are, were, and hope to get. At times, we really need more support. Currently, it hasn't been as good as it used to be. Sometimes we get slammed and need help. We don't need it all of the time, but when we need it, the support is critical. It all deals with server up time and keeping our clients happy.

Touching base on other projects. Wayne is going to be reaching out to Eric and Dustin to see if they need any help. Cory and Wayne got into some technical compliance stuff like SOC 2 reports and other compliance stuff. Lots of talk about risk mitigation and managing risk. While we were talking about risk management, we got into a conversation about accessibility issues and making content available for persons with disabilities. That got pretty deep but this seems to be a section of the web that is expanding, and requirements are being made more for mainstream sites vs just specialty sites. Lots of special tags and flags for screen readers and such. We also talked about the cost of making a fully accessible site. The costs are huge, especially for little guys. Anyways, it seems like there is some legal cases and such that are pushing this agenda further. We may need to keep an eye on it.

We spent some time looking at some of our other servers and database stuff. We then switched subjects and Cory and John were talking about projects and new CSS look and feel stuff. We would like to get more user feedback. We are doing the best that we can. We are constantly improving our code every day. Talking about new settings and dealing with look and feel and personal preferences. We would like to get good feedback and keep trying to connect the backend code with the frontend user interface (UI).

We looked at the calendar and did some scheduling for some of our new projects and rollouts. Right at the end, Cory was reporting to us on a couple of small bugs. We'll have to circle back around. We ran out of time.

Emails and merging in some code for Dustin.

Working with John on bank transfers. Pushed up some files for Dustin. Then back on the code review stuff with John. Looking over the bank homepage changes. Pushed up the new pages for John. Yeah!

Danny and Sean popped into the meeting. Nothing major going on but just talking about sales, demos, and how to put our best foot forward. We talked about getting small quick screenshots and samples to help go along with our demos. Currently, we bounce inside of a demo site, show someone around and then bounce somewhere else. I use the word bounce, and we are fine with that, but to a new user, that seems like you have to know a lot, in order to jump or bounce around. They want to know that we have certain things and want to get their hands held for the first little bit.

Because we are so flexible, it sometimes intimidates people and new users. That might be a good thing to remember for fracture (future project). Maybe setup a super simple step 1, 2, 3 process that always work (for example, the normal front door entance) and then show them how they can change that if they want to (side doors, back doors, basement doors, garage doors, etc.). Dustin was calling it handrails. I might be nice to have different training modes or education modes. If you turn it on, meaning education mode, it virtually tells you what to do. If you turn it off, you can bounce wherever you want (like normal). Almost an analogy of training wheels vs freeride or normal bike riding (without training wheels).

As a small side note, my dad (Wayne Moore) was saying the same things yesterday. We were looking at the main adilas.biz website and he was saying, I like the verbage but I want to see it (super tiny clips or screenshots). For example: It says "real time visibility and control with inventory management". Ok, what does that mean and can you quickly show me (a picture is worth a 1,000 words type mentality)? Just some quick screen shots.

As a note, there may be different levels. We may need a quick overview, a quick this is that (demo style), and then a deeper how to or let's really learn and master this. I can totally see a need for different levels of screenshots, examples, tutorials, and step-by-step walk throughs. Good stuff.

2/15/23 Edit pages:

- top_secret/secure/statement_home.cfm

- top_secret/secure/add_edit_statement.cfm - step 2 - select statement date range (2 of them)

- top_secret/secure/add_edit_statement.cfm - step 3 - set the dates (4 of them)

- top_secret/secure/bulk_receipt_verify.cfm - top form and looping over the results

- top_secret/secure/bulk_deposit_verify.cfm - top form and looping over the results

1/26 check and pushed final pages with Brandon.  Basic project complete.

1/23/23 checked and pushed 600 pages with Brandon.

1/18/23 checked and pushed 300 pages with Brandon.

1/13/23 updated more datepicker code on pages.

12/21/22 updated more datepicker code on pages (see below). Will connect with Dustin on testing:

12/6/22 Consolidated the Time code that Brandon and Charles did, and met with Brandon to check the code.  Two news and update pages have already been created for this project "Elements of Time Homepage Will Have a New Look" and  "New Look for Working With Time". Next we plan to have Wayne point the data 5 server to the branch (project-2260combine) so that the code can be tested on data 5. 12/5/22 met with Brandon on what we wanted to do with time:

    Date picker:

1. We want:
2. 1. put in 1/1/2 (characters)
3. 2. get 1999 when we put in 99 (not 2099)
4. 3. truncate correctly: 1999 goes to 1999 not 19
5. 4. if I supply a date in the past on the first click I want to go to that first (not how it is currently functioning going to todays date).
6. 5. create documentation in help file and in Adilas docs (update).
7. 6. update to all datetime instances. Check for date validation and go backwards (if I am validating a date I am putting a date in). (search for 'datepicker', '_date', 'date_', '
8. from_date', 'to_date', -form fields are what we are mostly looking for)
9. 7. on the times be able to put in a one digit (1 PM not 1:00 PM)
10. 8. put the datepicker on the content server.
11. 9. roll it out in small batches (10 or so pages instead of all at once)
12. 10. leave Bear100 code alone.
13. 11. communicate with Cory and John.

12/2/22 Spoke with Cory and John about the project.  John said there is a bug with the new picker that needs to be resolved. He said there is some information in the Adilas Docs that may be helpful (Adilas Docs>hamburger link>Adilas Core>components (top links)>date picker (left side dropdown, 'here' link - If you need more information on flatpickr for some reason you can find the documention for the plug-in here ).

Next, all of the datepickers in the system need to be updated to the new datepicker.  Brandon sent an email regarding what needs to be done to update all of the datepickers as follows:

 I found a page that shows some simple date picker stuff. Here is the page: top_secret/secure/add_bulk_flex_grid.cfm – if you search for “picker” it will take you to the different options that are needed. Here is a quick rundown.

• 1st include is set right before the include for basic_css.cfm it looks like this:

 

 

• Then any new date field will need the date-picker class. For example:

 

        on input fields --- the key is the class=”date-picker” part or css class stuff

 

• The last include is set right before the ending body tag. It looks like this:

 

Anyways, there are 3 basic parts… the top include, the new class on form fields, and the bottom include. This is true for any page that is a full page (no black box options). If it does have black box options, it is slightly different. Anyways, just wanted to get you some information. I don’t have a list of files right now, but we want to spread it (the new date picker) across the whole site. If you want, we can meet and build a list or if you want to poke around and fix things, that would be great as well.

The only page that I know we don’t want the new date pickers on is some of the bear 100 custom files. They get dates entered in via special formats and the date picker screws things up. Everything else needs to be updated (to my knowledge).

Touching base with Steve and Sean. Planning and scheduling demos. Talking about getting my dad (Wayne Moore) involved in some adilas sales. He is really good at talking with people, organizing things, and taking things to the next level.

Cory and Dustin joined the meeting and we switched gears and started talking about a possible error or errors. This took quite a while. We talked about possible date picker problems and using our new date picker. Everything keeps moving. The ground we stand on is in constant motion. That seems to be our reality.

We then switched over to other projects. Cory had a list and we went through that along with multiple things from emails. We got into a discussion on the hierarchy of different settings and which ones take precedence over other things. That can get tricky. It gets even trickier when you get layers of logic involved. Anyways, making progress there.

Hours of emails, tech support, and other stuff. Emails to Wayne, Cory, Kelly, etc. Going over validation stuff, routines, logic, fixing small bugs, and looking into sub inventory data and attribute mappings. On a Zoom session with Kelly, Wayne, Dustin, and I. Looking over code and testing things. Kelly even pulled a client onto the meeting to get some approvals and have her do some live testing. Pretty deep session.

As a side note, if all is going well, the value of the systems admin person doesn't seem that important but when all things go crazy and he/she helps to get it back in check, the value of that person is huge. They are often overlooked when seas are calm and the wind is not blowing (which means that they are doing a good job). Lots of unseen efforts. Thanks Wayne!

Server meeting. The whole first part of the meeting was Dustin and Wayne going over some new things for cultivation. We talked about doing a new database field for locations and calling it a location type (normal, retail, warehouse, backend, vault, etc.). That almost sounded like sub locations, but we didn't end up going there. I've got a bunch of other notes on sub locations and sub phases.

Kelly ended up joining us and we found out that we thought was a coding error was just a data or user error. Great dialog back and forth between Cory, Kelly, Wayne, Dustin, and I. It was a great session. Here are a few other things that I thought were interesting:

- Being consistent - across the board

- Forcing some clean-up and maintenance

- Talking about reports and proper data drill-downs - getting to the underlying data quickly and correctly

- Mixing different vendors and locations (report settings and filters). If they weren't just right, the reports would return different data (filter stuff).

- When Kelly joined, you could literally hear and feel the difference between a power user and a backend developer. Kelly, as s power user, had so much more depth of knowledge of what went where and how it got there (using existing tools). The developers could look at the data and the logic, but it didn't make as much sense because they had no context for that data. Interesting!

- We are trying to smooth things out. Some of that will be through new interfaces, training, and education.

- Some of the challenges of being so dynamic (as a software system or application). It is both a blessing and a curse (how flexible we are).

- What does it cost to keep clean data and how do we main that clean data?

- We would love to add some trouble shooting pages and/or known error reports or pages. Basically, a quick way to find and fix data that may have an issue. Flag it and then allow them to change it so that it is correct. This would be awesome if we could add this for our fracture project.

- Manual tests and audits of the data - Is it a code issue or a data issue?

- We talked about switching over our email servers and how that project is coming

- Talking about getting system-wide aggregates and how best to get that data in place. This is huge, we just haven't done it yet. We have all of the transactional data records, we just need to virtually let the cream rise to the top.

- Kelly and Cory are going to be coming up with some standard testing forms (what to test and different scenarios for testing)

- Cory had a small list of other projects that we checked in on and got small updates.

- John and Cory were going over end of the year payroll projects, once everybody else left

Emails, phone calls, and helping Dustin with some code. We ended up having to get Wayne involved to help us figure it out. Basically, Dustin's local branch was old and then when we went to make a new branch, there were updates that he needed that were being required for his new branch. We had to manually updates some database tables and then everything worked fine.

Work session with Bryan. Checking out code for the auto email project. Looking over code and going over the project flow. The branch is showing multiple merge conflicts, so we will have to do a manual merge (that takes a little bit longer). We also hit a snag on one of the include files (send email action pages). It is called from outside in the public folder but it resides inside the top secret/secure folder. That folder is protected and requires a valid login and session. The code worked great during testing but as soon as it goes live, it will be called via an automated schedule vs a logged in user. Basically, the validation on the secure page will block it from being used due to a missing login. We will have to restructure some code and put a standalone file out in the public folder to help do the same process.

Towards the end of the meeting, we flipped over and were going to look at some of the AJAX stuff that Bryan has been working on with John and Dustin. We were having conflicts while switching branches. We will reschedule a time to look deeper into this. Making progress.

Emails. Back and forth between Dustin and Chuck. Dustin was doing some testing on some new code changes.

Spent most of the work session working on the bulk flex grid tools. Got into some local testing with some JavaScript to keep track of which fields were modified. Nothing too crazy. Getting back into the project.

Chuck and I were working on the date-picker code. He had another 30+ files that had been updated. We did some local testing and merged and pushed the files up to data 0. We ended up sending an email to Dustin to help us test some of the cannabis specific pages, as Chuck and I didn't have the correct settings or access levels.

We did a quick reimbursement in the system for font awesome (icons). I also invited Chuck to help with the client facing scheduling project that is coming up. He is excited to help there.

Alan and Shari O. joined our server meeting today. Wayne was reporting on the server settings and new corp-wide setting object code. Both he and Alan have been working on that project. It is getting really close to being launched here in the next couple of days.

Wayne was also talking about a different data export project and doing some validation and text normalization. Basically, a way to check for special characters and then replace them (the special ones) with a normal or standardized character. For example: take different spaces as a sample - there are big spaces, narrow spaces, thin spaces, non-breaking spaces, special width spaces, etc. - all of those would just be converted into a normal space vs the special characters. The same is true for double quotes, single quotes, bullets, dashes, spaces, and all kinds of other special characters. Wayne got a new library from Ben Nadel to help standardize some of those special characters. All part of keeping good data that can be used by us and by other parties (for example - in the data export for a specific client).

We talked about moving and combining servers and sites to save money. This is mostly dealing with clients who have one or more dedicated boxes. If they shrink or close some of their locations, they don't want to pay for multiple boxes (servers or VPS's). Wayne was talking about some possible hybrid type solutions and being able to configure and setup multiple datasources and folders (sub sites) per box. This is a prep step for the datasource project or world building stuff that we would like to get to eventually.

This topic lead us into some talks about different clients and options for data storage and archiving data. As a side note, Cory was being very careful about trying to protect us and make sure that we are covering our costs. Just because we can do something, doesn't always mean that we should. There is a balance between time, money, effort, and promises made. It also plays into - what are our future plans? We talked about billing, value, perceptions, and making sure that we really cover our true costs.

Alan and Wayne got into talking about the new settings and changes on that side of the fence. We really want to keep moving that project forward but may need to wait a couple of days so that Cory can help with the testing and tech support side of new releases (system wide changes being released to all servers). Towards the end of the meeting, they were talking about dates, times, and coordinating deployment and rollout of new changes. That is awesome.

Everybody except for Steve, Cory, John, and I left. At that point, John gave us a small report on what he has been doing. He reported that his billing was in, times had been recorded, he is working with Dustin on some server training, doing other server maintenance, and working on other projects. Cory is really trying to make sure that communication channels are up and going between Wayne and John. Trying to make sure that we aren't duplicating efforts and everybody is on the same page.

Cory was asking for reports on different projects. Wayne joined and we jumped into the server stuff. He was requesting more specific errors to be reported via email. If the error reports are too generic (server 6 is down), that doesn't give him much to go off of. It would be better to say something like, server 6 is denying login access or something like that so he knows where to start. Anyways, he was requesting more details when reporting problems and server errors.

We talked about the database clean-up for data 0. Next, we got into looking over errors and slow pages and slow queries. The main problem child queries are all dealing with corporations with tons and tons of inventory, invoices, and sub inventory. There is just a lot of data there.

At the end, John gave a small report to us. He has been working with Dustin to help get Dustin up to speed with server stuff and pieces.

Dustin joined us and he and Cory were going over some live testing issues and the need to roll back a project. We did so and got it all merged back in and pushed back up to the servers. As a side note, they were talking about the cost of a bug. It takes extra tech support, causes stress, emergency development, code sign-off and re-deployment, and it frustrates our clients. There is always a cost for pushing up bugs.

This is just for fun, but Cory was saying - No pushing new code up on Friday! That's a bad idea.

Dustin and John left and just Cory and I were left on the meeting. We started going over a list of projects and questions that Cory had. We went over my cart favorite buttons and how they play with subs (child inventory). Next, we talked about 3rd party solutions and hardware.  They are both needed, but sometimes give us a black eye. We can't control those pieces very easily. We went over a question about active and inactive users, editing relationships, and possible solutions for resetting things and hiding inactive users. This already happens most times, but there are certain scenarios where both active and inactive users are needed. Say like a salesperson that is assigned to a customer. If an old assignment was put in place, they don't just automatically clear themselves if someone gets fired or made inactive. Those are still real relationships that need to be updated and reassigned. It can get tricky.

New files for Bryan for his invoice due date project. Also helped Dustin and merged in some code. We repeated the process a couple of times, each with small changes. Lots of back and forth.

Dustin and I looking over a possible code problem. Doing some live testing. Ended up finding the error and it was a client's data and them missing something on their side (Metrc rooms) for an API socket connection. Made a few other changes and pushed up code.

On a GoToMeeting session with Dustin. We were looking over code and pulling information out of JSON object for AJAX calls. We briefly talked about adding in even more asynchronous loading and data lookups, throughout the site. Dustin is getting into deeper JavaScript functions and dynamically reusing things. That is awesome and will save time and energy down the road.

Emails, research, and odds and ends. Met up with Drew from High Valley Bike Shuttle to setup his USAePay gateway and API keys. We got it all setup and did a practice transaction. After that, we did some light training and looking around his site. I'm excited to help them out and get them going.

Talking with Steve over a GoToMeeting session. We went over and covered a number of topics. We started out talking about merchant processing options. We already have a relationship with USAePay. However, we are also looking at NMI, Stripe, and Elavon. As we get more or new clients, they will have more and more merchant processing needs. Trying to stay ahead of the game.

Steve and I were also talking about the different mix of team players that we have. We got into talking about religion, beliefs, controversial topics, cannabis, non-cannabis, developers, sales, and how to balance all of those pieces. Our mix almost creates an interesting culture and a specific need (who else if needed). We don't have very many that can crisscross either based on the beliefs (religion and feelings), which topics that they are assigned to work on, and whether or not they will reach out and talk to people (sales). We have some of our developers that will only work on certain projects (me included) and other ones who don't do sales (they only want to do code). Because the team is so small, it can be a real challenge.

There has to be a balance and we are trying to find and maintain that balance. It feels elusive and slippery at times. Steve was saying or relating what we do to an analogy of people sitting around the fire. Everybody likes the fire, but nobody wants to go out and get more firewood. He really wants to push harder on the sales side of things. Basically, it feels like we are a little bit heavy on the developer's side of things.

Towards the end, we were talking about the ability to take basic building blocks and stack them into small combo packages to get awesome outcomes. It's not that the smaller pieces are super cool, all by themselves, it is just, when they get stacked together, they really become something cool. Taking the basics and stacking them together. Steve is really trying hard to work on bringing in custom controls and dynamics to all of his projects. That is awesome.

Here are some other notes that I took during the meeting. I started out jotting things down on paper, but was getting behind, so I started typing things so that Steve could see where we were and what we had covered. These notes below are from the typed stuff.

- People's willingness to play in different industries - cannabis and non-cannabis

- Personalities and where they feel comfortable and want to spend their time - development (writing code) and sales (getting out, networking, pitching things, and talking to people)

- We may need to cut back dev and push more on sales

- Analogy of cutting firewood vs sitting by the fire

- Balance and being able to keep going

- Have cory focus on clients who want improvements and are willing to make investments - client funded projects

- Wasting money on sales meetings and emails campaigns

- People who are great at what they do but they can't do all of the things to keep the balance - This ends up being a vacuum or a money pit because we have to pay for all of the one-sided stuff

- In cannabis - we can get some of the new accounts, but it is hard to make someone switch

- We are up against a lot of money - big money investments

- We want to stay as small as possible and stay nimble

- Paying someone for sales - somewhat of a headhunter

- Steve would like to see 5-10 new systems per month

- 3rd party solutions - there is a need there and they do help us float down the river

- Maybe looking at pair programming

- Talking about trust levels

- Shari O. has been the back-up for server resets

- Help is only helping if they are helping - we can't hold up a drowning swimmer

- We have had some peace and quiet with letting some of our guys/gals go... We need to get back there

- On the MMLLC - some of our team is worried about liability

- A couple of phases - anybody who wants to stay, needs to jump on the wagon

- Minimum is at 1/10th of a percent

- Don't worry about all of the details

- Get those set who want to and then go forward with the others

- Sort of a faith-based venture - just start, if you don't like it, we'll buy it back (talking about the company restructure stuff - buying and selling percentages)

- We have enjoyed working with Dustin

- Bryan has been a great work horse

- Steve would like to check in with industrial supply places and see what we can do there - find a vertical and then service it

- Maybe try some email campaigns for some of these smaller verticals

- Trying to expose more and more of the system - fewer black boxes and make it available for everyone

- Getting to a stable location (lifestyle)

On a meeting with Steve and Cory. Talking about projects for Eric. Steve will be meeting with him today to go over projects and ideas for ownership in the adilas multi member LLC corporation. Light report on what Dustin is working on. Cory had a list of questions, and we spent some time going over those pieces and questions. Looking into a part look-up problem for a client. The problem ended up being a huge part number (lots of alpha/numeric and special characters) and whether or not it was being URL encoded for certain actions or functions. That little fix will take some more time and we could end up flipping things to an id look-up vs using the text-based searches that exist right now. It's only for a certain method, but it gets used 20+ times.

Spent some time with John looking into deep nested loops and sub filtering data. This is on the discount engine project. Lots of string manipulation and escaping certain strings and characters. Once again, rouge and random client data. It is a challenge to allow flexibility and still keep a level of control on what a user can enter into certain fields, lists, and values. All part of the game.

It was Steve's day off today, but he was still in there pushing on things. He was checking in and uploading new custom labels to data 16. After that, he and Dustin were going over some new CSS (display) changes for some of the pages. We helped Dusitn figure out some stuff with the CSS and data table switches. Cory and Shari O. were touching base on some small tech support issues. Eric joined and was reporting in on the driver license scanning project. He is looking into our code and comparing it to a 2D barcode library that he found on git hub.

Eric and I ended up talking about other API sockets and functionality. He was saying that he likes to categorize things as - must haves and nice to haves. I thought that it was a fun way of saying needs and wants. Good stuff. Spent the rest of the time working on emails.

Wayne, John, and I were on the server meeting. We checked in on data 5 and some of the server monitoring that the guys are doing. Our goal there is to glean insight and info on slow queries, huge usage patterns, and see where we could speed things up. After that, we were touching base on other projects and going over our semi-on-going list of server things.

Ideally, communication will improve as often things get done and changed and no one knows about it. Almost like certain information tidbits reside with single users or developers and no one else knows what is going on. Super common.

We also talked about getting Dustin involved more with the servers and helping John and Wayne out in that area. They would like to get him all setup and trained on some of the Docker stuff and start the training from there. I gave them a time Id number to track their time and efforts.

Emails and general to do list stuff. Looking up some balance sheet item and loan info. Recording notes from other meetings and helping Dustin out with his local coding environment.

The Tuesday morning sales meeting was going on this morning. Marisa and Chuck were both presenting and sharing. They were talking about the scheduling side of adilas and how that would be cool to keep building that out. See this link for some other ideas on both horizontal views and vertical views for scheduling and elements of time. That link also has access to a small 2.5 minute demo video showing elements of time and some custom work that we did for Beaver Mountain (ski area and their snowsports school lessons).

Chuck and Marisa were also reviewing some recent email campaigns for trailer dealerships. They were looking at stats and how many emails had been opened and viewed. They were also talking about other places to advertise and connect with business to business software people and clients. Just looking for ways to advertise what we have to offer.

After the meeting, Steve and I were briefly talking about ecommerce and how it is going to be super important that our clients can sell all of their products and services. This includes normal inventory items, different services, and time (bookings and appointments). They all need to be able to be sold from the same ecommerce interface. You can tell that some of that is really heating up and there is a demand out there for it.

Alan and Dustin joined the meeting and we were going over units of measure and a possible variable casting error. John chimed in and recommended an Adobe ColdFusion update that might fix the problem. They spent some time looking into that.

Working and testing the PO line item rounding and working with the recipe/build interface. Steve had some ideas earlier today and I was playing with those ideas. I also got on a meeting with Dustin and we tried to resolve some details with his local environment. Small work session.

Dustin had some questions on his local environment. We jumped on and tried to figure it out. It ended up being a database connection string problem. We got it fixed by texting Alan and his responses and prior documentation. It was dealing with a timezone issue with the connection between ColdFusion and MySQL. Daylight savings was just yesterday, that's why we ran into this issue on Dustin's local box. All of the production boxes are ok, it was just his local dev environment.

Steve and Dustin were going over some small tweaks and changes that were needed on a number of different pages. Little tiny bugs or display changes.

Steve and I spent some time going over an SBA loan agreement document and reading and signing things. 27 pages of legal tech stuff. We chatted about some plans, options, budgets, and really trying to be focused. We tend to get pulled in 50 million different directions and projects tend to take a while to get fully across the finish line. The value of having a single primary project and staying focused on that piece. that is huge. We even talked about having a virtual carrot out there for when we finish a certain project, then we could look into and plan the next one. Kinda like a young kid with board games. Imagine the mother or father saying something like - You may only have one game out at once. If you want a new one, you have to get the other one fully cleaned up and put away. Then you can get out a new one. Sadly, we are probably at that level... :)

Dustin joined the meeting and was checking in and asking about merging in his code. He also had a server 500 error on his local box. Cory, Chuck, and I were talking about parts and items and requested changes. Going over pros and cons of the new look and feel changes. Some people really like it and some people want it to be reverted back to the old way. Cory really wants to include our clients and get their help with testing (power clients) and feedback.

Most of our discussion are possibly leading towards more settings on display and functions. That seems to be the secret. We also talked about slowing down and taking more time to test, get feedback, let our clients know, etc. The discussion turned into talking more about settings and building out vertically or horizontally. Ideally, we will try to build out more stuff vertically vs horizontally. It just scales better going vertically. For example: We have a corp-wide settings table that has over 400+ settings. That makes that table huge (horizontally). We are actually trying to flip that and run everything vertically (variables value pair) and add new records for any new settings. Database tables are built to have millions and millions of records (vertically stacked records). We are heading that way, to lighten the load on some of the huge database tables.

We ended up talking about some of the new pages and even rolling things back and making it look nicer (going back to the old way). We tend to assume a lot vs getting real feedback. Sometimes those assumptions can really hurt you. Anyways, we were pitching some small proposals and ideas around.

Cory and I going over projects. Talking about some of the upcoming internally funded projects and budgets on those projects. Here is a small list of some of the things that we know are on the horizon.

Future Development & Projects
- Client facing scheduling – bike shuttle
- Global or enterprise item catalog
- Dustin's Cultivation & Harvest Stuff
- Invoice due date & auto collection on A/R's project(s)
- Labels & label printing - Calvin's tool(s)
- Compliance and SOC reports (SOC=service organization controls)
- Switching over to Lucee vs Adobe ColdFusion - potential $2,000/month saving – reoccurring - $24,000/year savings
- Our own project costing

We also talked about meetings and which ones are the most important. We would like to trim that down a bit as well. Trying to get schedules and timing all figured out.

I joined and they were doing a dealership sales meeting. Marisa was leading out. Talking about trailers, dealership stuff, custom paperwork, processes, and getting serialized (stock/units) into the system as part of a dealerships inventory.

After the sales meeting, Steve was doing some new settings and using some include files for a custom gram controller in the view cart top mini area. His goal is to get rid of a bunch of similar custom black box code. That is awesome. Black box code allows us to interject any code on any page to make it custom. However, if you end up making tons and tons of black boxes that are very similar, you can actually create more work and maintenance. Steve is starting to move into a great one-to-many relationship on some of the new code that he is building. That is a huge step.

When a developer starts out, they build a bunch of things that are coded specifically for one client or one purpose. That is easier to wrap your head around and each thing (function or feature) has its own part to play. Lots of simple things that basically stand alone. As their skills improve (developers), they start thinking more globally and start building in functions, methods, special includes, etc. Basically, code it once, use settings and defaults, and let the users configure what they want (make it more dynamic). Then the features become what is called "data based" vs "code based". It allows the application to flex without having to hardcode every option. The settings and defaults determine what it does and then you can reuse it over and over. Instead of copying and pasting code from others, you start building your own code with a purpose in mind. Huge steppingstones. Good stuff!

As a fun side note, As Steve builds this new code and stuff, he is actually able to delete thousands and thousands of lines of code to make it more simple and concise. Sometimes that really boots a developer's sense of being if they can get rid of extra code vs just adding and adding to something that is already huge. Great little mental battles and victories.

Dustin joined us on the meeting and wanted to go over some harvest functionality. He and Steve were talking about keeping up with master on the different code branches. Marisa wanted to see if Dustin could help be on a demo for cultivation stuff. Good little meeting.

Some of the guys were checking in. Looking at some code for Dustin. Tons of emails. Steve was talking with Danny about labels and options there. After that, Steve and Sean were talking sales and updates back and forth on what is going on. Lots of moving pieces. I pushed up some code for Dusin. Steve and Sean did another small session on talking about new settings, labels, and other updates.

Helping Dustin over GoToMeeting chase down some variables. Making a couple of changes and pushing up some new code. Looking into an error that Kelly sent over via email. Alan ended up responding back on that one. Emails and doing budgeting prep work. Looking over banks, accounts payable, and deposits. Recording notes from the past couple of days.

Tuesday morning sales meeting was going on when I joined. There were 8 people on the call. Danny and Chuck were going over leads for dealerships and other verticals. Talking about option and what we have to offer to dealerships. Somewhat of an open format or open forum. Lots of good suggestions and reminders of tools and features that have been developed over the years. Steve was saying a bunch of things that he knows were really important when he was doing that business (new and used vehicles and trailers). Working with dealerships was where we started, back in the day. The first 5-6 years of the system were spent doing a custom write-up for a multi-location used vehicle and new trailer dealership, out of both Colorado and Texas.

If we ever need, we have tons of older data from those older corporations. They were shut down in 2009 and 2010 in order to focus more on adilas. The automotive and trailer dealers were coming off of a huge recession from 2008 and 2009. Our software (web-based platform) was where we were focusing. There is some fun history there, as far as how things developed and why. It could be a really fun origins type story. Countless times of finding a source of pain and then coming up with one or more solutions to combat the pain.

After the sales meeting, I helped merge in some code for Dustin. We also talked about tons of code that is partially built and tested but not deployed. We call that either code on a shelf or half baked (or whatever percentage - 75%, 90%, 99% baked) projects. We've got a ton of that that we would like to harvest and get over the finish line. Tons of options there.

John had some state tax withholding and payroll questions. We looked over some code and got him going in a good direction. Wayne popped in for a server meeting and we chatted before the next meeting began.

Quick meeting with Dustin to get him going on his local box. He was running into an error. We got it fixed and he is on his way. He is almost done with his production samples project. He showed Steve and I a quick demo. He and Steve will be getting together later to discuss the next steps and other projects.

Steve and I were talking about breaking up projects into smaller and smaller pieces. This may not apply to everything, but we are really trying to take better bite sized pieces vs trying to stuff everything that you can into your mouth (not really - but an analogy). We are going to try to release code almost weekly or daily where possible. We may need to disable it or limit it, but we want it to be pushed into master when it can be. That helps us limit the amount that we build and then put on a shelf (virtually in a code repository). Baby steps or progress by degrees.

Steve and I also talked briefly about other plans and what not. He was going to be calling Kelly this morning to go over things with her. I ended up doing emails and light internal tech support with our developers. Small stuff.

Working with Dustin on his new samples and production samples pages and project. He was showing me where he was at and we were going through questions. We followed a bunch of variables and then spent some time going over JavaScript functions and suggestions. This project was scheduled to be pushed before the end of the week for testing but that got pushed back a week. Making progress and it is looking good.

Dustin and I on a small work session. He had some questions and we worked through a number of changes and improvements. I spent some time explaining and diagraming (drawing and making connections) the sub inventory process and what data and tables are connected and how they are pulled together and related (database stuff and backend logic and relationships). Anyways, lots of drawing and small code samples.

Cory and I going over plans for the bike shuttle (client facing scheduling app) project. We were meeting over her Zoom account so that we wouldn't be distracted and get interrupted. Sometimes, everybody knows that we are on the main GoToMeeting session, and it doesn't allow us to fully get things done - too many distractions and/or other parties on the line. Anyways, we thought that we could use Chuck, Dustin, Bryan, and I on the client facing scheduling app and tying it out into full ecommerce as well. Lots of work with elements of time. All we need is some seed monies to get it going. We have someone who has committed $500 but that is not enough to jump yet. We know that it would sell and bring in an ROI (return on investment) but we have to be careful right now (cash flow stuff).

Two different phone calls. One with Steve and one with Danny. On the phone with Steve for about 45 minutes. Making plans and talking about possible options. The other call was with Danny for about half an hour. We talked about some of the industries that we deal with and options and personalities of different people that we work with and/or have dealings with. Danny is looking to change things up a bit and doesn't want to work with the cannabis clients. He would also like to turn the custom labels over to John or Steve or Dustin, if possible.

As Danny and I were talking - he mentioned a story about a kid who wanted to be good at a sport but wasn't into doing weights (lifting weights) in the off season. As the guy grew up, he saw the benefit of spending time in the weight room. Anyways, the story goes on to talk about how sometimes we can't see what is going on at the time. Instead of a weight room, he was saying that God puts us in the "wait room" (patience, spending time, and hopefully learning while we wait). Sometimes we can't see the advantage of the "wait room" until later on. I liked the story, good stuff.

Meeting with Dustin and Cory. Dustin was reporting in on his samples and production samples project. He wanted to know what was next, as well. We spent some time and talked about options. After that, Cory and I spent some time looking into expense/receipts and monies being paid out.

Dustin joined us and gave Cory and a I an update on his project for production samples. It is getting closer but still not finished yet. We ended up talking and doing some training on dynamic variables and looping over structures or objects. Trying to help him get the skills that he needs without recoding the whole thing.

Quick meeting with Dustin and Cory to go over progress. Dustin was reporting in on his sample package stuff for production and cultivation companies. After that, Cory and I switched gears and talked about projects and other developers and their projects. I also spent some time recording notes from earlier today.

Bryan and I working together. Light review on some finances and where things are at, inside of adilas, payables, receivables, banks, etc. Switched over to his multiple credit card readers and devices project. Good back and forth on what we have and what is still needed.

After Bryan and I's meeting, I went in and did some checking on some questions that Dustin had sent over dealing with JavaScript files, CSS stuff, and general questions.

Reporting on progress, both John and Cory were touching base about projects, hang-ups, and break throughs. Talking about bugs and getting fixes put in place. A lot of John's time has been spent working on bugs, fires, and server issues. He and Wayne have done a great job!

We got into a discussion and were talking about other services that we offer and want to offer. We need to put together a fun price list type flyer of what we offer. This could be core adilas, consulting, design, project managements, custom code, dedicated servers, and other client care services. We also briefly talked about how that pricing structure would look. We will get the sales and marketing folks involved as well, just kicking around ideas.

Finished up the timeslot by doing a small merge and push of some new code for a project that Dustin had finished.

Back on the reoccurring expense/receipts and schedule tasks rewrite. Got in to it and then got pulled out again, due to other requests and tasks. Merged in some code for Dustin. Phone call update with Steve. We were talking about new changes, updates, and upcoming projects. We also talked about getting Chuck going on the internal shopping cart as his next project. After I hung up with Steve, I was trying to get things prepped and ready to get Chuck going on that new cart project. Lots of bouncing here and there and trying to pull together some of the pieces. We've been wanting to do this for years and years. We are going to start tracking progress on that project using time id # 1561 inside of adilas.

Dustin joined us and gave Cory, Steve, and I a report. John was still on the meeting as well. He, John, was helping both Dustin and Steve get some of their mappings and local development environments setup and operating more smoothly. Along those same lines, there are always challenges with server updates and trying to make sure that everything keeps working together.

After the other guys left, just Cory and I were left on the meeting. We looked into a small issue with units of measure and the stored sort values. We are going to make a global change on that section and see if it helps. Cory and I also spent some time talking about other adilas team members. Each one brings a different skill set and flavor to the mix. That is good.

Emails, light research, and listening in on the morning meeting. Steve and Dustin were going over some new requirements and changes from Metrc bulletins and announcements (state requirements). The other guys joined for the daily standup meeting. They are getting close to wrapping things up for the enterprise units of measure and enterprise part category projects. They should be done with the current sprint by tomorrow. Just light clean-up left.

Going over the year end payroll project and needs. We did some light review, listed out some tasks, and even went into files and looked around. Lots of review and good little work session. John took some notes and I did as well. Towards the end of the session, John and I chatted a little bit about the new scrum and agile development stuff. We talked about the need of a middle level programmer (someone who understands both frontend and backend code and likes to play in that role). We also talked about lessons learned thus far and where we think things are going. We also want to get Dustin some help so that he can get some of his big projects finished up and out the door (deployed onto live servers and being used).

Meeting with Dustin and Cory. Dustin was showing us some of his production settings and new code for dealing with samples and special packaging. Lots of new stuff dealing with jQuery, Ajax, and lots of local custom JavaScript. His page is a nice one-pager with some helper files off to the side. Pretty cool.

As part of the meeting, Dustin was showing us some of his stuff and I asked him to give Cory and I a deeper tour on how he was using some of the technologies. I think that it was good and turned into a small teaching and education session.

Cory asked Dustin what he has left on the project and even lightly was leading him to start thinking about options of scrum or small teams helping to finish out the remaining pieces. Good stuff.

Steve and Sean were touching base and chatting about some sales, new updates, and some options. Dustin, Wayne, and some other joined and checked in as well. We had a bunch of other guys join for the daily stand-up meeting. Alan ran that part of the process. We had Alan, Bryan, Chuck, John, Wayne, Steve, Sean, Dustin, and myself on the meeting. I was mostly just listening, but I heard some good reports. Chuck showed some stuff, Bryan showed some stuff, Wayne showed some stuff, and Alan showed some stuff. I didn't know everything that they were talking about, but I was impressed with the coordination and communication that was going on. Good stuff.

Towards the end, Alan was asking Wayne some deeper questions on models, services, DAO's (database access objects), and mock testing stuff. Object oriented deeper conversations. It seems like it is going well.

There were 11 of us on the GoToMeeting session this morning. We started out and some of the guys had some questions from yesterday's meetings. We answered a few things and some of the guys chatted and asked each other some questions. Alan joined the meeting around 9:30 and then we turned it into a virtual stand-up meeting (daily scrum meeting). Each of the guys took a turn. I was only able to stay until about 10 am and then I had to jump on another meeting.

Here is who was on the meeting this morning. Bryan, Cory, Steve, Alan, Chuck, Dustin, Eric, John, Sean, Wayne, and myself (Brandon).

Bryan had some questions about the database, plans, tables, columns, etc. Chuck showed us some small mock-up pages. He asked for some feedback and got some quick answers. John was working on some prototypes and asked for help from both Wayne and Alan. Towards the end, Alan was reporting on what he was doing and working on. I wish I could have stayed to see what else they chatted about, but I was impressed. Hopefully more good things to come.

Steve, Danny, Dustin, John, Sean, and I were on the meeting. We merged in some code for Danny. John was checking on the auto deploy from master on the servers. Dustin gave us some code through chat for the servers and how the database handles the group by clauses. Steve and Sean were going over some custom data uploads. Small work session.

Dustin was checking in with Cory and I. They were going over some smaller pieces and doing some follow-ups. Dustin is currently working on some samples and sample packaging code. Sample, in the cultivation and production area are very common. They need to be tracked and monitored, but they aren't really like real inventory (kinda a mix).

Dustin was going over some layout options and changes that he is planning for the sample packaging build section. Lots of crazy gymnastics for the different test types and API socket data (state by state) that we get back. It makes it hard to program things with all of the dynamics.

Cory is going to reach out to clients and see if she can get requirements and screenshots of what the clients are looking for. It is so helpful that she is willing and able to coordinate research and customer needs.

As they were talking about things, the topic switched to sub attributes (child inventory and child or sub attributes) and how deep they needed to go in the new process. Showing and hiding the attributes when needed and making sure that they are there at other times. Pretty dynamic process.

Light talk about code repositories and using bit bucket. Cory was asking for more communication and keeping us posted on changes, timelines, problems, and launch dates. We aren't done yet, but Dustin was asking about the next steps and next projects.

After Dustin left, Cory and I were chatting about clients and some of their needs. Some of our clients are very demanding.

Having fun talking about history and progression. Dustin and Wayne were swapping stories and even talking about fun old games that they used to play. Lots of learning along the way. Interesting to see how far things have come.

Talking about current servers and monitoring CPU spikes and loads. Checking logs and scripts. Both Wayne and John are doing awesome with the servers. Wayne reported in on converting Application.cfm (in-line or line by line code) pages to Application.cfc (components, methods, and functions - much more versatile). Cory was asking about timelines for projects.

Wayne and John have a new testing environment almost fully setup to help our developers out. That is really cool! We are putting John in charge of the developer box. He can reach out to Wayne as needed. Some of our plan is to keep making it up as we go... :)

Talking about redundancy in the databases and some cool stuff that is coming down the pipeline. Talking about being able to switch out databases, datasources (pointer to the database), and even having multiple datasources and databases per server. At one point, we were calling that project world building or the datasource project.

John was reporting in on the adilas phones project. Cory and Wayne were chiming in. They were coordinating efforts and communication stuff.

Lots of guys on the meeting. Steve and John were talking about servers and a small outage last night. It didn't look like any malicious. They were also talking about how many changes happen month over month. It gets pretty crazy. That is both good and bad. Good, in that we are pushing the ball forward. Bad, in that the landscape is constantly changing and even altering flavors and flow. All part of the game.

After that, I got to show Steve what I was working on for one of his clients. Sean reported that they had a good demo yesterday and the client is going to come on to the system. Steve and Dustin where talking about the cultivation pages and section and what else is needed. Fun to see the progress.

Some of the guys were talking about the whole progress, over years and years. Code, Internet connections, needs, etc. Fun little trip down memory lane.

Merging in some files for Dustin. Looking into some new time settings that are needed to automate internal recipe/build actions. Light clean-up on some existing pages for time settings. On a quick GoToMeeting session with Chuck to go over the parts homepage and the differences between parent and child inventory items. We did some drawing and came up with a plan. These new changes don't exist yet, but will be coming on a facelift on the main parts or general inventory items homepage.

Phone call with Alan to follow-up on the ecommerce new cart model project that he has been working on for transitional invoices. He gave me a report and I relayed it over to Cory. I left her a voicemail message and she called me back. We are going to keep watching this project as it has somewhat lost some traction and needs to be pushed across the finish line. I talked with Alan and we'll try to push on it together to help get it done. Deep waters and lots of moving pieces. We've been stuck in black box land (custom code) as well as fringe or outlying cases dealing with recalculating taxes, with tax included, and rolling discounts into the mix after a valid login or customer assignment. Still doing some testing.

Back on the time settings for Steve. He is trying to get the projects and I'm trying to work on them to get them done. We are trying to tag team.

On the morning meeting. Steve and I finished up from an earlier meeting. Danny, Sean, and John popped on to check in. Mostly a small work session where everybody was on mute working in the background.

Dustin popped in to show Steve some new features on the cultivation and samples pages. Lots of new JavaScript and AJAX type stuff. Nice demo and it is looking good. We asked Dustin to organize a small training class for us on AJAX, jQuery, and JavaScript - mixing those pieces.

Emails and text messages as the other guys were working together.

Small data fix for Shari O. on un-posting an expense/receipt inside of adilas. Posting is kinda like a final lock-down. There are no tools to un-post something currently. I was asked to check on a data dump for Euflora and added a number of parent attributes to the custom data dump file. Pushed the file up live. I also merged in a file for Dustin, pushed it live, and sent him an email with some suggestions on some of the logic.

Danny was on the meeting this morning and asking about a possible mini training session per month. He was calling it a monthly deep dive, where we could pick a topic or section and do some training on that. We could let our clients know, our internal team know, and then go from there. Great idea. He was also talking about an idea for a feedback form and page for monitoring what our users and clients are wanting and needed.

Dustin, Sean, and Kelly were chiming in. Working on emails and other small to do list things. I unpacked a new events banner from Marisa. It looks great. It has a QR code and a web address on it. It also has the adilas logo and some other graphics including Adi (the blue dog avatar) on the banner. It will be used when we help with other events, such as the Bear 100 and other races, events, or whatever.

Quite a few of us on the server meeting this morning. I had a small list to go over with Wayne and we started there. My list was:

- The new Emerald Fields server and custom database

- Training for John - that is going great and we are very happy there

- Talking about the developer's server and making it more into a testing environment as needed - a server that is in total flex - lots of great ideas and conversation here

- Corp-wide settings and carving up the bigger tables. We also got into talking about switching between Application.cfm (current) and Application.cfc (where we are headed). Wayne and John are going to be looking deeper and working on this in the next couple of weeks.

- We need access to some Adobe XD files that we put on the content server. They exist, but we can't download them via a direct URL currently.

- More great talks about the testing and developer's server

- We would like to setup a meeting with Russell, Chuck, John, and others to go over Bootstrap 3, 4, and 5 - We would also like to look at options for other data tables that we may want to use. When we do this, we will eventually want to let Dustin, Bryan, Alan, Eric, and Steve know about decisions and direction.

- John reported to Cory on the adilas phones product and progress there

- John went over some of the discount engine stuff and showed us some of his new plans - light question and answer session between John and Cory

Good meeting and making progress. Good stuff.

Steve was working on a database update for some new corp-wide settings for PO names and recipe/build names. We looked at his code and made a few changes. We then went on and talked about the growing need for super high enterprise or global level product and item catalogs. It seems to be more and more needed, yet it is still out there a little ways.

Steve and I chatted about some funding options and then I pitched some ideas to Steve about the data assembly line concepts. Lots of small little drawings. We are actually doing it, building towards the full data assembly line concepts, but we just haven't really made that our focus. Dustin has already added a phase base process for cultivation. Steve is currently working on some production phases, and we have other projects that have similar flavors. The absolute ideal would be to allow our clients the ability to setup and run their own business processes and let them (our users or our clients) setup the phases, sub locations, options, flow, defaults, timing, etc. of these processes and procedures. That would be really cool!

When I got on, Steve had some questions about time templates and making some of them hidden and not allowing users to interact with them. I thought that was interesting, as when we were developing time templates, that there were needs back in 2010 and first part of 2011 where we wanted to build system monitors and system time templates and not let the users interact with them and/or change anything on them. Originally, that was one of the reasons for thinking up some of the templates in the first place. We talked about possible solutions and using the time template status to help control - active, inactive, and hidden templates. The hidden ones would or could end up being the system controlled templates. They would exist, but we could limit them from being edited, updated, and even viewed from time to time. Lots of options.

The other day,  Shannon and I were thinking about permissions and settings and it felt like there was a third piece to that mix. I couldn't put my finger on it. I'm wondering if it has something to do with a mix between the two and dealing with templates, of all kinds, not just time templates. A template is somewhat of possible mix between permissions and settings. Technically, you could have user-defined templates, system templates, time templates, invoice templates, user templates, location templates, corporation templates, etc. The list could go on and on. The templates allows for an interesting mix and also playing more in bulk vs single or standalone permissions and settings. Anyways, just a thought.

Danny, Dustin, and John were on the meeting as well. Each one checked in on what they were doing. Dustin will be out of pocket during the month of September, he was just letting us know (family and travel plans). Also, just wanted to record this - "family first" - super common phrase that comes out of Steve's mouth. Good stuff. In the end, that's what really matters.

Towards the end of the meeting, I was explaining to those on the meeting what Shannon and I are working on and how we are comparing the game changer of the video recorder to what Adilas is doing on the same business recording type level. I gave them some examples and we chatted about some ideas. Tons of potential.

We talked about how the video recorder went through a whole process and series of adaptations to go from big, huge, super expensive, exclusive, and had to have special equipment, budgets, and connections to being handheld, on a phone, in almost every hand (literally) and even cool inventions like the GoPro and how small, mobile, shockproof, waterproof, etc. It has become accepted and readily available. It really is and was a major game changer. Adilas is following a similar path in what we are trying to do and record and make accepted and available our business recordings. It (adilas) is the business recording device, without having to use 6-10 different software packages and then trying to marry things together in a huge mash-up type model.

This, adilas platform and dynamic app, is a fully integrated and fully functioning system - system being the keyword. End to end, the whole digital story. I can't tell you how many times we have said, wouldn't it be cool if we could play the virtual story (movie) backwards or forward and could stop, pause, or replay certain happenings. We don't have the data quite that flowy (aggregated and rolled up summaries and counts) yet but it is getting better and better. Think of the kind of data and business intel (BI - business intelligence) we will be able to get and show as we keep going forward. Once again, end to end, the full digital story! Backwards and forwards! Super cool!

Dustin - How to show an elephant? You show a picture of it and then break it down. We were looking over some research and Adobe XD documents from Jonathan Wells and talking about getting those prototypes, visuals, and mock-up's out to the public. Good stuff. Lots of work there still to do. Show people and the world what is possible. Adilas is a huge, working, fully functional prototype. We would love for people to take the time to really see what we are doing and working on. The trick is how do you do that? Make people slow down and/or take notice of what is going on. Lots to offer!

Cory popped on the morning meeting and had a few requests - things for us to look at. We merged some code for Danny and got it pushed up. Dustin wanted us to check some new code and push it up to a server as well. Steve and Dustin jumped on and talked about some of their processes and how they are somewhat sanitizing things. They are changing some of the names so that they are more generic vs strictly tied to certain industries.

Steve and I chatted about some loan documents and Steve gave me a couple of tasks to do to help with the process.

John had some code to check in as well. We worked together to make some changes to payroll verbage and added some file path changes. There was a new file called payroll summary report. We ended up changing it to pre-payroll summary report and flipped links, verbage, and what not to match. It really is meant for pre-payroll vs actual payroll. Good change.

Sean joined the meeting and reported on what he is working on. He and Cory are working behind the scenes to clean-up a company's records to help them get started with a clean slate. Sort of a manual clean-up process of getting rid of old packages. Danny checked in and had a small question on a query for some labels. After that, Eric joined and had some questions on some new expense types, background logic, and new changes dealing with his sales tax aggregates and mapping them into expense/receipts for paying down the sales tax liabilities. Lastly, Dustin joined the meeting and needed some new code to be checked and merged in. He has been doing a series of updates to the Metrc and cultivation and packaging stuff. Pushed up new files to all servers. Other than those things, I was doing emails and going through things if no one else needed my help for anything.

Emails and text messages. Pushing up a few more changes for Dustin.

Emails and merging and pushing up some new code changes for Dustin. He has been working on a number of small fixes lately.

Cory joined and had a number of questions on payroll. We talked and went over a few of her questions and tech support requests. An error was reported from a guy who was trying to run semi-monthly and it was missing some of the hourly calcs. It seems to be a special case where the calculate payroll page doesn't open the timecard range enough to take into account the full date range (things called memo hours or hours in other weeks that need to be calculated but not included for overtime, because they were on a different week). Randomly enough, this same user reported a similar problem almost a year ago and we couldn't find it. Anyways, almost a year later and it happened again. There must be some special case where it only happens under certain circumstances. All of his other ones have gone through just fine. We'll have to look deeper. We have some info on the corporation, the server, the users (payee id numbers), the date ranges, and other settings that we didn't have last time. That may help us find it.

Cory was also showing both John and I an issue with the auto midnight rollover for employees on graveyard shifts that start on one day, rollover the magic midnight hour, and clock out sometime the next day. We've been able to do that for years. We recently added in some new payroll timecard flags and that seems to be the place that the process is struggling with. We will have to do some testing to figure it out. Looks like a small bug or oversight. The new code is forcing the flag to needs manual attention, even if nothing is wrong. Anyways, we'll check it out and see what it is missing.

After that, Dustin and Cory were going over settings, and changes in Metrc API sockets and endpoints. Metrc is literally a moving target (Metrc is a state compliance system).

While they were talking and going over things, I was starting to look into the midnight auto rollover issue for the timeclocks. Once Cory and Dustin were finished, Cory asked if she could help. We talked about getting a dedicated developer to help with payroll, withholdings, new yearly forms, and other updates and expansions in the payroll area. John expressed some interest to be that developer, along with some of his other responsibilities. We spent some time talking with John on what would be needed, expected, and some general advice and guidelines. We are going to give it a go and I'll work with him to get him fully oriented in that area.

Steve, Danny, and Sean were talking about sales, directions, and breakthroughs. John checked in and had some files to merge and push up to servers. Just some template changes. Dustin and Steve were talking about production phases and next steps. Eric checked in and had some questions on expenses and special math for the balance sheet for his aggregate sales tax stuff. I'm glad that he is taking that project to the next steps. In the process, he is getting deeper and deeper into some of the financial logic and background processes. That is exciting.

Tons of emails and other small to do list things.

Work session between Shannon and I. Brainstorming on adilas core concepts. See attached for where we were working (word doc). Also, we were basing some of our discussion and efforts off of an older adilas formula flyer that shows business functions, application players, and adilas core concepts.

By way of a break through today, we decided that the adilas core concepts have two main categories and underlying groupings. Here are the 12 core concepts:

1. Capture & Record The Story
2. Groups, Players, Individuals, & Characters
3. Relationships
4. Trouble, Problems, Needs, & Goals
5. Decisions & Choices
6. Consequences (Cause & Effects)
7. Accountability
8. Permissions & Settings
9. Systems
10. Vision & Future Developments
11. Tech, Tools, & Maintenance
12. Objects & Data Over Time

The two main categories are: 1 - Elements of digital storytelling (numbers 1-6) and 2 -  How we adapt the digital environment (cloud/web) to track and record that story that is playing out (numbers 7-12). This is new for us and we were excited to see that there was a new classification within the adilas core concepts.

Like anything else, it is still kinda in flux and we don't know exactly what we have and what to do, but we are trying to refine things and boil things down. This is part of creating new content and verbage for the adilas system. Fun! We had a good session. Once again, if you want to see our raw notes, see the attached word document.

Also, we were thinking that number 1 (capture & record the story) was actually kinda like the end result - what we are aiming for or trying to get to.

We also felt like number 12 (objects & data over time) was actually how we enable the flow of the story to take place. The wording may be slightly different, but those are the concepts. Lots of interweaving pieces and give and take that goes on. Part of a living, breathing, system. Welcome to adilas!

At the end of the session, I did merge in some new code for Dustin as well.

Steve and Sean were on the morning meeting this morning when I joined. They were talking about creating SOP (standard operating procedures) for some of our clients. We have a bunch of companies that have made up their own, we may be able to piggy back and use some of those ideas and concepts to create a list of our own. They were talking about using those as part of the sales tools and package type approach. Interesting and lots of good ideas.

Dustin joined the meeting and he and Steve looked at some new code that Dustin is working on. He already has tons of settings for the cultivation stuff that he has been working on. He showed Steve some new settings and they went through a number of scenarios. Looking good and more options to allow the companies to control the flow and verbage of the different pieces. Once they can control those pieces, they tend to settle down a bit. Once they aren't fighting the flow and verbage, the rest of the process seems to fall into place. That seems to be a big key.

Steve had some questions about Git and the code repository. We got him all hooked up and going. In the background, I was downloading documentation for Paypod project that we are going to be working on (cash management - and bill/note and coin recyclers). Light review of each piece that I was downloading.

Steve and Dustin were talking about sub attributes and using smaller getters and setters to modify data as needed. We talked about different level of coding - in-line, using methods, and using dynamic getters and setters. We would like to use the getters and setters where possible. The more dynamic we can make it, the better off we will be. Code once and then use many. They were also talking about more settings on top of what is currently hardcoded for some of the verbage. It is so important that these companies speak their own language. It makes a huge difference.

Eric joined and checked in on the USAePay and EMV chip reader stuff. We are making progress, but there are many parties that seem to be involved. Steve and Eric were talking about adilas jumping in and being more of a middle man and actually pitching and selling some of the merchant processing pieces. We talked about some options and making some plans as we move forward. Part of our plan will be to provide a super robust and fully integrated system and payment solution. We have a bunch that work, but nothing that we are actively behind and trying to sell as our recommended solution.

John and I checked in and merged in a small branch of code dealing with his payroll and timecard projects. Small tweaks. We also setup another meeting time for later today to get into the new timecard logic a little bit deeper.

Cory joined the meeting and had some tech support questions. We looked into some small changes and requests that were wanted.

Dustin was checking in on the morning meeting. In the background, I was migrating 10K timecard records per click and updating them with new timecard flags and total times per time card. Helped Danny fix an internal email issue. We had to add in a global find and replace line of code to help it interpret the code correctly. After that, I logged into all of the servers and synced up some of the globally shared tables with new web page id's and API settings.

Small note on the things that we need to sync up - the value of using a last date modified field to help only update and sync what is needed. Some of these sync procedures were thousands and thousands of records, when only a couple of hundred may have changes (or less). If we had a last date modified field on some of those tables, the lift would be smaller and I could limit data syncs between servers to just things that had changed, based on a date or date range. The end goal would be to make a lighter light of these global server syncs and procedures.

Merged in some files for Dustin and pushed them up to all servers.

Eric and Steve were chatting about changes in the little town of Salida, CO. The world in which we live keeps changing. Some good, some bad, some better, some for the worst. Interesting!

Eric was reporting back to Steve and I about the EMV chip reading project for USAePay and possible conflicts with First Data. Our current integration works in most cases, but it fails if First Data doesn't send back the correct response on every transaction. We are expecting a certain format and response, but it doesn't always come back as we hope and planned for. That is causing an issue. We told Eric to keep tracking things down and let's move this project to the next level. We do want a good and solid integration and if we need to, we may have to flip the backend chip reader processor. Anyways, Eric will keep following leads and try to get some meetings setup to help figure out a good business choice.

Switching back to the sales tax aggregates and sales tax aggregate project. We (Eric and I) talked about a small to do list, future plans, data drill-downs, use cases, scenarios, activation process, event scheduling, and removing limits on other corporations. Eric is circling back around on that project and even has scheduled some future meetings to go over next steps and details. I was giving Eric permission to run with the project and be the senior dev or senior lead on it. We also got into talking about new expense types and planning a course of action there as well.

Dustin checked in. Danny check in and had questions about using adilas as a media/content library for email template assets. We talked about using an element of time, and uploading needed media/content (files, images, prep stuff, etc.) for all others to use. We went over a few other ideas and Danny will be running with that or those pieces. Good meeting!

Guys checking in. Dustin launched some new stuff yesterday and was looking for some feedback. They did some live testing with one of the biggest clients and had good reports. Merging in some code for John for some new social media icons out in ecommerce. A couple new ecommerce settings. Sean was checking on security and privacy and wanted to know if we had anything in writing. I pointed him to a couple of places. See attached for a security PDF and a Q&A about the adilas database and other security type questions.

Merged in some more asynchronous page loading for Dustin on his cultivation homepage.

Back working on elements of time and new time template page settings. Lots of new master time template settings and values. Also went over some usage for the new settings. I'm recording all of the info inside of an Excel spreadsheet.

Watching some new mini YouTube videos that Danny and Marisa were working on. John was sharing some new client leads from a gun shop. Merged in code for Eric. Merged in code for Dustin and had to fix some merge conflicts. Just busy to do list stuff.

A bunch of the guys were on the meeting this morning. There was Sean, Danny, John, Dustin, Steve, and myself (Brandon). Steve and I were working on some string manipulation stuff. This is where you take a string (notes or alphanumeric data of any sort), find sequences and then do certain actions based on those findings. After we made some progress we switched gears and got into some sales type talks and discussions. Danny had some great questions and was asking the group for some feedback. Sean presented some sales outlines that he was working on.

I ended up grabbing the screen and pitching some ideas and doing some drawings. We talked about how adilas is a great companion software package for any business, regardless of what else you have. We can fill in the gaps or be the whole solution. We are able to play at all of those levels. I gave my 3 point elevator pitch and explained it a little bit. The 3 points are: 1. Adilas is a high-end software as a service type product (SaaS) - meaning web based software solution. 2. We cover anything dealing with operations and accounting - very broad but still direct enough. and 3. We have a standard package (the software application or site) and then we are able to customize on top of that.

We got into a small discussion on selling what you have, even if it is not fully finished. I showed some of the guys my old LTF (learn to freeride - snowboarding interactive product and multi-media app). I told them that I got the whole thing done and then tried to sell it. A marketing guy had us repackage it, go to some trade shows, and then we ran out of money before we could really push it all the way. I still have some older products and pieces at my house, under my stairs. I related this to selling adilas and even the concept of what we are trying to do. Steve has been great on that and has landed client after client, even if all of the pieces weren't done.

By way of a history, the adilas corporation id is in the 20's and all of the earlier corporation numbers either already existed or wanted in even through things were just barely functional back in 2008. We started in 2001-2002 but didn't officially become adilas until 2008. Prior to that, it was called the Morning Star System and was a custom write up software package for Steve's used car dealerships and trailer dealerships. If you want more info, here is a couple pages of a brief history document (pdf).

It takes all of us. No one person could tackle the adilas monster. It literally takes all of us. Whether it is ideas, coding, tech support, sales, development, maintenance, servers, etc. It takes all of us. Be your own style. You will fit in and be a great part of the adilas team! We love it!

Towards the end, Steve and I were lightly pitching some vision and where we are headed as well. Fun little session for those who were on the meeting. Good stuff.

Merging in code for Dustin and his bulk batch functionality for cultivation pages. Talking about ways of speeding up the deployment process and getting new clients and customers (corporations) up and going quicker and quicker. New systems and doing data imports. We talked about ways of getting things setup quickly and being more and more efficient. We then moved into QR codes and what they can and should do. We went a little deeper on this topic and went over some known uses of QR codes.

We then started talking about projects for Bryan. We would love him to start working on flex attributes for elements of time (in-line database extensions for time and time templates). We also talked about getting Bryan to help clean up the shelf (existing code that hasn't been fully tied in). We know we have projects like sales tax version 5 (v5) project, invoice due date project, and many others.

Steve and Cory were talking about inventory forecasting and usage pages. Watching and monitoring supply and demand of items and such. Inventory planning type functions and options.

Towards the end of the discussion, Steve and Cory were talking about independent reps and consultants and some pros and cons. We have had great results in the past, however, things are changing and we are on purpose trying to bring things more internally to provide those services from inside of adilas. This is a conscious effort. We will continue to work with a few select individuals, but all new accounts will be helped and supported from internal resources. That's the plan.

We had six or seven guys on the morning meeting. Dustin and Steve were touching base on the bulk batch options for the cultivation homepage. Dustin was reporting on some of the changes and asynchronous querying that he is working on. Making progress, just not quite finished yet. They were also talking about new pages, options, and settings for a general nursery (growing different plants and trees) type flow and options. It is amazing how many new settings need to play into each industry and/or vertical. We have some similar things, but even that would need to be tweaked a little bit.

After that, we had Steve checking in with John on servers, me checking in with John on the payroll and timecard project, Danny checking in with Steve and Sean on some sales stuff, Steve asking me about some inventory planning (future supply and demand stuff), and other small meetings. Eventually, we all just ended up working on our own things and projects. 

Recording notes. Also working with Eric on testing and pushing some code for his cross-corp loyalty point stuff. Lots of back and forth with Eric, pushing up test code and running it live on a production server through a temp scratch file type approach. Also merged in some code for Dustin.

Quick meeting with Bryan on query params. We made some plans and touched base.

Dustin joined the meeting and he and I spent the rest of the time testing and doing some error handling on some of the code that he is working on. Lots of testing, validation, and soft error handling (easy roll over options). Good work session. We pushed up some new code.

There were a bunch of guys and gals checking in. Kinda fun, Cory was on the meeting and coordinating with the developers. We had some guys jumping on certain bugs, and others working on other things. It felt pretty cool and we got a few things done and pushed up. I was working on a corporation stats issue. We used to have two corp stats methods (functions to get corp stats). The new code broke up one of the stats methods into a third corp stat function. The error was dealing with exceeding the size of a possible function or method. We got it all fixed. Dustin and John were working on another small bug. Good work session.

Lots of guys checking in. John M. checked in on his payroll project. Dustin was showing and talking about AJAX stuff on his new cultivation pages. AJAX stands for Asynchronous JavaScript and XML (asynchronous data going back and forth). The new AJAX stuff helps with quick loading of pages and data. Dustin was looking into an error  message from Metrc. Sean checked in on the SAR custom gun registration stuff. Steve was talking with the guys and checking in on server speeds and stats.

Steve and Dustin were talking about companies growing and dealing with load times and more and more data. Part of the game. Steve and Dustin were then talking about allowing the user to control what loads first, second, third, etc. This is part of what we want to do for fracture - allowing settings and presets to show what needs to load first, second, etc. Help the customers get their data quickly and in the correct order. What is your flow?

Small bug fixes with Dustin. Pushed up new files and code.

Scanning receipts and helping to merge in some code from Dustin and his bulk cultivation tools. First round.

Danny, Dustin, Sean, and I on the meeting this morning. They were talking about a small mini mobile app for push notifications. Danny was asking Dustin about his experience with mobile apps. After that, Danny and Sean were working together on some other pieces. When I wasn't needed, I was recording some notes from other meetings.

Dustin and Cory joined the meeting. We were looking into Dustin's new cultivation and batch process actions. He showed us some small bugs and enhancements that he is working on. We talked about some possible strategies and he took some notes. It is looking good and we should be within a few days of getting the current version launched and pushed up live. That is exciting!

As a fun side note, Dustin made his local environment look really cool with a custom dark theme on the look and feel. It looked very professional and fun. Throughout the meeting, Cory and I would ask questions and Dustin would respond. Some great back and forth with ideas, flow, and user experience stuff. Once again, looking great. Some of the things were form on the top, bottom, how much to scroll, filters, flow, show/hide buttons, verbage changes, etc.

We want to keep things at a minimal but still make it fully functional (as far as what is currently done) without rolling into weeks and weeks of more development. Kinda putting a temporary cap on things to get them up and going, instead of creating the never ending feature creep type scenario.

One interesting takeaways from our meeting was the concept of creating a dynamic, user controlled, environment that allows for data to be started, gathered, structured, categorized, and a full end-to-end process all through settings and automation. Basically, it was the concepts of the data assembly line and a user controlled (dynamic) data assembly line. Phases, locations, moves, bulk functions, printing labels, batches and batch controls, removals, new items, etc. All in one place and flowing towards an end goal. Pretty cool.

The last thing that was brought up was how recipe/builds could help in manufacturing and production systems. It could be pretty cool.

Cory joined the meeting and was checking on some server errors that happened over the weekend. John was able to reply and respond to some of them. I helped where I could as well. Some of them are random and when and how they happen. No new changes were made to the code, but sometimes it is like it gets overwhelmed and/or can't find itself or gets buried with requests or something. Kinda random.

I tried checking on a query param error but was unable to find it. I spent a good half an hour. The client that reported it, was unable to duplicate it again either. Cory is going to notify the client that we looked but were unable to find any problems. If the error occurs again, we will try to duplicate it and look deeper. Otherwise you are virtually hunting for needles in haystacks.

Steve and Cory did a small session working on ecommerce and auto logins for clients. They got into app icons, preset client variables, auto login links, and other email options. We also talked about being able to expose some of the pieces, like email functionality, to our clients that they may not even know about. It's like the really cool functionality gets buried or requires a deep dive to make it surface or be in front of them.

I have a meeting later today with Dustin. Steve wants me to help him get his current code pushed up to the servers and merged in with master. Sometimes projects and code take so long that it becomes really hard to merge them back into the master branch. Everything has a shelf life of sorts.

Lastly, we talked about getting some of the new SOP's (standard operating procedures) up and into the adilas docs section. From everything to setting up new corporations, to configuring ecommerce settings, to how to log a perspective client. Good stuff. We are making progress and trying to get everything into a centralized and usable format. 

Dustin and Sean checked in. Small chit chat and then they bailed out to work on their projects. I was doing emails and recording notes.

Dustin was checking in on his bulk move by batch number project. Sean checked in as well. After checking in, they both bailed out to work on their own projects. I spent the rest of the time reading some new whitepapers from Steve McNew on different subjects. Merged in some custom labels for Danny.

On Friday, June 11th, 2021 we had an internal conference day for just the adilas team. We went from sales to internal code to ideas and plans. All over the place. See attached for my notes. Many great things were discusses. Once again, this was an internal team meeting, but we don't mind sharing what we were talking about. :)

//////

The attached notes are better formatted, but I wanted to push some of them here for searchability:

//////

Group Sales Meeting

Marisa, Danny, John, Cory, Sean, Steve, Dustin, Shari O., Dawn, Brendan, Steve (mac), Brandon, Chuck, Alan, Kelly, Bryan

- Kelly was saying that there is some public records per states

- We may try to pull our own list

- Questions... who, what, where, how good, etc.

- Maybe look at a sample of 10

- We may need a more focuses approach

- What about different industries?

- We need to get the name out there

- Kelly was pitching a social presence

- Do we know anybody who wants to do the social stuff

- Word of mouth

- Testimonials

- Some new video graphics

- To the penny, to the gram, every day

- What about small streaming commercials – focused and pointed

- Kelly recommends that we maybe focus on a slightly larger pool

- Dawn – maybe focus on start-ups or that small to medium range

- Get them at the beginning – maybe even tradeshows

- It is a pain in the but to switch over – pain creates options for change

- Focus on services... deployment, oversight, consulting, training, best practices

- How can we deploy something easily and repeatable?

- It is tough to get some of the people started, but once they get all in, they tend to stay

- Kelly has done this over and over again

- Using the professional resources that are available

- From Kelly – Help get the clients all the way in – full system and platform

- Getting the success on the first implementation and then building from there

- What about focusing on those who are having trouble and/or are struggling

- Dawn loves the support, training, and feel good part of it – duplicate that feeling to others

- How quick can we respond – we jump pretty quickly on custom needs, development, training, and support

- Get more testimonials from our clients

- We have some experience to offer to those who want it

- What about pitching best business practices

- It's ok to be non-traditional

- Being Relevant!

- Focus on helping over sales – from Steve (mac)

- Simple things that bring the relevant pieces

- Social webbing – group effort

- Danny, straight up, I don't want to be the social media guy! We have to find the right person and/or persons (small little team)

- We are not QuickBooks... what does that mean? Be our own style!

- Packaging this platform based on the target audience

- Formulating a plan – ease the lift – maybe a monthly meeting with some planning

- Influencers and YouTube options

- Small info tips...

- New age marketing – we have to play to the current market

- Big Dumb Animal Pictures – super simple

- We have to do a cost analysis to see which one(s) make more sense for us

- John, what if we setup our own little social piece (aka maybe the adilas cafe) – we could allow all of our users and power users to pitch and promote – we may need to approve things, but we have tons of very knowledgeable people and users

- We are looking for engagement – back and forth – a relationship – maybe get an intern to help handle this

- Danny – Switching over to the modal message marketing

- How to save the app to your phone

- Make the email piece better

- Small web tool to help with building special html links to embed promotions, direct add to cart, discounts, campaigns, etc. A simple form to help with the backend tech of those URL's and web links.

- Maybe, we need to upgrade our email platform. It is a small holdover from years gone by.

- What about the delay on the outbound emails?

- Marisa – maybe outsource things as needed

- Steve – would like more input on the bulk tools

- Better filtering and target marketing

- Steve wants to work direct with Dawn and Branden

- Matrix and target marketing – even predictive

- Maybe a little itty bitty (super small) native app on the different phones – iOS, Android, etc.

- Steve wants to get into possible predictive marketing

- Steve – looking for great feedback and even ideas and dreams...

- Archiving, saving for later, dismissing, etc. We have the data, what do we want to do with it? – Wet clay...

- Danny – Going back to past clients

- Version 1 vs Version 2 – type attitude

- What kind of clients do we want? We may not want certain kind of clients.

- We love people who like details and are willing to play

- We love people who take things to the fullest level

- We love people who just need a small little piece – there is a gap in their current model and they need some help. We can then grow from there.

- Do a full comparison of what we offer

- Pitch what we do differently – we help deploy and maintain your ERP

- White glove approach

- Playing with the tools that we have and flipping those into marketing messages

- Chuck – maybe check out some groups on Facebook

- Blog posts, articles, info snippets, quick videos

- Talking with Kelly – how have we helped small businesses become bigger or big business – showing the potential – dreams to reality

- The small goals to achieve – steps to get to the next level

- Small goals lead to bigger goals – getting some small successes along the way

- Clients and expectations – not all money is the same – budgeting and planning – what kind of client do we want

- Reoccurring revenue vs one-time revenue

- A quote is just one of many pieces that needs to be done

- People, skills, and cogs in the wheel

- We all care... where would you and your skills fit in best

- Seeing the bigger picture

- Maybe looking at personalities and figuring out the mixing and blending of our options and resources

- Slowing down and taking the time to see where we are at? Virtual time travel – child, youth, adult – as a company

- What's the difference between a goal and dream? A plan!

- The internal group summary that we did... a great start

///////////////////////////////////////

Second session - Servers & Infrastructure - Refining Our Processes - Tech Support & Training - Project Management

Steve wants us to show the online label builder

- We had some good talk about where we want to go

- We pointed to our internal summary report

- Steve McNew – helping with the strategic marketing plan, technology road map, timelines to position, plans for action

- Scale – can we grow and can we shrink

- Conversation between big and small – perspective – big and small (sales, number of team members, lines of code, etc.)

- Molly – Is adilas the big guy or the small guy? Think of code (lines of code). We could be considered a big guy if you were looking at code and functionality.

- We like being small (ish), but what if we are big already

- If we want to grow, that means that we want to get better – grow in a good manner and sustainable manner

- The underlying services that support the whole

- Be your own style!

- Steve McNew – old classmate with Steve Berkenkotter – guest speaker – part of the adilas team to help us get some things more standardized – processes and procedures

- Defense contractor for the military – 28 years

- Testing, software, management, auditor

- He has already called, interviewed, and talked with a number of different team members

- He did a 20 page audit and report on what he was seeing

- Getting into some testing and processes – he would like to see more of this

- Not trying to derail the train – we are trying to polish the Ferrari (spelling – awesome car)

- Whitepapers – catering to a higher audience – going beyond stick figures and into technical docs – not everybody will want to read some of these, but there will be some that require it

- Steve B – if we try to sell our product to those who can't afford it, it doesn't really work. They have to be able to pay for what we do (really do – billing for our time and efforts)

- Fin-tech – financial technology

- Using whitepapers as part of our marketing plan

- John M – unit testing – confidence of the developer team – currently only Wayne and Alan are doing this (unit testing)

- Going to ease into this – refining our testing plan

- Version control and when do we update these systems? The older way was wild west... we may want to figure out some specific micro builds.

- It would be nice to keep track of the versions and options.

- The balance between core and custom development

- The application needs some spring cleaning – what is being used, what isn't, what is going slow, etc. – Refactoring

- Priorities – customer priorities or our internal priorities – what is the mix and blend of these pieces

- We all ware many hats... we may need to define that so that we don't overstretch ourselves

- We all use (and can use) the system in different ways – how do we translate that information to our clients, other developers, and other team members (upstream and downstream)

- 2 minute videos – no more

- Work instructions – even giving it to someone who has never done anything in the system

- Danny – Shoutout to Steve and Brandon – we have done great – what is coming next? Resources?

- Talks about earn and burn ratios

- Prices have to match the services

- We are a growing business

- Kelly – going from 1.5 to 10 (millions) – that is a huge change

- We are competing with companies that are hugely funded... what do we want to do?

- There are some real things in our path – there is tons of potential – what do we want to do with it – also, sometimes there is shelf life on potential or advantages

- We don't want debt – however, there is a time for debt – cost analysis and being smart about it

- Making choices, but also being willing to fail

- Marisa – look at our new website

- Steve – there are some percentages of adilas that are available – not looking for vulture capital (just being silly – vulture vs venture)

- Someone looking to take on some risk but helping us to get to the next level, without taking over the company

- Kelly – pitching our vision and business plan – we have to define the vision – Danny seconded the define the vision before looking for the funding – goals, sales, budgeting, maintenance, and getting a business plan.

- Adilas Trust option – co-founders

- Possible option – Maybe take some of IP (intellectual property) and sell that to a new entity and then restructure those new pieces

- Dustin – thoughts on corporate structure – we are all on our own little islands – Ferrari to a tricycle – frontend compared to backend – splitting up those pieces and functions – he wishes that we could be more collaborated.

- John – teams and buddy projects – small sub teams – full stack (all levels) vs specific skills or somewhat limited skills – this needs to be part of our plan.

- Sean – we already have some small teams that are working on some of these projects – cogs of the wheel – buddy tagging the workflow and processes

- John – the adilas docs project – and being able to go to it and also add to it – working on standardizing the pieces – filling in the gaps

- Danny – Navy Seals – two is one, and one is none – at least two on a project – two-by-two

- Kelly – scale – having a back-up

- Danny – accountability back and forth

- John – confidence levels

- Kelly – what about a succession plan?

- John and Dustin – real life buddies and how they help out each other – seeing a different angle or perspective

- Marisa – tooooooooo much weight gets put on single persons

- Kelly – relieving pressure and helping with scale

- Marisa – Cory, Kelly, and Marisa – wonderful training slides, presentation, and delivery for the conference. Awesome job!

- Alan – modularize things – able to be reused – code concepts can relate to business functions – one to many relationships – translating knowledge into real life and different scenarios

- Chuck – last summer Chuck was on a joint project with he, Russell, and a different John. It worked out awesome – Keep pushing towards that kind of rollout of the project

- Molly – thinking and coming up with ideas. Keep it going!

/////////////////////////////////////////////

Next Session - Deployment & Oversight - Design & Layout - Internal Core Development - Custom Development 

- Deployment – where are we going and how can we make this all work – team effort

- Shari O. – first touch and setup corp, Sean and Shay first hour or so, Sean helping to coordinate the next steps and pieces

- Sean does a great job of reporting back

- Report on things, record the notes, get back with us to help us keep pushing

- Doing great with testing and prototyping

- Kelly – who is on settings, who is on planning, maybe even looking at pre-deployment options

- Before Kelly even does a demo, do some consultation – figure some things out without doing any pitching or selling. This is called listening.

- What are you looking for, wanting, expecting, hoping for?

- Make the demos custom to the pain points or key wants and needs

- The prep work is huge to help them be successful

- This platform is not a turn on and go type system – there may be pre demo, consulting, custom planning and demo, then custom hand holding to get them going down the road

- Picking the point of contact... who is going to own this thing?

- Owners, managers, and users

- Users want the easy button – Steve calls this the tail wagging the dog vs the dog wagging the tail – what is and how can we get buy in?

- Tools are great, but solutions to problems and pain points are even better

- Give to get! If you give too much, it can get you into trouble.

- What is the cost to fixing things... on the other hand, failing does help with major learning – there has to be a balance

- We tend to remember pain – setting people up for success

- Often users are looking for a quick switch. This system takes work. Please sell it that way.

- Not going to custom too quickly – learning the manual way – then automating it

- User buy in – light pain and then helping them learn a better way

- Change proposals and scope of work – setting up boundaries

- Feature creep – setting that scope of work – cause and effect of what they want and what they give – expectations and timelines

- Sometimes I start with NO – interesting

- A saying no - sandwich... Yes, I'd like to, no, I can't. Yes, I would love to help do this... - people think that no is a bad word

- Having a plan to say yes, vs just saying yes

- We like to please people – that is awesome – what does that cost?

- Help make the plan to say yes. Maybe, no (first), however we could do this...

- Making things repeatable

- What are the internal costs to do deployment?

- Say $350 for a setup fee – does that cover it? If yes, great. If no, where does that put us?

- Maybe on the setup, prep, an activation fee (define this – turning on the lights), setup and deployment fee (range), training, custom code, imports, labels, etc.

- We like to cater to everyone – that had bitten us

- Actual prices and then use discounts if needed. You can't really ever raise a price after the fact.

- Back-up our prices

- Use adilas to run adilas!!! This is our communication tool, let's use it.

- We are good at the dreaming and software building part of things, we need some major loving on the service side

- There is demand!

- What pulls at our time - It is time, money, skills, etc.

- Kelly – earn has to be more than burn

- Flipping the demand to sales or services that could be provided

- MVP – minimal viable product, plan, player, etc.

- Intangibles

/////////////////////////////////////////////////////

Next Session – Show and tell! What are you working on?

Calvin – Advanced file and folder finder, resize images, convert images

Brandon – harvesting assets from element of time

Steve – parent attributes report, items not on a recipe (manufacturing), modal message marketing for customers, log notes for vendors and employees (payee/vendor logs), backorders homepage, mini units, auto add item (quick PO behind the scenes), bulk update on the vendor – master copy paster... :)

- Branch 122 – fun

Bryan – cfqueryparams – stop SQL XSS (database hacks – cross site scripting)  - SQL injection – converting from dynamic queries to secure dynamic queries - Example: Corp_id = #Trim(some form or URL var)# or Corp_id = <cfqueryparam etc, etc,> - this stops the SQL hacks

Bryan is also working on eChecks for eXPO, Hypur checkout in the shopping cart (eComm), new API's for delivery (with documentation and samples)

John – Payroll project to allow holiday date picking, timecard flags, timecard totals (pre summing the math to go faster and lead towards bulk payroll), new timecard reports showing grouped sums and totals.

Page templates and style guide defaults with Chuck – Going from old school tables and links to the newer grid and mobile ready code. Part of the adilas docs project. Build once, use many (effective copy and paste). Basic templates (3 new ones). New information icons and popups (modals). Style guides and usage of those pieces.

Servers with Wayne

Chuck – Huge new web site!!! Awesome Job!!!

Global Design Dashboard, adilas docs, and new presentation gallery (sales tool).

Danny – message marketing, custom labels, sales team meetings – hats off to all of us! Keep listening and keep finding solutions. Open table – follow your highest excitement and be yourself! Be happy!

Alan – enterprise level catalogs, refactoring code (custom page settings), standardizing code for speed and reliability.

Random comments – Cory really liked having access to all of the team members, right here at the conference. Marisa – great to meet everyone – keep floating the boat. Sean – he likes the team. Molly – loved watching and wants to be involved. Chuck – idea of everyone joining slack

A few of the guys checked in and what not. Danny and Steve were working on parent attributes. Helping Dustin with some JavaScript popup windows and such. The rest of the session was a mini work session and recording notes.

Meeting with Dustin and Cory. Dustin has been helping John and Chuck and acting as a consultant for the new templates and style guides. Dustin was showing us some of his new code and changes for the cultivation pages. He is working on bulk actions for batches. Cool new layouts and flow on his bulk tools. We eventually got into managing popups, windows, and handling sub routines.

I did a little demo on how we used to use special popup windows for stock/units and different configuration builders. I showed Dustin some of the existing code and showed him how it looks and works. He has a need for similar functionality. Lots of high-end JavaScript and AJAX stuff.

Dustin and Cory were talking through questions and using a virtual sounding board for flow and options. After that, Cory showed Dustin that they have more testing and certification stuff with Metrc for other states. Dustin wants to stay on his current project dealing with the bulk actions for batches inside of the cultivation process. Let's keep him going where he has momentum.

John and Cory were on this meeting. John was reporting and going over the payroll project and how deep it gets. John has been working with Chuck and Dustin on some code templates and style guides. There is a mixing between frontend designers and backend developers. That is great and I encouraged that. Cory and John were commenting on different things and going back and forth a bit. Good dialog.

Our clients really like the ability to change whatever they want, inside the interface. This could be colors, look and feel, logos, watermarks, navigation, menus, verbage, etc. It gets pretty deep. Some people don't like dealing with change. We talked about the old icon menus (hidden menus under the more options buttons) and the new look and feel for the more options links and buttons. Pros and cons to making the changes. The old way was more in your face with buttons, lots of white space, mini screenshots for icons vs a more subtle way to get to the menus with simple graphic icons and a more sleek and stylized feel.

We talked about creating more work for other people by making changes. Sometimes we just look at what we want to do vs thinking about those who help and support our clients. If we just change something, it has cascading effects to clients, staff, and others who help provide support and compliance. It trickles down pretty fast.

We talked about other client expectations and helping our users move into more modern ways of seeing, filtering, and exporting their data to CSV and Excel files.

Shannon and I talking about info graphics and what we want and what we can virtually harvest (stuff that is already done and virtually laying on the ground). We also talked about how cool it would be to show the flow of financials and how different things interact with the system and what pieces do what. Think of a visual tour of what does what. Those would be some super cool info graphics.

Pushing up some code for Dustin.

Chuck and I started out our meeting talking about paper post-it notes and also magnetic erasable post-it notes. We were just having fun. Chuck is doing some research on web site and using a thing called a mega menu and bigger menu options with icons, pictures, and small amounts of text vs just a simple link or simple menu.

We talked about the adilas docs project and getting people over there and into the docs - using those defaults and standards (code snippets and templates). Often we are heads down, doing the same thing, over and over again. We need to pause and lift up our heads and learn and apply some of the new things.

Chuck is planning on doing some training for our team and wants to put together a crash course on the bootstrap grid system. This will help us as we add classes inside of our code to make it look more modern and mobile friendly. The deeper we get and the further we go, mobile development and mobile friendly sites are becoming more and more important. Basically, mobile first - type development.

John is helping Chuck with some default pages and templates. Chuck wants to help do some training to help Steve, Russell, Dustin, and myself with the frontend development pieces. Trying to help out and get us all onboard.

The adilas docs are a living project - things keep changing and what not. Chuck is willing to do some training. We will just keep chipping away at this huge monster. As new training is created, we will record it and make it available for other developers. Chuck used to have fun with a thing at the college where he worked. They would call it a 1 hour lunch and learn or mini lecture. Fun ways of doing some training.

Pushing up the CSV upload page for Steve. Helping Dustin out with a database update. This was one of Dustin's first database update that he wrote by himself. Good stuff.

Met up with Cory and Dustin to get an update on the cultivation project. Dustin is in the process of adding in a whole new section for processing plant on a batch level. The new page will have bulk actions such as move, phase, print, remove, and harvest. Good strides and looking good. See attached for a small screenshot of Dustin's local development box.

We tend to build with the details first and then circling back around to get the quicker or bulk type moves. If you can do it the long way around, you hopefully can then shorten it up and still have all of the pieces in place. Once you know where you are going, you can speed things up.

At the end of the meeting, Dustin bailed out and Cory and kept talking about other projects and other developers that we would like to take certain projects. Good meeting.

Dustin and I met and repushed up some code and did some code management stuff. After that, we got into one of his new reports and did some new queries, coding, and working through some advanced (multi relationship) logic. We did some deeper query, grouping, and looping training. Good session.

Merged some more code for Dustin. Reading through the questionnaire summaries from the internal questionnaire. Light edits and saving it out as a PDF. On the phone with Eric talking about other strategy options.

Merged in some code for Dustin. Some of the other guys checked in. Pretty casual. Then started working with Eric on his sales tax aggregation project. 

Guys checking in. Dustin gave us a small report on the bulk processes for batches and cultivation. We merged in a couple of small changes. Eric reported on the USAePay EMV chip reader stuff and where that project is at. It has been released and we are kinda waiting on a client. We may end up making a few little tweaks. After that, Steve and Eric talked about help files, popup modal windows, and showing more info and page help. John then reported on his payroll and holiday chooser project.

Sean, Steve, and I met with Dustin to go over some bulk move and bulk update options for his cultivation stuff. We are making plans to  use the counts to divert the clients to a bulk update process verses the traditional rendering of all information. We met with Dustin, pitched a couple of ideas, drew out some sample scenarios, and made a few plans. Everybody on the call was chiming in and all on the same page. Good meeting.

The general goal is to watch the counts, and do one of two things to help with the rendering of data. One, if the count is high, prompt and filter the records (even allowing multiple batch filters at a single time). The other option is to break the next step into slightly smaller pieces (counts per batch - within the returning record set). This would limit the amount of processing and still allow users and clients to view counts, quantities, batches, and be able to still drill-down to full details if needed. Kinda like an intermediate step where we show the groups within the data before we show the details. Both techniques will help a ton!

As a recap - group it, count it, break it down into smaller groups within the bigger group, and finally go to full details

Great meeting with Dustin and the gang. Dustin gave us a report on some of the cultivation projects that he is working on. He has three major projects that he is working on. They are: harvest packaging, bulk adjustments homepage, and a super cool one called accountability homepage. See attached for more details and notes. Great meeting.

3/23/21: Dustin will make cultivation API changes for OR

Working with Shannon on the internal summaries for the questionnaire. We have already written them, we are just proofreading and making sure that everything reads well. See attached for progress. After working with Shannon, I merged in some code for Dustin and pushed up some files.

Touching base with some of the guys on their projects. Small code review with Dustin. Pushed up some new changes. Quite a few of the guys had questions for Steve today. They were going over new features and asking questions about accounting. While they were doing that, I was recording notes and such.

There were a bunch of guys on the meeting this morning. All of them were checking in and what not. As they were talking with Steve, I was doing emails and listening in. Dustin popped in and showed us a new tool that he is working on. It helps to randomize certain numbers for one of the processes that he is working on. The randomization has a editable variation factor that you could plug into the mix. Pretty cool.

Helped Steve out with some email testing and what not.

4/14/21: 1550

3/2/2021: Dustin will add this in to help with speeding up harvest.

Touching base with Danny on things. John and Dustin joined the meeting and we went over some of the new tables that they are wanting to add for the cultivation project. Going over scenarios and use cases.

discuss table design for an aggregated data table for cultivation.

Merged code in for Dustin. Pushed up new code. Meeting with Steve, Dustin, John, and I to go over cultivation generation 4 (Gen 4) level changes. I took a bunch of notes and put them on a separate page. See attached for some of the notes.

2/15/21: Project for John, Steve and Dustin