-Get Steve and Danny on Git.

- We need to add Sub notes and comments Searchable by the quick search options. Maybe expand to all subs of time.

Online team meeting to cover security, adilas API sockets, black box code, and upcoming white label options. We started out with a number of reports by the different guys.

/////////////////// here are some of the quick reports by the developers:

- Eric - Fixing custom carts and working on the pricing engines. Lots of custom one-off's. Working on loyalty points and special tracking accounts.

- Russell - News and updates - new API socket feeds and such. WordPress site and other look and feel things.

- Wayne - Refactoring code, testing based design, and underlying framework. QuickBooks integration stuff - imports and exports. As a side note, Bryan has had many customers asking about similar type features. Wayne is also working on other database stuff and migration.

- Bryan - White label stuff for outside parties. Tons of custom projects.

- Calvin - Hybrid API to Windows desktop app. Custom PDF labels and printing.

- Alan - Helping Steve with Metrc API stuff. Working on tons of tax and in-line discounts. Helping Brandon with other projects.

- Danny - Generating sales - Props to the developers who are creating the functionality. He pitches the idea that the developers are accessible. Custom labels.

- Shawn - Helping with payroll, federal withholdings, state withholdings, and county level withholdings.

- Brandon - Helping the developers and doing small projects. Merging code and maintenance stuff.

- Steve - Grateful for the help with the Metrc API stuff. Working on phases and sub locations. Steering the ship. New approval levels on other state traceability systems.

//////////////////// meeting notes:

- Talking about the Adilas API and system - dealing with security. Facebook was brought before the senate due to a breach. They allowed an outside company to come in and develop an app for Facebook (basically a 3rd party solution). The problem was... what does that outside service actually do and have access to? The app ended up doing some internal data mining and then sold that data.

- We want our users to be successful - we want to enable them but we also need to protect them.

- Small switch in the sales focus. The older model was one-by-one and dealing with reps and consultants. We are seeing more of a switch to bigger companies that virtually take over the sales force and are wanting to sell our product more as a white label type application. Lots of mixing and blending of products and services. They are allowed to provide all of the supporting services that support our product.

- Ideas from the group about security:

- Russell said, bold it or make it red and let them know what they are exposing (meaning the API sockets). Allow the agreements between the parties... we are part of it, but we let them create the relationships between themselves.

- Steve said, we don't want to make our users work harder... to turn things on, but we do want to make sure that the clients know what they are getting in to. Example of what happened with back in 2015 with Hypur and Emerald Fields (two of our clients). Basically, the 3rd party solution (Hypur) got turned on and then it kept growing (what Hypur was doing and/or requiring) and eventually was trying to get at more sensitive sales and inventory level stuff. Eventually the client was super upset due to the lack of disclosure of what was going on and what was open/available to the outside party.

- We are seeing that most of these 3rd parties and white label people tend to expand what they are asking for. Bryan is seeing that more and more auditing type levels are wanted by these 3rd parties. We have also had a number of questions about different server levels and certifications. Our clients want to make sure that their data is safe and secure.

- Russell brought up the point and the difference between a couple of if statements on a page vs a full on white label type solution. We need to develop and standardize that white label type path. They need to pay for it and also be able to help maintain it (meaning the white label company). Taking things clear out to a white label theme (actual files and folders). White labeling is basically bulk black boxing but you can still use any of the classic pieces. We drew some small diagrams and talked about possible options.

- Shawn chimed in and started talking about building a city. Basically, kinda like urban sprawl or older parts of a bigger city - no plan, no alleys, buildings touch other buildings, and not a well planned layout.

- We need to stay on top of things. Keeping code and the database structure up to date. If we do this... it will help us be more efficient and save us time.

- Eric chimed in and said "process" is the solution vs simple communication only. Basically, as we are growing, we need to get to a more standardized process of development. We have a huge landscape to consider. Lots of moving pieces. Ultimately we need to adopt a process oriented approach. Wayne agrees. Different levels within software development. From critical and saving lives to making sure that we have solid code and pieces. It gets into speed and flexibility against slow and more stable type processes. Maturity in software development is sometimes measured in how well you implement internal processes. Eric thinks this is the next step we need to take as a company.

- Danny has been threatened... :) He was talking about levels that people rely on our solution and how all of that plays in and such.

- Small little analogy of the little red hen... everybody wants it but they may or may not want to participate. In real life, things cost money and take time to get done.

- From Brandon - Let's make this thing what we want it to be!

- Any core elements need to be merged into the master branch. This is required.

- Steve was saying... be on the lookout for companies and what they are wanting. That could help us know how to play with them... Maybe look deeper than the current project. We really need to protect our client's data. He was talking about the adilas market (adilas world) and also the 3rd party solutions page. We need to point outside parties to come through the main monitored pathways. We need to keep those sections updated and let the clients know what is being opened/exposed. Very important.

- The value of oversight and/or having someone to help watch them and help them out. This seems to be new trend. If that is the case, we need to make sure that they know what is going on and what is opened and what is closed (talking about data).

- Brandon will write up some super basic pieces of what our current rules and processes are.

- Alan pitched the idea... Local, live, and then into production - talking about a testing server that will be coming this year.

We ended the meeting and allowed people to jump off the meeting. We basically said we would be doing this again (meaning a team meeting) and would get them some info and instructions.

/////////////////////// after the meeting

- Alan and Steve were talking about breaking up code into logical pieces and making the road map more object oriented. Basically, organizing the use and flow of data - making the map for others to follow. Currently, we are just using Brandon's memory to help guide people to the right spot. We need a better road map that others can follow.

- They got into some technical conversations about threads, processes, RAM memory, read/write times, etc.

- Part of our process needs to be setting up and monitoring the servers (actual eyes and reports or dashboards). We need more information, stats, what pages are being used, what processes are running, and what data is being accessed and how often?

- We talked about caching, traffic, threads, database transactions, data mining, and changing from transactional data to more of an aggregated type model (summing up things and organizing things for reporting features). We need to keep allowing day to day operations but also need to optimize things for reports, exports, and other bulk reporting features.

- Alan and Steve were talking about the challenges of using outside API's and syncing up data between systems. Lots of options, but also lots of moving pieces.

- On the API sockets... We need to provide good samples of how to call things and also good response type data. It is really nice if we can format things as well. It just makes it easier for our guys and also outside developers.

9009 E Arapahoe Road, Greenwood Village, CO 80112
Phone: (303) 799-4555

See attached for notes, scans, files, and GoToMeeting recordings (videos)

--------------------------------------

Day 1

We did some intros and then got started. Danny Shuford did a demo and did a great job. See attached for some notes. Here are a couple of the highlights from what I took away from it.

- Solution for solution minded people

- It can be molded to fit your industry

- Changes keep happening

- Big open view of the whole system - it wasn't made for just one industry

- Brief overview of the framework

- Based on user permissions and valid logins

- All web-based and cloud-based

- Features and benefits - focusing on the benefits

- CRM - log notes, additional contacts, photos, and other media

- We all deal with money, but in the end... we are all dealing with people

- Note to me... Danny went into the customer table and doing the custom page settings on the customer fields. This is for things like the name, aliases, sort value, show/hide, etc. We really need to keep pushing that idea and concept forward. People really want that level of control. It just takes a ton of work to cascade that through the full system.

- He talked about news and updates

- "Our Interface" - what do you want? We don't have a single set interface, we let you choose

- Customer queue

- Lots of moving parts

- Drea - "Adilas is play dough"

- Inventory tracking

- Reporting and building your own reports

- Labels and changes to the requirements

- ecommerce

- Payroll

- Accounts payable and accounts receivable

- Print checks

- emails

- Customize and working with the developers

- Security and back-ups

- Steve - Showing some hidden gems

- Small demo on flex grid

Next, I gave a small section on the adilas model - core concepts - and intro to world building. I will upload my outline. I'm also hoping to upload the video as well. I don't have any notes because I was the presenter, but here is my rough outline:

- We will be bouncing around

- Start with a guy holding tons of stuff

- Talk about the needs and how to organize things

- Go over different tools... head and mind, paper and pencil, word processing, spreadsheets, databases, software packages, web or hosted solutions

- Go over systems and how things start to inter-relate

- Cover the 12 main players

- Cover the 12 business functions

- Cover the 12 main world building concepts

- Mix and blend to get the desired results

After lunch, Alan Williams did a presentation on highlighting and exploring new features. He started out with a fun group activity and a game of sorts. Minimal communication and we had to figure out a path through a virtual mine (bomb) field. It ended up having forward steps, side steps, back steps, etc. We eventually, as a group, got through the mine field. Really fun exercise and it opened up some conversations. Here are some notes from Alan's presentation:

- Little active - mine field - group activity - finding their way

- How does this relate to the adilas process?

- He then showed some of the steps that we have taken to build the application

- Side steps, back steps, and forward steps

- Going into advanced add to cart and sub functions

- Request from the group - no standalone discounts - Make that a permission and/or a setting. Standalone discounts can and do cause tax problems.

Next, Steve Berkenkotter lead an open Q & A section. The first question was asking about any updates with the Metrc (state compliance and tracking system for Colorado). That got pretty deep but exposed some of the challenges that exist between connecting and maintaining dual systems (adilas and Metrc). Here are a few notes:

- Questions on Metrc

- Some new tables and new limits from Metrc

- Auto processors - running nightly stuff to help sync data between systems

- API and server to server connections

- Challenges that exist

- Mixing old and new functionality

- Transfers

- Sales

- Using elements of time to track states, status, phases, and groupings

- Getting back at the data - reporting

- High level vision

- Question from Pat - 280E - new tax and accounting rules - what can we write off as cost of goods? What about unitizing expenses?

- Steve - How the IRS is looking at things and expecting things

- Steve - loves numbers and how he brings his skills to the table

- Work in progress - attributing a value as part of the accounting

- The progression of building and breaking

- The system is able to store the data (huge piece of the puzzle)

- The system may be customized to get the data back out and/or to get the data in (another huge piece of the puzzle)

- Template building

- A consultant spending time and configuring a system before it is released to the end users

- Small questions on CSS and changing certain page colors

The last section of the day was a presentation on historical stepping stones - what have we learned and why do we do what we do? I did this presentation so I will add my outline. Once again, we are hoping to get some videos uploaded to this element of time incase someone wants to watch the videos. Here was my outline:

- Where did we start? Spreadsheets, static web sites, zip disks and sending inventory around from place to place

- Fixing current business problems

- Where is your pain? Start there

- Letting operations lead - Use the adilas interactive map to help show flow

- At some point, accounting will need to follow

- Checkpoints and flowing data

- Gap between operations and accounting - drawing the gap, horses and carts, and old school T accounts - light history of accounting

- How does time play into the mix

- Comparing operations and accounting in a static environment

- Comparing operations and accounting in a dynamic environment

- Progression - drawings of the data assembly line and how it ended up at a 3D data assembly line

- 3D world building - x=time, y=resources, z=space or depth - draw out the box or cube

- Black boxes & white label options

- The whole deal

We didn't quite make it all the way through the whole outline, but we covered a good portion of it. Towards the end, we went around the room and got some feedback. Those documents and notes will also be uploaded. The final request from the class was to have adilas allow the "adilas version" spreadsheet to be shared with the world. It was originally created in order to get a bank loan, but Steve said to release it to the world. Great meeting and good energy on day 1. Good stuff.

--------------------------------------

Day 2

We spent most of the day working on and going over inventory tracking and point of sale (POS) features. See the attached videos. We also had some great demos from Calvin Chipman on building custom labels and one from Dustin Siegel on some new code and features that help with plant phases and cultivation. Here are a couple of notes from some of their presentations. For a more complete version, you may need to watch some of the videos from day 2.

- Calvin and the adilas label wizard - He gave a slide show and then started to interact with the label builder. After he was done, we asked him to show some of the behind the scenes pieces of his label builder. Good stuff.

- Vaporware - the product doesn't fully exist (yet) - part concept, part actual, not yet fully functional

- User designs the label (step 1)

- User selects the label from inside of adilas (step 2)

- The label(s) are created and displayed on the fly, based on stored instructions, mappings, and special code. (step 3)

- Part of the demo was showing sheet labels with a data merge, labels with barcodes and QR codes, static text, dynamic text (user can interact and change things), data mappings, graphics, etc. Pretty cool.

- Small talk about PDF's, Flash, & HTML and CSS - printing options from the web - Our choice is PDF currently

- Interacting with printers, browsers, and other hardware pieces

- PDF - actual size vs shrink to fit size

- Questions about font point size and possible limitations for compliance reasons - We will leave that up to the users, that way we don't have to chase all of the compliance rules and regulations.

- We talked about settings and maybe limits that could be stored and looked up on the fly.

- Possible template options

- Be careful saying a compliant label

- A good disclaimer to keep things legal according to the local and/or state requirements - put the liability back on the companies and/or users.

- Small story of a company and internal programming wars and war stories - Different places that Calvin has worked.

- It may take a hybrid solution of both software and web

- Small demo of the actual builder - Calvin is going to be taking that and putting it more into a wizard-type format. Currently, you have to be pretty techy to use it. Round 1 - prototype.

Dustin gave a presentation on some new cultivation processes and some dynamic mapping. We had some technology issues, the demo was going slow (Internet) but the concepts were awesome. Imagine going from a manual one-by-one process, to a bulk streamlined process. Huge time saver, plus tons more data points, capturing the whole story clear down to minutes, seconds, locations, phases, etc. Pretty cool.

--------------------------------------

Day 3

Busy day today. We got into sub inventory, why we do sub inventory, customer relationships, elements of time, flex grid, ecommerce, custom emails, group mass texting (GMext Pro), and a presentation by Kelly Whyman (super power user from the Denver area). We are going to be posting the videos and the notes from the day. Good sessions. Here are some of the notes that I took while others were presenting. Once again, see the attached media/content files for videos and other digital notes.

These are some notes from Shari O.'s presentation on CRM functionality

- CRM - The real acronym stands for Customer Relationship Management - Shari O.'s acronym for CRM is - Can't Remember Much - pretty funny

- Good data in = good data out - Fill things out completely and make sure you get good data in

- The client log and how to use it

- Leaving personal footprints in the sand - using the log

- Addin gin a user-maintained history... internal communication

- Cover you own rear-end

- Being business appropriate - have good manners when recording details and data points

- Custom emails

Drea did a demo on how to show/hide transfer packages inside of the adilas/Metrc inventory pages. Here are some notes from that:

- Transfers in and out and how to hide things

- Everything in adilas is flexible

- This new functionality is only a week old

- Talking about manual clean-up and automatic clean-up - doing side-by-side comparisons

- Using the data tables and being able to sort and search data - almost on the fly - re-writing the page based on the data.

- Some of the new CSS cards, tabs, and such - really look super cool and it seems more intuitive - it also makes it look more modern.

- We would love to keep adding new data tables and more options

- As we keep going, we may need more clean-up options

Calvin game a PowerPoint presentation on GMext Pro - This is his group mass texting solution. He did a great job and I think that people really liked it. Here a few notes that I wrote down.

- Pretend like you are a client

- Communicating to a large group or large groups (plural)

- Pitching GMext Pro - great demo and presentation

- Some of the stories of huge companies and how changes have happened and how those big companies weren't able to keep up. WordPerfect and Blockbuster were some of them. Major game changers entered the market and could do things better, faster, and cheaper. People gravitated to those new options.

- Technology happens... embrace it and thrive

- Mass texting and single text notifications - similarities and differences

- Phones and phone numbers - with mass texting, you are basically buying phone numbers so that you can send more texts at a time. Each phone number can only send 1 text per second. So you may need 5, 10, 15, 20, 25 phone numbers to get all of your texts sent out.

- Problems with people giving out the wrong phone numbers (bogus numbers or wrong numbers) - that can break your marketing campaigns - too many wrong numbers and you get reported as a spammer.

- Ways of opting in and out

--------------------------------------

Day 4

Final day of training for this go around. We started out day 4 with a group session on tips, tricks, and best practices. We spent quite a bit of time going over settings, permissions, and parent attributes for items. Steve then did a whole session on the three main parts of the balance sheet (assets, liabilities, and equity). The topic was intro to adilas backend office and functions. Steve took the words backend office and tried to flip it to - let's put the owners in the driver seat vs trying to drive from the back of the plane (pretend they are trying to fly the plane from back in the bathroom with the doors closed). Great session.

The afternoon session was talking about BI - Business Intelligence & Big Data. The group talked about databases, data, and how to both get data in and out of the databases. Lots of fun examples. We then has some other Denver power users jump in and do demos on tiered pricing and smart group buttons, and another one on the process of doing a full inventory reconciliation and full inventory count. Great info and good sessions.

The final session was supposed to be on the adilas model - vision, future, and wrap-up. We were all too tired, so we just chatted and went over a bunch of the things that we learned from the training session. We got some great notes and tried to clarify a few items, topics, and concepts. Pretty casual ending. Great people, wonderful ideas, excellent participation, and memories made. A great training session. Here are some of the notes that were taken while others were presenting:

- Molly presented on parent attributes for items - think of tag or ways to categorize things

- On parent attributes - for example: say you have an item but want to show different brand names or characteristics - Say you are selling shoes... You may want Nike, Converse, Adidas, etc. Or running, walking, hiking, trail running, etc. These would be good parent attributes or tags.

- Parent attributes are huge for ecommerce searching and creating tags for different items

- Russell did a great job on so many different features - we would love him to keep building more features

- Easy setup

- Building your own little shortcuts

- Parent attributes are used for labels, sales, ecommerce, searching, filtering, etc.

- Treat parent attributes like a way to build your own database... eight use the flex grid and the custom fields or use parent and sub attributes.

- Both parent and sub attributes are unlimited and they have a proper data type such numeric, dates, text, toggles, and drop-down lists. That really helps when putting data in and also when querying the data to get certain results back.

- As an idea... what if we build out both parent attributes and sub attributes to all 12 main player groups, inside of adilas. You literally could build your own one-to-many database relationships. The main 12 player groups are deposits, invoices, users, vendors, customers, stock/units, expense/receipts, balance sheet items, elements of time, quotes, PO's, and general inventory items. Currently, parent attributes and sub attributes are only available for parts or general inventory items. Think how cool that would be if we pushed it to the next level...

///////////

- Small note from a meeting during one of the breaks... what is the internal adilas funnel to report an error or a bug? Who gets put on that project? We need to figure out our own process and communication funnel.

- Bryan and Molly and others... funding some of the consultant projects - what is the short list and then where are things at. Basically, what do we have to work on and what are the priorities of those pieces?

- Shannon may be part of this funnel that we are trying to build out

//////////

Back to the main training even... The next session was Steve Berkenkotter and Shari Olin - going over financials and adilas backend office functions. Steve pretty much ran with this subject and did an hour long power session on the three main parts of the balance sheet (assets, liabilities, and equity).

- CPA homepage interface

- Inspecting what we expect - you have got to look at what is being delivered as a final product (actual items and/or tasks or services)

- Going back to the beginning - balance sheet homepage

- When you get a new system, we setup a default bank and default location

- Problem with batching... Say trying to remember 30 days back and/or not getting data and information for a long period of time. It kinda leaves you guessing and/or missing some of the details

- Steve - Think of flying a plain... try to be ahead of the plane... where is it going - often pilots try to think 3 tasks ahead of what they are doing

- Views of the balance sheet - a trial balance - working and checking mode

- Assets, liabilities, and equity

- We covered the difference between the income statement (P&L - profit and loss statement) & the balance sheet

- Values and tax laws

- Depreciation and schedules

- Life cycle - length of the life of an object and/or an entity - time and a schedule to lower a value (usage & wear & tear)

- The IRS has setup the tax game... They want you to play and even play up to the lines that have been setup - think of a game - play to the line

- Where you put things in very important

- Small discussion on double entry accounting - history and pros and cons

- Skate to where the puck (hockey) will be

- The formula is the most important part of it

- Passing things like a hot potato... basically moving things along the data assembly line - roll call accounting

- A balance sheet is a snap shot in time

- Talking about the profit margin and where does that come in to play

- Small holes in the ice - things that are either gotcha's or thin ice (not all the way done)

- Some of the guys and gals were saying that we need - big dumb animal pictures - super simple instructions

- Accounts receivables - Think of that as they have your inventory or they have your endeavor (a promise to pay for something) - basically, they owe you money

- You have to know the story - sometimes the numbers tell the story but sometimes the story tells the numbers what they mean

- Liabilities and hidden liabilities - be careful there

- Hidden costs

- Triggers

- Payroll and payroll taxes - this is a huge sink hole

- Sometimes we can't do things due to the technology - as that opens up, we have more options

- Auto processing and calculating needed values in non-peak times that could then be available for other reports

- Fall backs, redundancy, auto-syncs, and re-syncs

- Turtle up, sometimes the servers will shut down and pull in their legs - kinda like a turtle protecting itself

- We need an all encompassing system to help steer the ship - think platform or system

- Owners - who holds the liability

- Steve - analogy of the tail wagging the dog vs the dog wagging the tail - who is in charge & which way do things flow?

- The owner needs someone who is a decision maker and/or gate keeper

- What is the game plan and do you have buy in?

- The POS (point of sales and inventory tracking part) is only a small part of the puzzle. Very small compared to the whole business realm (world).

- Abundant model - you have to imagine a line of people wanting your services and standing in line - next, next, next

- The backend - really, this is the pilot's cockpit and/or the driver's seat

- Absorption (in take) model & attributing sub costs over time

- Dustin - I want "this" (meaning adilas & underlying data) to argue with my boss, not me.

- I need a business tool & now I can run faster & better - thank you

- Equity

- Net Profit - it comes from the P&L - one of the only connections between the income statements (P&L) and the balance sheet.

- Investment - how was this company funded and/or formed?

- Fracture - just having fun - it keeps doing it (fracturing) on its own... maybe let it keep going and play accordingly

- Change "backend office" verbage to the cockpit or balance sheet.

Towards the end of the day on day 4, we had a couple of power users show some demos and such. We had Josh do a presentation on my cart favorites and smart group buttons (tiered pricing). Drea made a suggestion that you make the pricing tiers as dummy proof as possible. They even pushed the ending values clear out to show a visual warning to the person using the buttons. The other major request was for this feature (buttons and tiered pricing) was dealing with allowing these buttons to be time sensitive for sales and promotions.

We also had Drea go through and show an inventory update and how she does a physical count and then an inventory clean-up. She would pull reports, export data, show/hide columns, add columns, print things out, and have her people go work. Then she showed how the system would take those over and short values and push them through an update PO (internal tool for updating inventory counts). Pretty cool. As we go along, we will need more clean-up tools.  Clean-up tools make things look better and help to give users a peace of mind. We also talked about trust issues and how sometimes it is tough to trust and/or trust people. All of that plays into the mix.

My final note about the training sessions is that those who played with us, live and online, really had a good time and we all learned a lot. Good times, great food, and wonderful people. Inspiring sessions. If you want more details, check out the media/content pieces (notes, excel docs, scans, and videos for more info).

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

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

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

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

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

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

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

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

Email between Danny and Steve at adilas. They are looking to see where we best can use our marketing dollars. This email came from Danny Shuford.

Good morning Steve,
I think it would be good for me to start recapping our meetings on Friday.  This way I can go back and see where we need followup.
 
This morning we discussed looking at other vertical markets that we are already in.  I made the suggestion that we go back to adilas and pull reports to see which markets have been the most profitable for us.  I think it's easy to assume that has been the cannabis industry but as we discussed the cost of doing business in this industry is extremely high when you factor in development cost and what we would really need to be competitive in marketing and advertising against some of the already established giants in the industry.  
 
We might be better served at going after bowling pro shops for instance.  That market could expand to tennis, golf, frisbee golf, ski, etc.  These rec sports all have specialty shops that need a product like ours.
 
We also discussed other industries that have serialized inventory such as trailers, motorcycles, auto, mobile homes, storage containers, etc.
 
In summary I will start pulling reports so we can analyze this even deeper.

From Danny - We are trying to bring in parent attributes to a label located on invoice side. I worked with Steve on this last week and he felt it would be best if you had a look at it.

I met with Danny over a Zoom session. He was really close. We got into his code and looked at it and found the problem. We made the fix and he was off to the races again. Good stuff.

We had a meeting with Chuck and he was showing some new progress with the campground stuff. We are code naming it camp-adilas just for fun. That was Marisa's idea. We had Danny Shuford, Marisa Shaw, Chuck, Steve, Alan, and myself on the meeting. Steve and I were lightly distracted, due to a server issue. We had two servers down and we were part in the meeting and part trying to make sure that things were being taken care of. Interesting.

Anyways, here are some notes from our meeting.

- Visual services and access to add-on services when selling and booking a campground site

- Color coded helpers to help with states, statuses, and color coding helpers

- Be able to show available, occupied, and services available to each site

- Marisa was talking about a synced reservation and a non-synced reservation. This deals with who is booking the site. Is it grandma and grandpa who put their card down to reserve 4 different sites for their family (synced or all together) or is it just a single family booking a site (non-synced or self pay). She was saying that we need to be able to do both and allow those groups to expand, contract, and break apart if needed. All of this deals with billing and reservations.

- It is really important to be able to show just the open sites for a specific date range.

- The sites themselves need different status levels. For example: pending, confirmed, checked in, checked out, reserved, etc.

- They talked about a "do not move" lock on certain site. This deals with a state or status that keeps the person locked in for some reason. It could be VIP treatment, special needs, special group considerations, or some other circumstance.

- We need to be able to add notes to any site and/or reservation.

- Block a site through a date range. Also being able to block the same site with a possible extension date range (not for sure, but a maybe or possible extended stay).

- Lots of needs for discounts and campaign tracking. This is already built in, but we wanted to note it anyways.

- Waiting lists would be nice. Able to sort and move people around on the waiting list as needed. They even talked about different queue type options.

- Lots of color coding and legends

- Being able to move reservations from the waiting list to some other available site

- Lots of talk about treating the waiting list like a queue of sort sort. The queue would be, by default, first come first server, but it would also have ways of tweaking it based off of needs, special circumstances, and/or add-on services (being able to manually move things around if needed).

- Currently, the campgrounds are doing tons of little hand-written notes and post-it notes to keep track of things. That gets crazy as things get busier.

- Danny was talking about using the priority fields on the elements of time to help sort certain reservations and/or waiting list persons. Just an idea.

- My biggest take away from the meeting was Marisa's comment - "I can sell this!" - Chuck is making the system sellable due to the ideas of the intuitive graphical user interface and what the possibilities could be. That was my favorite comment. Good stuff. We need to make this thing sellable.

- Sent an email to both Chuck and Russell to have them look into some of the stuff that we have been doing with Jonathan Wells, the designer from Rexburg, ID area. Here is the link: Web link - developers notebook - q=meeting%20with%20jonathan

Started out following some logic on the code for the calculations for customer loyalty points on the special accounts. Trying to follow the earned points logic as well as the use and/or redeem logic. I'm also trying to follow the both redeem and earn logic on the same invoice.

Steve was on another call with Danny Shuford. Once he got finished, he popped on to the meeting. We talked about cascading new changes and how much that sometime jostles the ship. We launched some code the other day and Steve got a number of emails that he had to answer, people and users just asking questions. We talked about the ever increasing need for more settings and cascading those settings all around the site. We also talked about helping our users know what is coming, especially if we are affecting multiple parties.

We talked about the job of supporting our products and helping out our customers. I told Steve that my brother loves this saying about mountains... the top is only half way. We need to take the same approach with our projects and products. Building it is only half way. The other half comes in the support, maintenance, enhancements, and education. Kinda interesting.

Alan did a team training event. We had Josh, Danny, Steve, Wayne, Bryan, Russell, Alan, and Brandon on the training meeting. The main topics were dealing with using different tools for different jobs and then going into a small quiz/discussion on what tools work best for what needs/jobs/projects. Good discussion. Some of the topics were dealing with loops, data structures, options, and scenarios for different tasks.

See attached for a link to the video.

On the morning meeting. Danny Shuford and Dustin were on there. Danny needed some help with his local development environment. We went through a few things and then he was going to keep going and even try to reinstall some of the pieces. After Danny and I finished, Dustin had some questions about pagination and limiting certain processes. We talked about some options and tools such as the FORM scope and the session scope. We went over a few code samples of setting things up, checking for the correct values, and even cleaning up the custom session containers after we were done. Great little meeting.

Danny, Dustin, Steve, and I were on the morning meeting. We answered a couple of questions and both Danny and Dustin jumped off to work on their own projects. Steve and I went over some internal API questions and we sent Steve in a direction to build a complex data structure for his API socket data. He is having fun, building both the sending and receiving side of the API socket. Often, as developers, we only get to play on one side or the other of an API socket call. Sometimes the other part of the puzzle is built by a different company and/or an outside 3rd party entity. Nice little work session.

Steve had some questions on his API socket that he is working on. Eventually, he will need to add in a number of loops and loops within loops. We are seeing about six levels deep on the loops. This is for his aggregated daily sales totals and passing data back and forth between servers. The loop levels are going to be: loop by corp, by store/location, by vendor, by category, by form (a sub group within a category), and by size (another sub group within the form group). Six levels deep. He is planning on biting off one piece at a time. Lots of loops, arrays, and structures within the arrays.

Danny popped on and had some questions. Eric came on and had a few questions as well.

Before the training meeting, Wayne joined the meeting and we talked some server stuff. We have decided to pause the AWS stuff for right now. We need to work on some internal code changes so that we can get to a clustered environment. One of the first major hang-ups is how we store images per corporation. These are logos, watermarks, and all of the images and scans per main player groups (all 12 player groups - invoices, customers, items, expense/receipts, stock/units, elements of time, deposits, etc.).

We are planning on doing a group project where we go in and fix the image storage stuff as a group. That will be fun. We also briefly talked about Docker images and how those will and/or may play in to the mix. We talked about how nice a Docker image would be for new developers coming on and being able to setup their local environment in a nice and easy way. Big time savings.

Team training meeting with Alan. We had Bryan, Danny, Dustin, Josh, Wayne, Brandon, Steve, Russell, and of course Alan on the meeting. The topic of the day was simple to complex data structures. We started out with Arrays and then went deeper. Part of the course was showing the difference between script vs tags (how to code ColdFusion - CF script vs CF tags).

We got into topics such as member functions, structures, queries, objects, algorithms, and deeper into conditional logic.

See attached for a link out to the video.

Meeting with Chuck, Steve, and I. We went over some of the new screenshots and I took a number of new screen clips. We talked about the videos that Chuck had created. He will re-render them later, once he gets a full version of the software studio that he is using for capture. Steve suggested that Chuck look at some of his brighter colors and help soften and/or tone them down a bit. Just a suggestion. We also talked about more settings and getting a sign-off from Marisa on the flow and functionality. That is our next major stepping stone. We will keep refining things until we get that sign-off. From there, we will start moving to actual code.

If you want to see the mock-up videos for the camp adilas project, click here.

We also spent some time talking about the upcoming Bridgerland demo and what we wanted to do there. I proposed a few ideas, we drew some loose sketches, and setup a new time to work on the project. Leaning towards a configurable presentation gallery vs a perfectly straight in-line presentation. Lots of fun ideas and concepts.

See attached for a number of new screenshots.

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

Notes from Chuck - sent via email on 11/13/19. I thought that they would go good here.

I had a meeting with Marisa and Danny today at 11-12.

Here are my notes from the meeting.

Overall they are very impressed and happy with the new colors and setup of the current layout
 
Updates that I need to do:
- Marisa is going to think on a better verbiage for the split sites setting.
- Need to add a setting for a waitlist for those who have already created a reservation but want a different site if it comes available.  For example if they are currently in a site with only electricity but would also like one with water and sewer hookups if it comes available
- A way to merge duplicate records (in case there was as misspelling on a record) - this isn't an essential launch feature but would be nice to have
- Add (FT) behind RV icons on sites to be more specific
- When the check in or out button on sites is clicked it will launch an invoice so the user can see if the customer has a balance and needs to pay in which case it will go to a payment option, or if the customer is paid in full the user can look over the invoice and then email or print an final invoice for the customer.
- I want to redo the layout for the user setting as it's confusing
 
At the end of the meeting Marisa was asking a time table for completion as she is excited to sell it!  I told her "maybe spring, and that I really didn't know".  - hope I wasn't overstepping on that :)  she is really excited to get it out.

Danny and I met up over the morning GoToMeeting session. We had some struggles and switched over to a Zoom session. We were trying to get his local development environment up to speed. It was having problems with pulling in sub inventory and running the basic shopping cart. We got it fixed and he is off to the races.

Working on the view only permissions. He is working on customers, vendors, and quotes. He is going in and shutting down some of the editable links. Making some of these sections view only.

Steve, Danny, Eric, Alan, and myself were on the morning meeting. Danny had questions about how to be more productive in keeping project notes, searching for things, and getting to the project details quicker. We mentioned that he could build his own top payee links (custom button) or write the id number down and then be able to go from there. We also briefly talked about having a super flexible quick search option for expanded time search. Something that would search elements of time and be able to search the mains (normal titles and notes), the sub dates and times, the sub comments and notes, the sub flags and tags, and other pieces. That would be really cool. Maybe a time-all search or something like that.

Eric and Steve were talking about new rules for the customer loyalty points and adding in some new rules. Eric is getting close on that stuff. They spent some time talking about discount rules and other advancements dealing with the special accounts and the customer loyalty points stuff. We are making progress there.

Steve and I were talking about an upcoming demo and some of the needs and direction of where we are wanting to go. Steve offered to fly out and help with setup and what not if needed. We went over a few items and talked some strategy.

After that Alan and Steve were working on some Metrc packaging stuff.

Bryan and Molly jumped on and we looked at a small bug in the cross corp invoice to PO code. We jumped on live servers and looked at database records and tried to find out what we were able based on simple searches and changes. We then tried to implement the new changes. Bryan is going to put up some small changes and we'll do more testing and go from there.

Danny, Dustin, Steve, and I were on the morning meeting. Danny had some Git (code repository stuff) questions. Steve and Dustin were working on some bug tracking. We also showed the guys some of Chuck's new layouts for sales. We had a bunch of fun ideas. Some of the ideas were being able to change the backgound images, changing the main presentation settings, and even being able to click on a link and have it automatically switch background images, verbiage, and settings. A simple little URL switch and all of a sudden, you have a customized presentation. Super cool idea.

On this same line of thinking... if we can flip the demos and presentations really easily, we could potentially use the same presentation gallery to do different presentations for different verticals. We just store the settings, verbiage changes, images, and even options, features, tools, and usage models. That would be super cool.

- Maybe using the ice-down date as a transfer between transactional data to aggregated data... That is a great switch and/or trigger. Similar to the water to ice analogy... The transactional data is kinda loose... Once it gets pushed to the aggregated data, we really want that data to be more stable (more like ice). Great idea.

- What if we had some bulk tools on the transactional side to post and/or lock things down. Once that data is locked down, we can then pull that data across to the aggregated system. Steve was talking about a possible two-part effort. They get to set a date (virtual line in the sand) and things behind that date can't be changed without altering the ice-down date. We also allow the users to lock things down on the transactional side of things.

- On a different note, Steve would like to build things out to a trust level... Making a number of adilas players as dependable cofounders. As a side note, we could use the new customer loyalty points to keep track of a virtual club member point system. They, the special accounts, are already setup like mini bank accounts.

Pretty quite morning. Both Danny and Eric popped in briefly. Mostly just a small work session and doing normal day to day stuff.

Team training lead by Wayne. Talking about unit tests and test driven design. The original meeting between Alan, Wayne, and Brandon may be seen on this page:

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5192 - prior and original notes for the project

Those who were in the meeting were: Brandon, Steve, Alan, Bryan, Danny, and Wayne.

- Unit tests - Using Ortus Solutions and TestBox - Click here for a link to TestBox. In TextBox, all tests begin with the word "test".

- On unit tests, you virtually fake everything else and just test the piece that you want. Super important for complex steps, phases, status changes, variable scenarios, etc.

- On the naming convention for tests... tell it what you are doing, what you are looking for, and what to expect. This is all in the test function name.

- We went into some light instruction on doing some testing.

- Google Wayback Machine - we were having fun looking back in the past (what the Internet looked like in the past). We went way back in the adilas history to 2008 and 2010 and were able to see some archived screenshots. Kinda fun.

See attached for a recording

///////////////////////////// - different meeting

After the main training was over, Wayne stuck around for awhile and talked with both Brandon and Steve. Lots of fun ideas and experiences were being shared. I wish I would have been recording things. Here are some of my notes.

- We talked about project management and writing out full specs on certain projects. Sometimes that is super tough due to limits of knowledge and building what is wanted vs what is being specked. There is a difference and sometimes you don't know until you get into things. It is so important to take more of a try storming type approach vs a strict requirement based set of rules. Things get pretty dynamic.

- How could we sell what we have without breaking the bank? That is huge question. As part of this conversation, we started talking about the SaaS model (software as a service) and how that model is somewhat taking over due to the benefits. We keep making it better and better over time.

- Some of the key things that are driving our sales are word of mouth, businesses expanding (existing companies needing more systems), etc. Not a whole lot of cold calls and direct selling currently.

- Expectations and scope of what is expected... currently, there are no real defined operating parameters. That creates a problem.

- Metrics and controlling what the expectations are and then playing along with that. That could be number of users, locations, invoices, inventory items, bandwidth, storage, processing, etc.

- What are the benefits that the clients are looking for? Figure that out and then show them what you are helping them with. That validates the cost and satisfies a need. What is the value to someone and how do you show/portray that value? Value means something different to every person.

- Going back to the wayback machine - One of the screenshots showed some super general stats, such as: x number of invoices, x number of PO's, x number of expenses, x number of deposits, and total pennies coming in and total pennies going out as of that date/time when the page was loaded. Kinda fun. People want to be able to see their stats.

- Small discussion on who pays for what... someone comes up with a  good idea but then who pays for that? Often that cost is passed back to the core adilas team and we are then tasked with the building, funding, supporting and other pieces. That gets really heavy some times.

- Just an idea... what if we showed what we are contributing to the core... say the new customer loyalty points or the discount engine - Those were thousands and thousands of dollars and were new free features that everybody just gets. We are building on this thing everyday.

- Another subject was... if we build something and nobody else wants it... then who pays for that? Or you have a company that wants something and they request something custom and then nobody else even knows that exists. In that scenario, other people would love to use it, but they don't even know about it. That makes it tricky, especially for who is going to fund that new development and/or maintenance.

- Long story made short, people want their data and access to that data. The battle keeps going.

- Sometimes we only recognize things that are not going well... everything else seems almost a given (what is going good). Well, it takes time and money to get all of those things to run smoothly. That's a challenge.

- Wayne was saying that Steve and I's goal is to help other people catch our vision and then run with it. The trick is getting other people to want to play that game along side with you.

Danny was ready to push up some of the view only permission changes. We got in there and looked around. He is about 80% done with that project. We talked about a few things and I spent some time listing out a few changes that I would recommend. For his first multi-page project (over 20+) he is doing awesome. Most of Danny's other projects have been a single page or a custom PDF label or something like that. I am impressed. Good stuff.

The 4 places that he is working are PO's, vendors, customers, and quotes. Just by way of a note, we may need to go back through some of the pages and actually remove some of the columns due to the removal of the drill-down links and navigation. This could be done later if needed.

Josh popped in and was asking about simple bug fixes. He wants to be one of the guys to help respond and fix some of those smaller bugs (say 1-4 hours - little mini projects.). Yesterday, he and Alan knocked out a small one that our users needed. We were shooting around some ideas and challenges. There was some talks about ways to gather the help/support info from the user on a per page basis. We also talked about who services those tickets and how we track them. We are thinking about elements of time and using that tool to hold and process the help/support tickets.

Danny chimed in and was talking about the tech support process and also the follow-up after the fact. Building customer loyalty by providing the fish to the seal (reward) and following up. You gain a lot of ground that way.

We did a small demo of some of the new screenshots from Jonathan. Lots of good ideas and options. Steve really liked a number of the new concepts that he was brining into the mix.

Build and break, build and break. This seems to be a reoccurring theme. Build it, let people use it (almost even abuse it), when it breaks, you rebuild it and start over again. You have to do this over and over again.

Alan did some team training on if statements, switch statements, for loops, for each loops, while loops, and do while loops. We had Alan, Brandon, Steve, Danny, Josh, Russell, and Wayne on the meeting. Here are a list of smaller sub videos that were shown. Each of these are less than 4 minutes each.

https://youtu.be/IRY9B43QbBM - if statements
https://youtu.be/c6ObO5Ind8U - switch statements
https://youtu.be/jxfhdJsAD8I - for loops
https://youtu.be/o6S6NMrIPC8 - for each loops
https://youtu.be/NMoOKoAMJSI - while loops
https://youtu.be/9lTQlrbtHP0 - do while loops

See the attached video link for the full 1 hour training meeting.

Group meeting dealing with camp adilas project. We had Chuck, Marisa, Danny, Steve, and Brandon on the meeting. We are all really excited to see where things go. Good stuff.

- We talked about confirmation numbers and being able to add and search those.

- Being able to change customers after the fact. This could be the main customer or adding additional sub customers, depending on needs.

- If more options are needed, it will be built on top of the existing adilas backend platform - that opens up a number options.

- Report settings - adding prebuilt reports based off of the settings. Being able to tweak things as needed.

- Permissions and fully removing certain icons from the menu systems based on those permissions or lack of permissions. We decided that fully removing those options would be best for this project.

- Mobile and being able to help solve issues on site - this is huge and could be a great selling point (the mobile version of the app).

- We talked about helping with real traffic flow (actual cars, trucks, vans, SUV's, RV's, campers, trailers, etc.). If we can help alter the bottlenecks, that may be a huge help. The mobile app will open up some options there. Some good discussions around that topic.

- Self check-in options

- Digital signatures and disclaimers - other possible customer portal options

- "I'm here" button and then help them get checked in

- Using other adilas reps and consultants to help do other things and provide other needed services or additional options. This could be design, web work, custom code, training, setup, map stuff, etc. All kinds of options.

- Cart settings for scans and presets. Being able to show preconfigured add-on's and normal barcode scanner POS options.

- Being able to set a default home screen for different users. For example: the check-in desk, the gift shop, the reservations desk, whatever.

- We got the verbal green light to move from graphic concepting to HTML/CSS - clickable web mock-up with dummy data. After that gets finished, we'll actually wire the whole thing up via backend server-side code and database connections.

Awesome meeting. See attached for the video recording of the meeting. There are also a number of still screenshots in the photo gallery.

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

These are some notes that Chuck submitted after the meeting.

Hi everyone,

Here are the notes I took from today's meeting.  Let me know if I missed something.

Notes from meeting with Brandon, Steve, Marisa, Danny and Charles on the design sign off
 
Tweaks that need to be done to final product
 
- Reservation # added to invoice (under Invoice in the upper left corner of the invoice) and possibly use a bar code or QR scan for the invoice to pull up the invoice.
- We can use a setting for a seed to generate the reservation number for example use a date and site number for the seed or something similar
- We need to have the ability to change or split the invoice for different customers.  This can be placed in the settings icon on the invoice
- Have a go to admin that would place the customer back into the Adilas back end if they needed to adjust advanced settings
- Add a vacant filter quick button to the sites page
- Ability to add quick buttons to the menu list.  The customer would be able to add favorite searches or functions to the menu list by choosing an icon and setting up a tool tip.  Setting would be found under the setting icon for each section
- When we get to doing the front end we should look at having a self check-in option that can either be a full self check-in or an I'm here button to notify the user that a customer is there and ready to check in
- Need to look at icons and standardize some of the icons.  Replace the cog with filter at any area that a filter is being used instead of settings.
- Be able to set which cart/invoice section is default (cart, invoice, or scan)
- Make a user that only has access to the pos system and can just sit and scan
- Changed the calendar to have green vacant and red filed on the sites overview
- On the calendar ad function so you can click a day and it will take you to the sites page for that day
- Add a date range either through search or above calendar to change the background of the calendar pages.  When one of those dates is selected it will take you to the sites page with that date range pre-loaded

Steve, Danny, and I were on a GoToMeeting session. We were watching and monitoring servers, on tech support calls, and trying to get things up and running. As part of the conversation we talked a lot about some of the outside parties and being able to access the pieces that we need to. This could be outside 3rd party code, independent apps, specific code, WordPress sites, and other pieces. We really need our own access to these pieces.

Hosted solutions are big animals. We have to build it, service it, and keep it going.

We have a great team of people who all have a number of key talents and pieces. How can we keep organizing things so that we get and keep those key players.

Looking at options and seeing where we can fill in the blanks.

We talked about text message marketing and some of the crazy challenges with that. Currently, there are two main players out there. One is Twilio and the other is AWS. Both of them have some built-in text messaging options. Here is a link to Twilio - https://www.twilio.com/

Wayne popped in and we looked at data 0 and data 2. Currently, those servers are some high traffic volume players. We were talking about ways of splitting up the servers into smaller clusters and putting the databases on their own dedicated servers. We also talked about some world building project stuff and splitting up databases. As a fun side note, Wayne jumped in and showed us some of the resource monitor stuff for that server.

Sometimes we use custom code as a virtual buy-in or investment to our platform. We love it when others succeed.

Steve and I spent a bunch of time talking about our current plan and how things are developing. We will keep on keeping on. Lots of good stuff ahead.

Steve, Dustin, and Danny were on the morning meeting. Each of them checked in and lightly reported about where they were at on their different projects. Steve had some questions about some of the up and coming servers and the states and status of those servers. I mentioned to Steve that maybe we need some kind of official request form vs just emails and verbal requests. Those are hard to track.

We also had some discussions about the efforts that we are trying to make to get our guys and people to help contribute and use the elements of time to keep track of things. Steve has been a great driving force for good in that direction. He is even starting to tie in the elements of time id numbers to the guys invoices and pay. That will help. Sadly, when it is tied to someone's pay, it starts to become important. Once again, using the system and making it be the bad guy (in a way). We've done that before.

Alan lead some team training again this morning. See attached for a copy of the recording. We had Alan, Bryan, Danny, Dustin, Josh, Steve, and myself in the training session. We covered recursion (interloping functions and/or self calling functions) and got into closures as well. Some of these are somewhat advanced techniques. Along with that, we lightly talked about base cases, how to jump our of recursion processes, map, reduce, filter, each, stacks, queues, and other programming options.

We spent some time talking about FILO (first in last out), LIFO (last in first out), and FIFO (first in first out) operations. These are pretty common in computer programming and how to loop through various records. As a fun side note, those same terms are used in accounting and inventory tracking on how to account for items being moved through a company. Interesting.

We did some light dives into the underlying Java libraries and using Java stacks (arrays). Alan went over some options and member functions like push, pop, size, etc. We also talked about using built-in member functions to help format and string things together in modern script languages.

See attached for a copy of the training and recording.

A bunch of us were gathered for the morning meeting. Danny and Steve were talking about sales options for the camp adilas project when I joined. After that, Wayne, Steve, Danny, Dustin, Alan, Eric, and myself were on the call. A few random questions about servers, aggregated totals, custom database instances, etc.

Danny, Dustin, Steve, Wayne, and I were on the meeting. Danny and Steve were working on some custom logic when I joined in. After that, Wayne had some questions on security, internal processes, and systems audits. He has a client that has tons of questions about these topics. He was just looking for some information. We sent him a link dealing with some Q and A's that we answered.

https://news.adilas.biz/2019/10/25/adilas-database-information/ - q and a about servers and database stuff

- Outsource and use Newtek (the server farm) for all special needs - backups, disaster recovery, virtualization, limited access, and other service plans.

Steve and I spent some time talking about database design and aggregated data totals. We ended up talking about grouping, flagging, tagging, and how to manage those loops and/or processes. As part of our design we ended up talking about the phase from Eric - Extract, transform, and load. We dived in deeper on some of those pieces and tried to make some plans.

Focusing on what we have... We have to start there. We love to promise things but that always takes time.

Steve and I were having a conversation about sales and how to use what we have and then building what they need, meaning our clients. We also talked about getting new clients and/or helping to service the existing clients by capturing some of the byproduct services (setup, training, consulting, design, custom code, oversight, management, etc.).

Working with Danny on a deep code review. He is adding 6 new view only permissions dealing with view only on vendors, PO's, customers, quotes, parts/items, and expense/receipts. We were dealing with 50+ pages and lots of black box changes. Great session.

Back on with Danny working on code review and sign-off on the six new view only permissions. We ended up going backwards and loosing up a few of the pages. We had them almost too tight (took away too many of the options and navigation).

Adilas team training lead by Alan Williams. We had Alan, Bryan, Danny, Dustin, Russell, Brandon, and Eric on the meeting. Steve was there, but I believe he was on another call and just muted.

Anyways, most of the session was dealing with arrays and different ways of getting the same results. Mostly a practice session of sorts. We did some hardcoding, some loops, and even got into some closures such as map, reduce, each, etc. We talked about hardcoding things vs dynamically creating content and pros and cons of both. Lots of good comments back and forth and good team or peer training going on. Good stuff.

See attached for both the video and the chat log - we were passing code samples back and forth.

Danny and I did another session on the view only permissions. There are six new permissions. We got files merged in and uploaded to data 0. Danny is going to test things and then let me know. We'll push files to the other servers either later tonight or tomorrow morning.

Danny, Dustin, and Steve checked in at different times this morning. Mostly some quick questions. Once we were done with that, everybody just started working on their own projects. Pretty casual.

A couple of the guys were on the morning meeting. Danny checked in, Eric checked in, and Steve was on the meeting. Eric and myself were talking about version control and testing. These are somewhat smaller things but they end up having bigger consequences down the road. Eric was putting in his vote on both pieces (full version control and testing). We already do a lot of version control, but there are certain custom projects that we let slide through without putting them in version control. It doesn't seem to be a problem right at first, but it bears its head later on if work is needed to be done on those pieces. We have had many a file that gets overwritten and changed because it is not in the master code repository or master code branch. We do pretty good at the core pieces but we struggle a little bit with the custom pieces. Eric volunteered to help with some code sign-off stuff. He doesn't want to do the big projects, but he does want to help with some of the purely custom stuff.

- Small possible bug with core loyalty points and being able to get the redemption value clear down to zero. A client reported that they had to leave one cent in the account. They couldn't get clear down to $0.00. That may be a rounding error or a simple greater than or greater than or equals type thing (mathematical  operator sign). Eric is going to follow that one around and get it finished.

After Eric left, I only stayed on the meeting for a little bit. Steve and Danny were working on getting a local development environment setup for Danny. I spent the rest of the meeting doing emails and recording notes.

Met with Danny to work on allowing certain special characters into sub inventory attribute values. Certain special characters may be dangerous due to a thing called cross site scripting (XSS). Normally we restrict certain things to keep the data clean and safe. There is a new label requirement coming for 1/1/2020 which requires the clients to be able to use certain special characters in the sub attributes. Those values will eventually be used on labels.

Danny and I got in there and made a few changes. We merged in the new code and pushed it up online. After that, I kept working on the two new servers and prepping things so that we could release them as live production servers.

Steve and Danny were on the meeting when I joined. They are getting things going and having fun. They were talking about some options to chat with a developer who may want to play in the white label arena. Just talking at this point. Dustin and Eric joined the meeting as well. After Steve and Danny were done, Eric had a number of questions. Including some questions for Steve and I about doing more core adilas stuff. We chatted and gave him the verbal go ahead. Eric has been a great help and brings a number of key pieces to the table. Good stuff.

One of the topics of the day was dealing with API sockets and 3rd party solutions. A ongoing question was, are we building things to push data or pull data? Who is responsible for what part? Those questions always come up and then it comes down to what points are being pushed/pulled and who is paying for what development? Good conversation and Eric has a great working feel for what is going on.

We briefly talked about using Eric to help with some of the new campground stuff and having him help with that wire up job. We have some other things that we need him to do first, but making good progress and developing a good plan. If we could get Eric to switch from custom development to adilas core development, that would be awesome.

Danny jumped on and had a few questions about his local environment. We helped him do some light debugging and got a few files in place. All is well now with his local development system.

After that, I spent some time prepping and recording notes from earlier today. Busy times.

Danny jumped in and reported. He was excited that he figured some stuff out.

Dustin jumped in and touched base.

Steve and I were chatting. He and Danny had a great meeting with a consultant/developer. His name is Grant. Talking about all kinds of angles and what does it take to get and keep a customer? Light talks about niche type arenas and areas. Where do you compete and what do you bring to the table? Back to supply and demand type scenarios.

- Is the world flat? That is a trick question... As technology increases and as business grows, things tend to flatten out (become normalized). Steve and I were using a GoToMeeting session to bridge miles and miles - all through technology.

- We are having different consultants and sales type persons talking more to us. Lots of management and motivational type consultants trying to help us out and getting things going. Lots of flavors and getting things moving in a direction.

- Steve is hearing a small bell ringing… somewhat of a warning bell of sorts. We need to change some things and work more on what we have and what we offer. Currently, we are all over the place and not fully focused.

- David and Goliath type scenario

- We really want to work on our own product and help refine it and make it better and better.

- Small talks about protection and how can we preserve that? We want to keep building and growing and we know that there are some risks out there.

Great team training meeting today. We were working on real world problems and things we do all the time inside of adilas. We went over building form controls how we have been doing and where it could possibly go. Really fun seeing the different ways and even how we could push it clear out to the component (reusable custom code/tags) level. Lots of fun. We had Steve, Brandon, Alan, Bryan, Danny, and Josh on the call.

We spent some time going step by step and building on the last code sets. We talked about scoping variables and when to not scope the variables (scopeless). We did quite a bit of training on reduce options and the power of modularizing the components. This leads into an MVC (model, view, controller) type level with options. Good stuff.

See attached for the video.

Steve and I met as part of the morning meeting. I can tell that Steve has a lot on his plate. He is running from fire to fire. Some of that may be year end stuff and pressure and some of it may just be busy times. Danny checked in and said hi. After Steve left, I jumped back on the year end stuff for 1099's and W-2's. I also had a couple of phone calls, emails, tech support stuff, some developers checked in, and other random stuff.

As a side note, Russell sent me this link. It has some great UX and UI quotes. 
Web link - 16 quotes

UX and UI mean user experience and user interface - how does your product act and interact with a user?

2/3/20: Danny emailed with Pete and is waiting to hear back from Pete.

Gun store wants to simplify serialized sales process. Steve sees this as settings and wants to line Danny out once reviewed with Brandon.

Brandon drew out how steps now include 1-10 but could be limited (with checked boxes or unchecked) so fewer steps were needed.

See doc folder for png files that show what he wants.

Had Alan on the meeting with Chuck and I today. We wanted to get him in on the projects and getting a high level awareness of what is going on. We started out with the camp adilas project and where that is in the development cycle. Chuck did a demo for Alan and they went back and forth with ideas and questions. Both guys are excited to work together on the different projects.

After that, we rolled into a session talking about some snow owl theme (current look and feel inside the system) changes and where that could go. We looked at some mock-ups for the classic homepage and then then into user permissions and profiles. See the screenshots for some of the new ideas. Still in concept mode but definitely coming. We are thinking of putting a facelift on a number of the high usage pages or places where it looks older or more outdated. We are trying to change up the user experience and make it better and better.

We talked about user profiles, permissions, and allowing templates and presets. We talked about having tabs, vertical tabs, accordion displays (ways to show/hide additional data), floating submit buttons, putting help files and summaries under the gear icon on the side of the page, stash and go with a sock drawer type concept, and even changing the page flow to help the users. Currently, they do an action and may end up on a different page or on a success message. They then have to navigate away to another place or do some other action. Good page flow will really help.

A couple of other topics were mixing tasks and skills to get a job/project done vs a full stack developer (able to go from top to bottom or point a to point z - the whole thing). We may need to help some of our developers get really good at certain tasks to help with efficiency and productivity. We also talked about light messages and helping to lightly push our users towards the newer look and feel and/or new functionality options. We know that we have to be careful there, but we will make some attempts when ready.

After the meeting, Alan and I talked briefly about some of our developers and where we are headed and who could help in what regard.

New note added on 1/8/20 - Danny Shuford contacted me and asked that we make the view only permissions easier to get to. I showed him some of the concepts of where we are going with user profiles and permissions and said that I would add a note to this element of time. The original idea came from Kelly Whyman and Danny brought it to us. Great idea. That may require some special code just because the view only permissions are not standalone permissions. They require the main permission and then the view only permission to limit the options.

On the morning meeting. Pretty quite. Answering emails, paying bills, and texting back and forth with developers. Danny popped in for a bit and had a couple small questions. They were dealing with the new view only permissions (six new permissions) and making it easier to click those options. I recorded some notes on the time id # 5463.

- This is another idea dealing with permissions. We may need to flag and tag the permissions so that we could show them differently. Currently, they are setup based off of the layout of the classic homepage (system search, system basics, system assets, system liabilities, system time and requests, system reports, system maintenance, and system management). It may be really nice if we could put flags on certain permissions such as invoices, POS (point of sale), deposits, customers, view only, etc. Tag and flag them so that we could pull related permissions into smaller groups to help with grouping and clustering of the permissions.

- Along those same lines... we need to add flags and tags on navigation options, permissions, and settings. That will help us organize and sub organize the permissions, settings, and navigation options. For example: All settings that deal with invoices, all permissions that deal with invoices, all navigation options that deal with invoices. Get them all grouped together, using flags and tags. We could then allow for those values to be searched through the quick search. See the concept art work from Jonathan Wells dealing with the new adilas navigation system. This same concept may be extended to pages, help files, videos, tutorials, etc. Basically flag and tag everything so that a single word search will bring up all possible options (mini search engine within the system). See attached for small concept idea on adding specific flags and tags to the items (permissions, settings, help files, nav, etc.).

Steve, Danny, and Dustin were on the morning meeting. I joined later on due to a dentist appointment. Steve was helping the guys with their different projects.

Steve and Danny were on the meeting this morning. After they figured out their stuff, Steve had a couple of requests for me. He and I are planning to meet up with Wayne Andersen when he comes to visit family here in the states. Wayne currently lives in Portugal, over by Spain. We have met with him tons of times but never officially met, in person.

Wayne ended up joining the meeting and reported on some VPS's (virtual private servers) and where things are at with that. We have a client that wants his own VPS to run his own data analyst against. Wayne is setting those pieces in place. Basically, we have to have a private environment, access to archived data (non live data), and then any other access to the server as needed.

Wayne also reported on a server to server migration project that we have him working on. 

Alan lead the team training today. We did a light review and then jumped into more database logic and topics. We spent quite a bit of time discussing database data types and basic select queries. We had Brandon, Alan, Danny, Josh, and Wayne on the meeting.

See attached for the chat log as well as the video recording.

Steve was leading out on the morning meeting today. Both Dustin and Danny checked in briefly. After they were done, Steve and I spent over an hour chatting and talking about direction and options. We had an assignment from a business consultant to talk about a some disfunctions (places that need work). We spent some time and worked on one area. The disfunction area was rejecting structure. There are about five areas that we will end up looking into.

See attached for some notes. The main take away was we need to keep going and doing what we are doing. We would love to focus more on the adilas café ideas and concepts as well as opening up the market to allow our power users to help staff that part of the puzzle (buying and selling services - part of the adilas marketplace). The other topic that we talked about was employees and employers. Steve really likes the idea of the dependables and keeping a small core team of independents that can run and manage themselves.

Steve, Danny, and Dustin were on the morning meeting when I joined. They each reported and then bailed out. That is pretty common. After that, Steve had a few questions. We went over some of his plans for the transactional data to enterprise data roll-ups and some of his plans. He is right on target and seems to have a good plan for that project or multitude of projects. Good stuff.

Met with Chuck over a GoToMeeting session. We covered three main things in our meeting today. The first thing we looked at was the Wander Ways website and the mock-ups for the sales arm of the camp adilas project. See the screenshot for an update. Nice looking site and Chuck will be working with Marisa and Danny on prices, verbiage, photos, and content. Exciting.

We also went over some new mock-ups on the adilas corp-wide settings and corp administrator homepage. We talked about some options and also decided that a nice banner image would really help that page out.

The last thing that we did was go over some code for the camp adilas internal tools and project. This project is in the coding phase and looking good. Chuck is using some of his new JavaScript skills to help wire things up a bit. Still in the transition between code mock-up (CSS and HTML) and backend wiring (making it real and come to life). Great report and making progress.

As of 10/29: Another $500 roughly.
As of 9/22/2020, 2119.25 billed. Danny has completed but there is a snag with the particular pdfs that Scott has. Waiting to see what happens next.

7/27/2020: First part complete as of today. Waiting for Brandon to push live? Danny starting on second part. To date, $1,000 billed.

5/28/2020: Client paid- in the queue

4/2/20: Waiting on green light...

2/13/20: Client is interested in moving forward.

2/3/20: Images to subs was quoted at $2,000. Then once this is done, Danny could do "label" for $500-$1,000. Sent email to client today, waiting to hear back.

Attach PDF's to subs and merge the pdf's to print all together. CMS media content

1/23/20: "We are being required to print Certificate of Analysis for each batch that we transport for each client.  The BCC is requiring physical copies to be transported with the manifest and physical goods.  We are currently printing each COA manually by each line item on the invoice.  I was thinking that Adilas may be able to help us with associating COA’s to Sub Items as PDF’s, then combining these into one PDF that can be printed."

Database team training done by Alan. We had Alan, Brandon, Bryan, Danny, and Josh on the call. The topics discussed were: tables, layouts, relationships, joiner tables, one-to-many relationships, data diagrams, data types, triggers, stored procedures, functions, and views (snapshots in time or specific copies of table data). There was also some talks about automating actions, tight and loose connections and dependencies, multi-step processing, and other options.

We also spent quite a bit of time talking about how we have a lot of existing code in ColdFusion (server-side scripting language) and how we could move and/or transfer some of that power and control over to the actual database. This transfer of power and management could be code, logic, locks, and other database specific code and/or functions. As we keep going forward, we will most likely see more decoupling and loosening of the server-side scripting language (currently Adobe ColdFusion) from the underlying database code (SQL). The database may end up doing more work on its own vs having to be told what to do every time from the scripting language. Small transfer of power.

See attached for the recording.

Danny had some questions about multiple barcodes on PDF labels. I recommended him to get with Calvin and see if he could get the adilas label builder wizard installed and configured. That product already allows for multiple barcodes and QR codes per label right now. Here is a link to some more info on that product.

Steve and Dustin were on the meeting and introduced a new developer Alex Hearding. Alex will be helping Steve and Dustin with different tasks and what not. Light intros and talking about next steps.

Alan did a team training session today. We were working on database queries and syntax. Only myself, Alan, and Danny were on the meeting. Because it was so few of us, we spent some extra time and Alan catered the lesson to Danny and helped him get going. That was really good. The main topic was beginner select queries. See attached for the recording link.

clean up code for plant tags

Danny and I pushed up a few new files. There were a couple files that needed to be pushed up to tighten things up a bit. This was dealing with the six new view only permissions.

After that, I helped Eric push some code up for the web/API sockets dealing with inventory and my cart favorite buttons.

Team training meeting done by Alan. We had Wayne, Brandon, Bryan, Josh, Danny, and Alan on the meeting. We went over some basic database queries and talked about a number of key pieces dealing with queries. Some of the topics were: Select statements, in clauses, or statements, aggregate functions, counts, table joins, etc.

See attached for a copy of the video recording.

Met with Danny to figure out if we want to go ahead and push new code up to master or wait for Dustin.  Dustin and Danny discussed this and they felt it might be best for Danny to push up his code and then Dustin when he is ready.  We worked on the code but didn't push it. Brandon has a question for Alan before pushing it.

Part way through the meeting, Kelly joined and wanted to show me an issue with some inventory reports and costing. After we looked at the issue, we scheduled some time on Monday to get into deeper and look around.

Emails, tech support, reverting files for Danny, and helping to train Tanner on some new tasks.

Alan did a team training on database queries and sub queries. I got lost at the end, just because it was new terrain. It is good to go over that type of complex query. We had Alan, Brandon, Danny, Josh, and Bryan on the training session.

See attached for the video recording. 1 hour.

Emails, tech support, and API socket help. Danny had some questions about a report and a project to add some new columns. I also did some review on a document for project management.

Cory ask Danny to take on this project to amend a report based on id number 1640 (time id inside of adilas - as a community funded project).

Working with Danny on the project. We did some code management stuff (Git and bitbucket) and then started in on the project. We wrote down requirements, questions, specs, cautions, etc. We then started working on the actual code pieces. Not sure, but I'm planning on working with Danny on this project all the way through from start to finish. It may be a bit deep for him to do on his own. Great training session.

Danny to start design work and implementation of new website for adilascannabis.  the current website has not been updated in over 5 years and needs a major overhaul.  I believe we can do this relatively quick using wordpress template.  it will also give us the ability to initiate a blog which will help in SEO.

On a GoToMeeting session with Danny. We were working on a daily/weekly sales report and adding in new columns for cost of goods sold (cogs), profit, and profit percentage. He is doing great and making progress.

There were 5 people on the morning meeting when I joined. Steve was helping them and they were lightly in a line. Each one had some small reports and/or questions. Steve helped some of them and others had questions for me. We had Danny, Jon (new developer), Alan, and Eric online with us. Steve helped Danny, We then helped Jon with some new pages and getting started on some code changes. After that, we worked with Eric and then Alan.

After each of the other guys had their questions answered, Steve and I worked together on some logic on the cross corp (aggregate or enterprise system) mappings that he is working on.

Reviewing code and making a few changes with Danny. He is super close. We should get it in the next push. While he was fixing a few things, I was recording notes from the day.

On the meeting with Steve and Danny. Going over small items, projects, and new changes. Lots of moving pieces. Steve was showing me a shopping cart demo done by Spencer (outside developer) and how cool it was.

Web link - Adilas/Main_GUI.html - demo page for the short and sweet cart

Steve was also showing me some of his cross-corp (enterprise level) vendor mapping project. It is looking good. We talked about a few tweaks, but making progress.

After Steve left, Wayne joined the meeting. We logged into some of the remote VPS servers and made a few changes. He also helped me with my local box, as it was running slow. While rebooting my local machine, I called and talked with my dad. He has done some grant writing in the past. I briefly talked to him and asked him if he would be willing to help me and play that game again. He said yes and we'll set something up. Fun stuff.

Danny and I were working on a multi date report and figuring out final piece for totals on percent of profit. Lots of variables and lots of loops.

Bryan Dayton joined the meeting for a little bit. He had some questions and we got him going while Danny was copying and pasting code. Bryan's code was dealing with different tasks and if statements.

Full visual code review with Danny on his custom daily/weekly sales report. We also did some training on arrays and how those work as super variables as compared to basic or singular variables.

Completion of project to push code to servers. Working with Danny and going through code sign-off and clean-up. We cleaned up his branch, rand some code diffs, and line by line clean-up.

Instead of group and team training today, Steve went through a number of things with those who were online. We had Alan, Steve, Brandon, and Danny. Steve went over a document that had 10 basic steps to what we are trying to do with the custom projects. As part of the conversation, we talked about a number of other pieces such as:

- Moving things from the general project pool over to the project queue

- limiting R&D and moving R&D into real-time development (bring it closer to home)

- marketing the custom options that we have

- SaaS solutions (software as a solution)

- 2 different teams - look and feel team and backend team

Topics from the morning meeting. Build one thing and get it across the finish line. Then do the next, and so on. Pare things down to one at a time. Steve and Eric were talking about things and different topics. We keep getting distracted by so many things going on. Steve, Eric, Danny, Dustin, and I were all on the GoToMeeting session.

Danny joined the meeting but had some traction on another project and wanted to keep going there. He will reschedule so that we may review code for final push to servers for his custom report.

Spent the rest of the time recording notes and scheduling things on the calendar.

Review code to push to other servers. We did and got his project pushed to all servers.

Line Danny out on this new project. Worked with Dannon on a new black box invoice project. Got him setup with ideas and direction. After that, Steve and I talked about projects that are going on and what needs help, what is working, and direction. Constant battle. Fun but sometimes tiring.

Danny checked in and had a question or two. We got him going. Paying bills, doing emails, and other small tasks. Went back and recorded some meeting notes from scribbles on post-it notes.

4/2/20: Danny asked if we have the ability to process Square payments...

Not at this time as we are not current to if they have the API availability 

Working with Danny over a Zoom session. He had two new black box invoices to get a code sign-off for a client. We merged things in and pushed the new code up to the server. Emails and tech support. Met up with Bryan and went over some of his promotion code stuff. That has been a long hard project. The main difference is internal shopping cart vs ecommerce shopping cart. They have slightly different flows, so you have to play a little bit different.

Joined the morning meeting. Steve and Danny were on. Danny was looking for some marketing stuff and testimonials. We chatted about a could good options and persons to contact. After that, Steve and I spent most of the morning session going over projects, small questions, changes, and going over direction.

Met up with Danny to go over his next project - id #1449 in adilas. The project deals with customer fields names and aliases. The first one that has been requested is the "terms" field and the alias as chosen by user under the settings for that section. We are planning on prepping the field to make it even better and better for future field name aliases and corp level settings. Good stuff.

Just for fun, these are some notes from Steve to his friend Danny.

adilas is the future of cloud
custom cloud

Current SAAS (Imagine a static cloud with our competition on that cloud)
Future CSAAS (imagine a dynamic cloud with just adilas on it)

Old SAAS is version based (updates roll out via version)
Future SAAS is custom based (updates roll out real time and are client driven)

Not only is adilas changing real time, adilas changes are driven by the client.

This creates the most powerful software and a client can drive their business forward.

Times change, software must change with the times

Business processes change, adilas changes by businesses.

Look at the black box code you just completed, that was an extreme example.
Look at the view only code you just completed, that was specific client based update that all clients have access to. Many will never use this but it's part of the process to build the solution bigger.

adilas - Expanding and Refining Functionality, Driven by Business

adilas gives businesses the ultimate tool

--------

As part of our meeting, Chuck joined us and we talked about the presentation gallery (navigation, slides, and talking points) vs a real self-guided website that has a self-contained sales pitch. Great little meeting. See attached for a small version of where presentation gallery and slides are headed.

4/9/20: Requested by Danny per Steve.

Continue where we left off conditioning pages for session scope to allow cascading of alias fields for customers (custom field settings for the add/edit customer fields). We had a pretty good work session and made a bunch of progress including a new method to look-up and create the dynamic field setting structure (way we hold the data and put it in the session scope for later use).

4/10/2020: currently you can search by salesperson/budtender but the name doesn't pull into report or export. super_invoice_line_results.cfm

4 different spots are touched. One tricky thing is updating a column count. middle to low weight. Danny or Bryan could do. 3-4 hours.
In the future choose certain columns. 

We had a good meeting with Jonathan Johnson doing some business consulting. Steve and I met with him for the first couple of hours. We then invited Danny and Marisa in to talk about sales and marketing strategy stuff. I took lots of notes and they are on my local hard drive.

- Figure out how to use your consultant well and then do it, use them as a tool. This was a request from Jonathan.

- In decision making, step up to the plate and swing. Let's get to work.

- We really need to keep applying what we are learning and what we know. Knowledge, unapplied, doesn't do much.

- We are looking for help to build a sales and marketing department within the adilas business model and structure.

- Dealing with leadership and decisions, we need goals, focus, direction, and a plan. Take those next steps and get going.

When I joined the morning meeting, there were multiple people on already. Danny, Dustin, Eric, and Steve were on. They finished their business and then each of them ended up leaving except for Eric. He had some questions dealing with custom industry-specific interfaces and the printing of labels. I gathered up some resources for him and sent him a number of links as well as showed him how to access the pieces inside of the system.

Steve and I chatted about some marketing ideas and Danny chimed in that he really enjoyed the business consulting meeting yesterday with Jonathan Johnson from Epic Enterprises. Good stuff.

Working with Danny on some merge code stuff for his dynamic customer settings.

New project with Danny. We went over a new dynamic customer input setting for the additional contacts that are available when adding a new customer/client. The new settings would allow us to show/hide up to 3 additional contacts and prep the forms with specific values.

After the meeting with Danny, I got a call from Steve. It's his day off, but he was checking in on some server issues, server loads, and discussions about moving clients around to newer servers (load balancing).

There were 5 people on the call when I got in. Each of them asked some questions and then eventually bailed out to work on their own projects. Here are some things that I pulled out of there discussions.

- What is the real purpose there? Thinking on a per page level. If that is known, that can really set the tone for the project - aka a focus. Basically, being more clear on the objectives and then sticking to it. That really helps. Idea was presented by both Russell and Danny.

- Some marketing ideas from Danny about free software and then charge for other pieces and/or services. He was talking about a product out there for music lovers and how the sound mixing software was free but they had to pay for specific hardware. Lots of options.

- Eric was talking about being able to build business processes. I would love to take that to the next level. Think how cool it would be if we could setup an area where people could build a business process, name it, setup defaults, determine layouts, requirements, and flow. Then, once those pieces are set and in place (saved), we then could show and use those real settings. Imagine being able to setup your own data assembly line and then the system helps you keep and maintain those business processes. If you need to alter something, you could go back and just tweak some of the setup pieces. That would be so cool.

- Talking about auto printing from the web and using a queue of sorts and then doing the print jobs based off of a service that monitors that queue.

- Talking about custom code jobs. How are jobs coming in and being completed? We have lots of independents and what is the plan for the adilas shop (dev shop) and the projects being passed through? Along those lines, we need to take care of the house. The house being adilas. Often, some of the independents do the work, they get paid, they move on, but they suck tons of resources from adilas without paying for any of those usages. Time, talent, and money are all resources... we need to make sure we are managing and taking care of those pieces.

- Eric was talking about rough estimates and how he likes to bid a project. If needed, he sets up an estimate and then says he bills by the hour regardless. If things get deeper, he then lets the client know that it will be different then the original estimate. It flips it back on the clients and they get to say yea or nay. It's a way to somewhat protect yourself.

Danny, Dustin, Steve, and Eric all checking in. Danny is working on some customer settings for adding new additional contacts and being able to configure and preset options. Dustin is working on sub queue settings and how that relates to business flow and logic based on the queue choice (pick-up, drive-through, delivery, in-store, online orders, etc.). Basically using existing features and flagging and tagging invoices and quotes (part of an internal process).

Steve and I spent some time talking about aggregated system and what they might look like. We spent a good half an hour here and were drawing and talking pros and cons. We are still exploring some of these ideas.

Eric popped in and had some questions about auto printing labels, settings, and looking for code samples and direction. He is doing great and helping with some of the growing custom needs.

Danny and I looked at some new code and made a few tweaks. It looked good so we merged it in. Once we deployed it, we ran into a small bug and had to roll one of the pages back. We'll update the code and make it work, but temporarily we had to roll back (only partially done). Good session though.

Working with Danny on trouble shooting some new error messages on the add/edit customer pages and settings. We launched some new code yesterday and had to roll one of the pages back due to an edit problem. We redid the page and did some testing. We got it fixed and pushed up to all servers.

Recording notes from earlier today and other to do list stuff. Paying bills. Looking into some small tweaks and enhancements. Pretty light.

A bunch of the guys pushed in some custom code. I wasn't able to get to it, but they have been making branches so that we could merge in tons of custom files. Bryan reported almost 400 files, just by himself. We have branches from Danny, Bryan, Eric, etc.

On the morning meeting. Both Eric and Danny popped in and had some questions about git and bit bucket stuff (code repository). We chatted and then they both bailed out. I was doing emails and cleaning up some older pull requests on bit bucket.

Danny popped in and had some questions on a loop. After that Steve joined and we were just working on small projects. Eventually we ended up talking about strategy and our model and where things are going. We used the last half of the meeting to go over ideas, draw things out, and chat.

Danny was having issues with the bulk print labels and pulling the parent attributes correctly per label. We looked into it, added some dynamic variables and then unwound those pieces and went back to simple values. We ended up adding the dynamics to the upper logic page instead of the sub logic page. Somewhat of a round about.

Emails, light tech support, and helping Danny merge in a small bulk print labels file.

Got on a meeting with Russell just to get him some server log files. He is going to be parsing them and building a tool to pull the log files apart (one of his class projects for school).

Anyways, as we were downloading logs and what not, we ended up striking up a conversation about the adilas model and how things were working. I took a whole other page of notes, see attached. Lots of good stuff. No immediate answers, but openly talking about things and where we want things to go. Steve ended up joining us once we got part way through our meeting. Totally impromptu type meeting, but some good things.

Part way through the meeting, I merged in some code for Steve. We also talked a lot about managing starts and stops (transitions on code projects). That is tough to manage some times. Here are some of the other notes.

Good things...

- Lots of projects coming in with funding
- People want what we are doing

- Limited number of devs
- Some don't like mmj projects
- 2 guys that are designers
- Few project managers

- We don't need more normal developers... we need more mmj developers (currently)

- Smart enough to work on their own but be able to understand

- Project manager and product manager on mmj side
Steve, Dustin, Eric, Spencer, Danny, Bryan, Jonathan Wells

- Here's our problem... how can we get people in and working on those projects quickly
- Not shooting for the best model... but enough to help it work and function

- We are looking for people who are willing to play how we need them to play
- There is a different team that is working on r & d and new code

- Laser focused training to get them up to speed.
- Training for existing developers (already trained but just switching syntax)

- The core system needs to be separate from the business verticals that are built on that core

- Every business vertical needs its own team/manager to really help it play together

- Lift where you stand... take care of your space

- If you get teams that just deal with specific verticals... they become productive in their space - cover your zone

- Trying to keep developers in their flow... the transitions (starts and stops) kill and drain the energy

- Working overtime vs more people working part time - Steve used to do this in the car business

- Managing those resources and making sure we are paying for our guys

- Priorities

- We are looking for developers that know other code... and it only takes 10-20 hours to get them up to speed vs months and months or years and years. We can't train from the ground up.

- Behind the funding game... robbing peter to pay paul

- Making those hard decisions... who is critical?

- Take care of the assets that help the ship keep running

- Budgetting and setting priorities - working within those budgets - what about your family? Looking for the best bang for the buck

- High level decisions and then trickle down to what is needed

- We get enough smaller jobs... the little things start to sink the ship

- Steve's idea... work on what is being asked for and help make it look better while we are in there - bring the designers back inside to help with the current projects

- Constant process of refinement... less clicks, looks better, more automation, looking for the easy button

- Where are things headed... as a question?

- Things keep changing... because we are in a system, you get cause and effect

- If we don't redo or rework some of the pieces... this ship will sink

- We need take care of the customers but we also need to say no at times.

- We build and build and build - we may need new architecture - things have changed over the course and we need to build and/or adapt - we are not what we started out to be and/or were developed to be

- Analogy - cleaning the house... move everything out and do a deep clean or just clean one area at a time

- What is the vision of where we are going... ok, once we know, let's start moving towards that new model - how do you help spread that vision and direction?

- Breaking and pulling out the logic into their own functions (api sockets, function, objects, etc.) - the key is to isolate logic from the view of the page

- Following the processes and procedures to get to the end goal

- Where is the puck going to be... dream it up, and then trim it down if needed

- Improving from where we are at - ok, where are we going... we need to have a master vision

- By small and simple things, great things are brought to pass - little drops in a bucket, over time, they will add up

- Thinking and considering the choice of languages along the way

- Slow and steady wins the race

Danny and I looked at some queries and made a few small changes. The new queries were pulling in ecommerce transition invoices and there were a few differences between the query for quotes vs the transitional invoices. Once we got that figured out, we were good to go. Danny and I were done after the first 15 minutes.

The rest of the time, I was doing emails, uploading new code, merging in files from Bryan, and other to do list stuff.

Steve, Dustin, and Danny were on the morning meeting. Eric popped in for a bit but then bailed out. Steve had some questions about loops and doing cross corp mapping on banks for some of his aggregated stuff. Dustin had some questions about large amounts of text and how to help tie-in custom in-line database extensions for invoices. For example: long winded delivery directions or some other long (over 255 characters) string or value. We talked about using the custom_json table as an extension to help with the longer notes for invoices. We went over some of the details and how that would work and/or play through.

After that, Steve and I jumped back on his cross corp bank mapping stuff. Bryan Dayton joined the meeting and we got him squared away with a BioTrack API/integration project. 

Danny is working on project id 1759 for the mmj home page settings. We did some light code review and made a few changes. He has a new setting that allows for a switch between quotes and transitional invoices for ecommerce orders showing on the homepages. We worked on some code, logic, and flow for the new settings. It should be closer next time we meet. We made some good progress today.

Danny ended up helping with his mom and dad and wasn't able to meet. I fixed a small bug on the expense/receipt homepage dealing with showing media/content on the snow owl data tables with multiple pages. Pushed new files up to all servers.

Working with Danny on a manual code merge. For six of the files, the merge was kinda crazy and hard to follow using the merge tools. We ended up looking at things on a more general level and trying to add in the new changes on top of the old code vs trying to merge the old and new code. We went through things and made changes. After that, I pushed up the new code.

Idea from Eric - On the WordPress news and updates - What if we stored the info in application or some other semi-permanent way and then flushed and/or updated the data when the people using it did a push and/or published a new article or entry. That way it would be semi-fixed and would only be updated when it really needs it. Kinda a manual flush rate. Great idea.

Eric joined the morning meeting and had a question about some new custom JavaScript for a corporation id list builder for his cross-corp customer loyalty points. We got it working. This allows a bunch of checkboxes to be selected and the builder just pulls off the corp id number and puts it in a list.

Dustin and Danny were working together and talking about building in smart group button assignments right into the add/edit parts or items page. We chatted about ideas and options and eventually Danny left with some marching orders (new plans for the project).

After that, Dustin and Steve were working on some cart stuff and talking about the constant flow of ideas, needs, wants, and requirements. It seems like it never ends.

Met up with Danny to talk about his project of adding in assignment options to the add/edit items page for my cart favorite buttons called smart groups (aka tiered pricing). We went over some of his current direction and worked on taking things to the next steps. Mostly a mini training session while working on the project.

Part of the morning meeting with Steve and Danny. We helped Danny with his new code to add smart group button assignments (tiered pricing) to the add/edit parts or items page. Steve also gave a report of some of the things happening on his side of the fence. Lots of moving pieces. All we can do is just keep going and adjusting. That seems to be what we do, daily.

Recording notes, emails, text messages. Uploaded some files for Danny - custom labels.

Working with Danny on logic to help add/edit parts (items) and assign them to smart group buttons on the fly - through the add/edit page.

On the morning meeting with Wayne, Shari O., Steve, and myself. We ended up having Eric and Danny join us later on. The start of the meeting was dealing with new server company settings for Hostek and different tech support pieces. We got Shari O. all setup to help with any tech support pieces.

Wayne is really stepping up to help us with code, Git, bit bucket, and code management. We spent most of the meeting going back and forth with Wayne on ideas and what not.

Danny was unable meet at this time. We rescheduled for later in the day. Most of the time was spent on emails, small code changes for the QuotePro guys (sub inventory API socket stuff), tech support, and other small fixes.

Met up with Danny to go over some of his new code for assigning smart group buttons (tiered pricing rules and assignments) when adding or editing a parent part/item. It's looking good and coming along. Danny and Steve have been working on this project to help Danny with his skills and tasks. As part of our review, we had to get pretty deep into some logic, tables, sub tables, rows, and columns stuff. Most of the logic is in place, we just need to make some surface type changes.

Tons of other random projects and what not.

Phone call with Molly and Bryan going over ways to get real-time inventory counts. Including ecommerce, quotes, other secure shopping carts, and getting those details as fast as possible. We briefly talked about some of the things planned for mini conversions and being able to track the real-time quantities in bulk and keeping track of changes without updating everything. This is a big need if a 3rd party is using normal web or API sockets. Lots of calls and requests and not everything is changing all the time. It is becoming an efficiency type issue. They, 3rd parties, keep calling to get updated counts and we have to calculate and report even if nothing is changing. Too heavy of a load on the API sockets.

Small code changes for Danny and pushing up some new branches and custom labels. I also did two new pushes for Bryan on some of his code branches. After that, emails and recording notes. I also had to flip some stuff around on my calendar as most of this was unscheduled and pushed some other projects out of the way.

We jumped on a GoToMeeting and Danny and I got some code ready to go live. We were working on the add/edit smart group assignments on the add/edit parts/items page. We got it all merged in and pushed up to all servers. We also talked about a couple of other projects and processes. Trying to get things ironed out. Lots of moving pieces. Good session.

Wayne, Steve, and Danny were on when I joined this morning. They were going over Git and Bit Bucket stuff and some of the settings on the new servers.  Everything changes all the time. Towards the end of the meeting Eric had a few questions for Steve. We also talked about the adilas API sockets and how they are used. We talked about the different roads and how that translates into paths, options, traffic, and security. The current API sockets section has a few know paths. We have a demo mode, normal mode, 3rd party mode, and an internal usage mode. Each one plays slightly different.

Eric, Danny, and Shari O. were all on the morning meeting. Each were checking in and had random little questions here and there. We had to flip some user settings for Shari O. and also we went through a corporation email setup. Steve and Danny batted a few questions back and forth. Towards the end of the meeting, Steve joined the meeting.

Danny checked in earlier today. He is good and didn't need my help today. Light clean-up, emails, and prep for getting back on the cross corp invoice to PO project.