Bryan and I spent some time working on a few ecommerce changes that he was working on. There were three projects. One was show/hide a category counter. Another was an alias name for the categories out on the web. And the last one was some default part category and default normal item level images and changes.

We spent hours looking over code, running tests, and then merging and deploying. Not sure why, but the deployment (pushing files up to servers) was struggling and having issues.

Recording notes from yesterday

On a GoToMeeting session with Steve and Wayne. They were on much earlier (hours earlier). I was out of the office. Many of the servers were struggling. We didn't do anything... it was just one of those days. We could see some hack attempts, domain stuff, and huge amounts of traffic on our WordPress news and updates pages. Wayne was working his magic, Newtek (the server company) was doing their stuff, and I disabled the WordPress calls and connections. Once all of that got mixed together, we were able to stop and jump off of the group GoToMeeting session. Somewhat of a crazy day.

A bunch of the guys were on this morning. When I joined, Steve and Wayne were chatting about servers and plans. Wayne showed us how to get some stats and pull usage reports. We then moved to some questions about some data migration and questions with a specific task. Our last main topic was moving from metal (older servers and hard drives) to virtual (VPS) stuff.

Our earlier meeting ran over. Once Cory had a chance, we went over projects and quotes and what not. One of the topics brought up was testing and pushing code. We are constantly deploying new code, pushing things up, reviewing things, and making changes. It happens all of the time.

The question and/or topic was - what are the processes and protocol for doing those changes? When should they happen? And what communications should be in place either before or after new code is pushed? That gets kinda tough and we didn't have any set in stone answers. It kinda depends on what is needed, wanted, tested, how deep, how wide, and how much each project affects the core pages and/or core logic. We chatted about some ideas and options but no firm concrete decisions were made. Lots of variables.

Steve really wants to pitch some of the VPS (virtual private server) stuff to our clients. He had some questions along those lines.

Eric and I got on a meeting and chatted about cart auto printing labels settings. We decided to combine these new settings with some older settings for the cart. We then went over options for using a pop-up window, cfwindow tags (modal pop-up), and other configurations. We talked about auto printing, JavaScript, and PDF forms.

Ecommerce code review and push with Bryan. We also spent some time and lined out the next project. Bryan will be working on API sockets for the customer loyalty points (sub of the special accounts section).

Russell and I met for a couple of hours. He recorded most of the conversation on his Zoom account. The primary topic was the cart and what things need to be watched, monitored, and/or included. We spent a bunch of time listing out a few ideas and options. We drew a lot and bounced around the current existing adilas application. The cart is a huge piece of the puzzle. Lots of good conversations going back and forth about ideas, flow, needs, wants, and wouldn't it be cool if's.... good meeting.

See attached for a small list of some of the topics that we were talking about and covering.

As a small side note, Russell and his team are looking into Jira as a project tracking tool.

Steve and I were the only ones on the morning meeting today. We had some great talks about staffing and delegating. We talked about getting different people to help us in different ways. As part of our discussion, we drew some pictures and talked about getting some virtual pumps to start working and cycling through projects and tasks. As we talked, we decided that we may need a few different pumps (small teams doing certain tasks) in different spots.

We talked about Russell and how he is going to be running a small team over the summer months. That is really exciting. We are also very excited that he will actively run it, he is good at saying no or not right now, and he sets limits. We are expecting some good things coming down the pipeline due to the fact that he will be actively running and managing those pieces. The whole plan there is some maintenance and revamping some of the highest used pieces inside of adilas.

There were other topics and discussions about setting bounds, saying when (stop), different roles of builders, creatives, and checkers. We also talked about smaller tasks such as logos, watermarks, images, black box custom code, labels, etc. Some of those pieces are really small or simple. We really need to get some of those tasks handed off to others. Another huge one is emails... we get so many emails, you virtually can burry yourself in no time flat.

Keep redesigning based on pain.

We also talked about branch management stuff (git and bit bucket - code repository), being our own style, and letting the guys and gals help us decide who will carry what part of the load. Good chat. I felt better after talking and getting some things off my chest.

More brainstorming on big data and how that plays into the mix as one of the 12 main business functions that we provide. See attached for our brainstorming. You may need to scroll down to get to the big data sections.

5/5/2020: This is a bug that needs to be fixed. When you look on the po homepage, you can't see anything in the media content folder. But when you go into the PO you can see the content in there.

Back working with Russell on the cart and flow that is needed. We spent quite a bit of time today talking about barcodes and how we are currently doing that process. The idea came up that maybe we could create an aggregate (summation of sorts) for barcodes. We currently have 5 main tables where barcode are stored. That may seem random, but it's true. We may want to combine those value into one table vs doing a full text search on thousands and thousands of rows within those other tables. As a side note, barcode may be on parent items, sub inventory, my cart favorite buttons (preset code), recipe/builds (kits and groups), and even flex grid (custom tie-ins). It gets pretty deep, pretty quick.

We spent quite a bit of time talking about aggregation of data, efficiency for searches, and even down to the fracture level (future project for adilas). We talked about our current goal to fix up and update the current system, while still looking ahead to the full fracture type interface and layout. As we go forward, some of new projects will be prepping the way for where we are headed in the future. Good stuff.

Steve wanted me to go in and do some compare and update files on new VPS (fl.ianthis.adilas). Prior to doing that, I spent some time paying bills, doing emails, recording notes, and doing follow-ups.

Alan and I met for about an hour to go over and talk about code repository stuff and how we want to help manage those pieces. After that, I contacted a few of the developers and wrote an email with some of the new requirements and expectations for code sign-off and deployment processes.

Emails and small to do list stuff.

Meeting with Chuck to go over projects. He is currently working on some ecommerce email campaigns with Marisa. The email campaign has a Star Wars flair to it - kinda funny. He is also working with Russell on some of the re-vamp projects. The other thing on his plate is the presentation gallery project and getting that coded and working. He is currently working on menu systems and what not. Good report.

More emails and light tech support.

Alan reported on his current projects and then we went into a new project dealing with transition invoices. These are things like WIP (work in progress), layaways, pre-paid invoices, work orders, etc. Currently, they allow a window of time between when they start and when they end. The current window is measured in days. The new project is extending that to hours, minutes, and seconds for the transition window. We went over project details and talked about a number of key pieces including the eventual goal of running the balance sheet and P&L (income statement) over a 3D calendar of sorts. Lots of fun ideas.

Met up with Bryan and did some quick merges of smaller branches. After that, we talked about how to get some of the other things that Bryan needs to do to get all of his custom code into the master branch. We are doing a big push to gather up all of the custom code and keep it in one spot. We did some drawings and went through some scenarios of how that process would work and what tasks are needed.

On a multi-hour Zoom meeting with Russell. The first hour, he was pitching me on ideas for his new shopping cart and ideas that he has and wants to do. After that, we jumped back in on our shopping cart discussion. Lots of back and forth and even sharing drawing tools as we made notes, suggestions, and requests. Fun meeting.

5/7/2020:Add DOB field for verification on checkout. See attached quote for details.

5/7/2020: Condition specific e-commerce gram controller to allow for pre-packaged logic. See quote for more information.

5/7/2020: Tiered pricing logic for specific unit of measurement. see quote for more info.

5/7/20: log customer data during sales process. see quote for more info.

5/7/20: Dustin can fix- small project. Deals with predictive field entries in packaging.

I met with my daughter Aspen to go over some of the crazy stuff that is going on in my life, at adilas, and just in general. I'm feeling squeezed, stretched, burned out, and overloaded. This little exercise was very good and helped me put some thoughts and emotions into writing and on paper. It didn't automatically fix them, but I really feel like it helped. We bounced all over the place, but I wanted to record them for history sake. Sometimes we try to make everything smell all rosy when in reality, it can be very hard. 

We started out with - what do you do in a day? Then a week? Then a month? What are the pre-set things that happen all the time? Lots of good questions. This lead into us going over a rough schedule and talking about time and where it gets used and called for. These notes may be all over the place, but the general gist is there. Also, I did upload the scans of her notes - good meeting.

- Days off aren't really days offs, especially lately.

- Emotions: overloaded, stretched, no in the zone time, efficiency, so many transitions, nothing seems to end.

- Lots of my time gets taken up or scheduled by others. I have allowed that as a way to help the bigger picture. What do I do in the spare moments? 20-50 emails a day, 5-10 aren't that important, the rest need replies and/or action. I record notes from every meeting. I do enjoy this, but it does take time. Other times I have to track down bugs, help with servers, do maintenance, or do code sign off. Many of these are unscheduled and just expected, even if my normal schedule is full.

- The dreaded transitions - there is a transition between getting into a project, doing the project, and cleaning up or pulling out of a project. I have to switch gears all the time. You never really get deep into a zone. It is all surface stuff and transitions in/out and light doing. You don't feel super efficient or productive.

- Some of the notes that we take have some really good stuff in them. We go so fast, we hardly ever get to go back to them. If truth be told, there is a virtual gold mine in some of the notes, ideas, brainstorming, and documentation that we have gathered and/or have at our disposal. I would love to go back and learn from those things. It really is a gold mine.

- There is a pay disconnect. This exists not only for myself but also for Steve and others. We get paid about 1/3 of normal rates and wages. There is no incentive for working harder. The harder we work, the more gets piled on us. It's like digging in sand, you take some out and it just fills back in. I'm not sure of the answer, but there is a pay disconnect.

- Here are some of the tasks that I do: record notes, fix bugs, work on emergencies, servers and FTP stuff, databases, maintenance, code sign-off, planning, meetings, training, pay bills, emails, text and phone calls, decision making, consulting, code work, projects, graphics, helping others with their projects, being a cheerleader, helping to share the vision of where we are headed, quoting projects with Cory and Steve, coming up with requirements, writing new content (sales, tech support, adilas university stuff). Business meetings, advising, sounding board, talking, interviewing, customer tech support, client meetings, organize events, day dreaming, and helping the developers and designers with their projects.

- I kinda feel like I've been taken advantage of... there is a huge vacuum that needs to be filled. Way more work than any one person could possibly do. I'm willing to help but I feel that I get sucked in and loaded up because I'm willing to do it. Over time, that becomes a problem and adds stress, anxiety, and burnout. We've got to share the load.

- Some of these things won't go away and that's fine. The biggest problem is time. If you don't have time to do these things, they build up and create almost insurmountable barriers. You still have to do them, but it feels like there is no time. Problems begin to become excuses. That is at least how it begins to feel.

- Here are a few of the things that add stress (no specific order): demands, required but unscheduled tasks, multiple servers, bugs, maintenance (monotonous), transitions lessen productivity, willing to help but getting taken advantage of, vacuum, independents and lack of stability, finances and bootstrapping (fun for awhile but not for 10-20 years of that), no budgets, changing finances and funding, everything is just in time, soo much potential - it clouds your focus, and issues with clients and business verticals (say medical cannabis or other business verticals).

- Towards the end of the meeting, Aspen was asking me about plans and the future... I'm not sure what it will be... but I'd really like it to head in this direction. Going from dreams to goals to reality, getting a great core team going and in place, be able to divide and conquer, be able to focus more, have a positive outlook (vs being somewhat depressed or down), making smart investments in people and products, get the servers stabilized and snappy, eventually do a full product rewrite, and go from a transitional system (current model) into more of an aggregated or summarized type system. I don't have to build the whole thing, I just want to help plan it and teach it and share the vision of where we are headed. Lots of good options.

A bunch of the guys checked in and then bailed out. Lots of general to do list stuff. Wayne joined us and did some Minecraft show and tell (his kids and Steve's kid were having fun seeing all of Wayne's stuff). That was really fun. We also got about 50 files from Steve merged into the master branch. Good stuff. Making progress.

Brainstorming on big data and how that plays into the big picture for businesses.

5/8/20: Special category page for metrc users
Auto set u of m
Category settings on one page

See quote for more info and client doc

5/8/2020: Add Product Type field to Parent  See attached for more information

5/8/20: Add the sales QTY and Price per unit sold/ see attached.

5/8/2020: 

1. Add fields for Tiered Pricing ( see attached for more info)

5/8/20: Bryan will take a couple hours and fix this.

This endpoint we are testing out is the “last_edit_date” field, within the getWebInventoryByEditDate 

5/8/20: Alan helped me with a few questions with the API recently for Headset. I am not sure which developer knows this call best -

{
  "RET_SECOND_MESSAGE": "Use your back button and try again.",
  "RET_STATUS": "noPart",
  "RET_MAIN_MESSAGE": "Unable to find the part number that you requested.",
  "RET_TYPE": "error"
}

The only idea I had was that these parts are set to "hide on web". 

Attached is a list of products from one corp, although they are reporting a list for all corps. I did confirm that all of these items are set to "hide on web"

5/8/20: Brandon can knock this out. Will help with word press api calls overwhelming server.

Eric popped in and we went over his current process for the auto print labels. We did some light debugging and talked about direction from there.

Going over quotes and projects. We are getting better and better at this. Good progress.

Meeting with Molly to go over some custom gram trackers. She has found a small bug between the restore to cart (quote back into the cart) and the custom gram trackers. We took some notes and will do some research on that. Towards the end of the call, there was a lot of talk about API sockets, WordPress, and Molly's new product that crosses adilas with Woo commerce.

Touching base with Calvin about custom code and potential on some servers and upgrades. Mostly just touching base and chatting.

We had disabled WordPress on our news and updates due to misuse and digital hack attempts. We reinstated it in certain areas. Limited and controlled vs all snow owl footers and auto feeds. We still want it, it was just being abused. 

A bunch of guys were on the meeting when I joined. Wayne had a number of questions and requests for both Steve and I. We are all working hard on the servers and trying to get things to be tighter and more stable. He wants us to go through the corp-wide settings (hundreds of fields and settings) and put them into objects vs normal database columns. This will help with storage and database engine stuff. Wayne brought up a couple of other errors and we got different parties looking into the different places. Trying to divide and conquer.

Eric touched base with Steve and I and we chatted about some plans. Lots of moving pieces and it doesn't seem to stop. That seems to be our lot in life right now. Eric had me start looking into some merge branches that he needed.

More work on a couple of branches. Eric was removing files, doing some clean-up, and code changes while I was doing emails and other to do list stuff. We merged in one of the branches and got the other branch going in the right direction. It had a few extra files that weren't needed.

Meeting with Cory, Steve, and Spencer. Steve came in a little bit late, so we started out just doing some quotes. Once Steve got on, we moved over to Spencer's stuff and looked at his responsive - one-pager - cart project. Also, Spencer told us that he would be interested in working more with us on internal Adobe ColdFusion projects. That is really good news and we are excited about that.

See attached for the mobile ready responsive cart stuff. I didn't get all of the pieces, but enough to show the proof of concept. After that meeting finished up, Steve, Cory, and I talked about other projects and things that are on the radar (up and coming pieces). We also talked about the developers and who is going to work on each project.

5/11/2020: Auto print labels part two would allow settings to cascade to normal bulk print page. Currently only pointed to one page. 

8/26: Request for Square as payment type for CBD.

8/14/19: Request for MTrack as payment type. Client has started using a new debit card and wants a payment that denotes the name of the card.

Brandon handles this. Pushes to data0 and copies to the rest of the servers. Steve can also do this.

Request for these two payment types on 8/12/19. Have heard of other requests in the past. 

5/11/2020: Brandon brought news and updates back online but it won't show on feeder unless click on+ more. Was too slow and hard on server. Need to bring it back in a different way.

5/11/2020: Currently sub attributes act funny when you choose the setting: show subs sell subs. Could be something simple. Need to do some internal gathering of info to determine what is happening and what the fix would entail.

5/11/2020: This project is for the research portion of determining the code and logic of the gram tracker and why it isn't performing a certain way during restore to cart.

Next project will be the fixing of this issue.

Emails and random small stuff. I did add some screenshots from the 2nd email in the Star Wars ecommerce email campaign to the gallery.

Cory,

Thanks for the extra information!

We are aware of the intermittent 500/503 errors that you are experiencing. Our technology team has also identified the issue causing this error. We expect a resolution shortly and will follow up once we have confirmation that the issue is fully resolved. 

​

In the meantime, please retry any transaction that receives a 500/503 response until this issue is resolved.

Thank you so much, and reference ticket #446893 for your records.

Have a good day,

 

Andrew Magnemi

API Team

Metrc, LLC

Your ticket number is 446893

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.

Merged in some files. Wayne was talking with Steve and I about objects, classes, sub classes - tons of coding stuff and concepts. He is working on some new code to help with tons of settings. We are seeing setting on 4 different main levels. They are corp-wide (per world), group (12 main players such as customers, invoices, PO's, items, etc.), page level settings, and user level settings. Anyways, Wayne was showing us some ideas that he had to create setting objects and then sub divide them by group types. Some great ideas.

We talked about WordPress and how we are using it. We currently use it to help with news and updates and spreading the word about new changes, updates, and features. Wayne was showing us a possible replacement called Hugo https://gohugo.io - we will take a look and see what we think. Instead of PHP, MySQL, and API socket calls, the Hugo site is really good at basic static web sites.

These were some of our planned topics of discussion. We somewhat got to them, but mostly it was Wayne talking with Steve, myself, Alan, and Russell and filling us in on his dream of where things are going.

What the plan for migration?

Who will take care of what?

Who else needs to be brought in to help with this? Alan had the idea of each person goes in and beats up on stuff that they know about and/or built. We don't want overlap, but we do want to test these new environments. Photos, media/content, ecommerce, carts, CRM stuff, elements of time, E/R's, deposits, 12 main players, API sockets, 3rd party integration, settings, permissions, database updates, migrating data and images over to new servers.

What is the timing for this?

---------

Notes from our real meeting:

Wayne was doing some training for Russell and Alan. He is somewhat leading the way and then Alan and others are following suite. Some good direction. Both Russell and Alan were asking questions and they were having a good discussion. Steve and I were somewhat on the outside of the whole meeting.

They were talking about ways of setting up dynamic settings, database storage options, server configuration, clusters, and prepping things for moves in that direction. Pretty cool stuff.

Wayne is really into Docker images and showed the guys some stuff about that and how he is using it. One of the topics here was dealing with setting up new servers, development environments, and onboarding new team members. The current process is quite slow with multiple manual steps.

One of my takeaways from the meeting was - Get out of the way. Help to lead and guide them but let them run. Use the talents of those around you.

More talks about databases, engines, and clusters. They are setting things up to go faster and further.

Quote from Wayne - "We do custom like no other". It truly is a custom solution and we are willing and able to play in that direction.

Shannon joined the meeting right at 11 am, our original start time. Our other meetings went over so she ended up on the meeting for an hour just listening to techy database stuff and other developers reporting on projects. We weren't able to do any new marketing content. We will hit it again on Thursday.

After Wayne finished up with the guys, Alan gave Steve and I a report on what he is working on. He is working on new enhancements to the Metrc homepage (state compliance stuff). Some of the new changes show advanced states and status options for the invoices being synced with the outside state tracking system. That will really help. We really wish that Metrc would provide responses back with their API socket calls. That has sort of been a pain point.

Steve and Alan made some small decisions about flow and the code. After that, Steve had questions about the BioTrack API sockets. That is another state compliance system. Not only are we building our own solution, we have to interface with multiple outside 3rd parties. That really makes it tough some times.

6/2/2020: Assigned to Bryan.

5/12/2020:surface BT apis for quote pro. See attached quote for more information

Recording notes. Merging in files, emails, and follow-ups.

Great little meeting with Jonathan Wells. We had Steve, Cory, Jonathan, and myself on the meeting. Cory was only able to stay for the first little bit. The main subject was dealing with a dashboard of sorts and mock-ups and samples in the fracture interface (future project for adilas).

Super cool mock-ups, tons of potential. We are going to be pitching some of these mock-ups to current and perspective clients. See attached for a number of screenshots.

Some other topics that we discussed are: investments, prototypes, reverse shopping carts (brining products into the system), global master lists, virtual catalogs and being able to copy values from the catalogs, predictive buying and selling trends, thresholds with maxes and mins, and other topics. Good stuff.

Working with Eric on his auto print POS (point of sale) labels. Added in some new settings for the cart and did some testing both locally and live. Pushed new pages to all servers.

After Eric and I got done, I went in and added some notes and images for earlier meetings today. Here is link to some fun dashboard ideas and concepts.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=6368 - dashboard overview mock-ups

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.

Chuck wasn't feeling well so we had a quick 10 minute meeting and called it good. He is doing some mock-ups for Bill (a client) and working with Russell and Marisa on different projects. Spent the rest of the time working on small little projects and to do list items.

Met with Alan briefly. We chatted quite a bit yesterday. We touched base on a few things and wrapped it up pretty quick. I then spent some time working on some groupings to help Wayne with the settings on the corporations table. Too many settings and we need to start grouping them.

Worked on grouping the database fields on the corporations table. There are between 350 and 400 fields (all settings). Broke the fields into groups. We will end up storing those settings in groups such as: main info groups, look and feel groups, ecommerce groups, invoice groups, customer groups, payroll groups, etc. All of the settings have a grouping or a note about special instructions.

Cory showed me a random math error between the original price, the taxes, and the rounding error. Pretty deep. I took some notes and then logged in and tried it. I worked for awhile on doing manual calculations and checking out the different pieces. Lots of notes. Cory was on for the first 20+ minutes, then I was just working on it on my own. I made some progress, but no solution yet.

Bryan had some questions about application scope variables vs normal page scope variables. We got things fixed and he headed on his way. After that, I returned to the math bug that Cory showed me earlier today.

Towards the end of the day, got a call from Russell. He was saying thank you to me for helping to pioneer some of the original pieces of adilas. We all know that they need to keep progressing, but it was nice to hear a thank you every once in awhile.

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.

Shari O., Steve, and I were on the meeting for the first little bit. We had some good conversations about where things are headed and likes and dislikes of some of the options that we have. Shari O. has always been a great helper and a core part of the team. Eventually we (Shari and I) went over some email stuff but the first half of this meeting was some great open conversation about direction, team players, and wishes and dreams on how things get structured. Here are few things that I pulled out of the meeting.

- How big do we want to be? How flexible or rigid do we want to be? What personnel/staffing would help those dynamics? And where do each of us want to fit into that mix? Great questions. We chatted and did some drawing to illustrate certain points and pieces.

- Our current trend is more towards an open model. We just feel more comfortable there.

- Shari O. really wants to get some good customer care and proactive helping of our clients. That has been a big goal of hers for years.

- We also went over email settings, auto forwarding for our clients, and how best to setup custom email addresses to lessen our loads and make our customers more responsive and productive.

Nice meeting with a mix of all kinds of topics. Towards the end, Shannon joined the meeting and was able to chat with Mrs. Shari O. for a bit. That was good.

Shannon and I worked on and did a bunch of brainstorming on the business role of ecommerce and how that business function ties into the bigger picture. It's huge, we were just trying to capture some of the pieces and ideas.

5/14/20:Currently when you add a new payment type, it defaults to checked. This confuses clients when new payment types appear when they are doing sales.

Zoom with Hypur to see about adding to the e-commerce payments allowed

Spent some time recording notes from this morning. Then back on a deep math quest to help debug some rounding errors on the quote to cart process. I ended up adding some hidden dumps of the data and variables if a developer uses a certain keyword or number pattern. Kinda like a lock and key.

Bryan joined the meeting and had some questions. He was debugging some API socket connections and just needed some direction. It ended up being a small syntax issue.

Going over quote and projects. One of them was dealing with a client's request to delete some data due to the sell of a company and the person wanting their old data but not the new owner's data. We talked about options of physically deleting the data, voiding out the data, or virtually flipping the data to a different corporation where nobody would see it or touch it. Pros and cons and we will get back with the client.

The other topics were dealing with new and custom reports. Lots of requests for daily breakdown and better grouping of the data vs line by line or invoice by invoice. Basically a small call out for better aggregated data and reporting. The data is all there, it just makes it hard if you have to pull multiple reports to get it. 

Great little meeting. We met with John and talked about a bunch of different options. Brandon has some notes from the meeting. We asked about his current experience with doing adilas development, where he wants to go, what he would like to do, etc. Fun meeting. We determined that he would like to work under Russell and be on that small developer team. He anticipates that he could have up to 10 hours a week to help with code, backend, frontend, and UI/UX type projects. Sounds good to us and we'll keep moving forward.

Trying to catch-up on emails. Over 80+ new emails in my inbox this morning. Steve needed a merge with the master code branch. I spent some time working on that.

As a side note, one of the new emails was email 3 for the Star Wars - adilas ecommerce email campaign. I have copied in some screenshots from the email. Chuck and Marisa are having fun and I think it is fun.

Dustin and I got together and did a large merge with the master code branch. There were 35 files, some of which had some major changes. We originally only had about an hour scheduled. It took 2.5 hours to finish everything up. Pretty big. Light training along the way.

Emails, pushing files, and checking on a bug reported by Wayne (division by zero on a multi-corp report).

Talking about project management, custom reports, custom links and buttons to those reports, and communication channels. Some of our main resources are time, funding, and talent/skills.

Both Cory and Russell were throwing ideas back and forth. Good conversations. Light show and tell about who's on what and what is happening. Both Cory and Russell were talking about setting up a set weekly meeting.

Lots of talks about new data tables and functionality that is both wanted and needed. Big data and huge amounts of records... trying to guide our users to the best tools for the job. Helping to ask them questions and then solve those options. Definite flavor of aggregated data and quick summaries and counts.

Our clients really want to be able to experience their own data in their own way.

Big data is big data... If you are viewing things on a computer or a phone, you still need to scroll. How can we help with that process. We were talking about sticky columns, sticky column headings, smooth scrolling, quick access to filters and sorts, and mobile responsive ideas, options and things. Freeze panes, panels, special windows, etc.

Some people don't like change... but some people really do like change and it is exciting. We may need to play both sides of that. Surprises and forced changes sometimes come across the wrong way. It all comes back to settings. We will try to provide as much backward compatibility but still help push the market and the experience on and on.

There were also talks about permissions, levels, and what data gets provided for each role and/or level. Soo many needs and everybody needs something different. All part of the game.

We even got into some look and feel concepts and where we want to go. There was also some talk about scheduling some of the releases of the new products and features.

Bryan and I did a session on a couple of projects. The main one that we were dealing with was customer loyalty points via the outside or external API sockets. We have to be able to pull info, rules, settings, summaries, add transactions, edit transactions, apply or redeem payments, etc. Fairly deep. Good stuff. We still have a little bit of clean-up, but getting really close.

Alan and the guys were talking about all kinds of stuff when I joined. He is using threads, grouping on line items and reports, and re-syncing with Metrc (a state level compliance system). All kinds of good stuff.

Eric had a number of ideas and questions about a cross-corp wholesale cart. We need to be able to bulk transfer between corps, not include taxes, not discount things, possible mark-ups, and even transferring data into a holding container of sorts vs an immediate transfer of the goods. Lots of talks about the wholesale cart and what that might look like. As a side note, they were even talking about accounting options for selling between corps.

Flipping some expenses and re-voiding certain pieces for a client.

Talking about our model as far as the main adilas team. We had Shari O. and Steve on with us. We really want to keep building small teams of people vs individual or solo teams. We also need to spread the load and in order to keep building. It is too much for just one person.

Brainstorming on ecommerce. See attached for some of our brainstorming ideas.

Extension of your inventory system
Configure everything
Customers
Ordering and fulfillment
Shipping
Merchant processing
Emails and notifications
Special features
API sockets & extensions
Custom - no problem
Keep building for the future

Spring Big Meeting

#3 priority for client. See also project 1507 (metrc api for transfers) this is the workaround in adilas until they open up the api.

As of 5/25/2020: Holding off on this project for now due to funding.

Adding 4 columns to payee permissions report: corp id, email address, status, and last log in date and time.

https://data0.adilas.biz/top_secret/custom/reports_payee_permissions.cfm

5/19/2020: small bug fix that needs to be done by someone. If you put in the same check number, it checks it.

People should order checks in different sequence.

Shows a warning at the end, delay the message until the end.

This is a link to a promotional video that Marisa Shaw did for adilas. It included the avatar dog "adilas". Pretty funny and well done.

https://youtu.be/l0roAYKiWPo - 3 minute video on what adilas does

Scanning and recording some notes from a meeting with my daughter Aspen. She helped me out back on 5/7/20 and we took a few pages of handwritten notes. Great meeting. Recording some of those notes.

Got on a GoToMeeting with Shari O. The subject was dealing with email accounts, settings, and how to best handle some of those pieces. Here are a couple notes:

- Being able to send emails have been around for quite awhile. Here are some of the project rounds as I see them. 1. Can I do it? Yes, it is done and we can send emails for invoices, quotes, statements, and custom. 2. How well does that work? This is where we are at right now. We could really use more histories, logging, error handling, notifications,  Wayne's touch, Russell's touch, etc. 3. The third round might be full automation and being able skip adilas all together to get the emails and communications going.

- We talked about outsourcing some of the big and small projects and pieces. There are times that we really need more manpower and skills.

- There are waves that pass over all of us. If we watch out for each other, we can help de-stress and transfer the load as needed.

- Shari O. and I talked about the jelly fish model - dealing with how the adilas model, tasks, and talent pool is constructed. See attached for a rough drawing.

Eric and I met and talked about options for a wholesale cart. We talked about the existing wholesale cart for stock/units, the internal transfer invoices, and other invoice types. We ended up talking about a new table to record wholesale customer settings and then play off of the special forks (conditional if statements) in the code that already exist. Good meeting. Eric will keep pushing on that and make a pitch to Steve and the client who wanted that feature.

Our meeting started and we cascaded some new API socket documentation around to different servers. Bryan finished up 5 new API sockets to help with special accounts and loyalty points. After that we talked about a different project that would allow ecommerce invoices to be put on account. Prior to this, ecommerce required that full payment needed to be made before creating an ecommerce invoice. Under the surface, the real reason for this change is a quote doesn't affect inventory but a real invoice does affect inventory.

Quiet morning. I was on the meeting all by myself. I spent time going over scans and notes from 5/7/20 and a meeting between myself and Aspen (my daughter). She was acting as a consultant and sounding board of sorts. Recording notes and thoughts from that meeting.

Chuck and I had a good meeting. We went over some existing projects and progress reports on each of those. Chuck has been working with Marisa on email campaigns, ecommerce training, and prep for a meeting to show the camping stuff (wanderways website and campground tool).

We went over some font awesome stuff and then rolled into a project that he is working on for Steve. The new project is a custom dashboard for employees and special HR type functions. We did some training on black box stuff and pulling in images and photos to the new custom page.

Weekly check in from Alan. He joined earlier, but I was still working with Chuck. We got back together around 11:30 am. Alan reported on his current projects and showed me some new code that he is working on. He does a great job re-factoring and re-using different code blocks. He showed me some new stuff dealing with objects, DAO's (data access objects), services, and database triggers. All of those pieces are fairly advanced and above the ability of some of the other developers. Nice update.

Emails, tech support, and recording notes.

Chuck and I were working on a custom flex grid project for a client. We mapped out 11 different flex grid fields and did some backend database clean-up on his local environment. We then started to pull in the data to Chuck's custom output page. Wire up job and doing some training along the way.

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.

There were a bunch of guys on this morning with Steve when I got on the meeting. They were chatting and helping each other out with questions and responses. Good stuff. Eventually, Eric, Steve, and I were the only ones left on the meeting. We spent the rest of the meeting talking about sub attributes for customers and how that would look. Lots of talk about real in-line database extensions and how those might be able to play in to the mix.

For a current project, we pitched and threw around 3 different proposals. Option 1 was to leave the core customers table alone and add a new wholesale customers table with options and settings. Option 2 was to expand the main core customers table with some new columns to hold the data. Option 3 was to build out "flex attributes" (aka real in-line database extensions for customers. This would allow our users to add whatever fields they needed to customer with specific data types (text, drop-downs, numerics, decimals, or dates). Great conversation.

Eric, Steve, and I spent a bunch of time writing down ideas, notes, and drawing diagrams of how things would look and/or function. I will attached our notes from the meeting, but the main thing was dealing with how to create a super generic table to hold the sub or flex attributes for customers, PO's, invoices, expense/receipts, elements of time, users, vendor, stock/units, etc. All of the 12 main system players.

Lots of talks about core values vs the new dynamic flex attributes. We also talked about auto creation, auto setup, and mapping to help make these new values work. Exciting stuff.

Brainstorming with Shannon on concepts of the business function of ecommerce and how that plays in. Working on an outline for the presentation gallery project (future sales tool). This is the last of 12 major business functions that we have been outlining. See attached for the current outline. Still a work in progress but coming along.

Emails, phone calls, texts, and recording notes.

Jonathan Wells (designer) was on the meeting with Steve and I. He had some questions... the deeper we get, the more we really need to get all the way out to mini conversions. It is becoming more and more plain to see. Our users really want to see their quantities, units of measure, and weight equivalence values. We can fake it right now, but it really needs to go deeper for some of our reporting. Nothing new, we already know about this, we just are seeing the need for mini conversions being pushed forward. It is gaining momentum and steam (warming up and getting hot).

Steve and I looked into the restore quote to cart functionality for Molly. We looked over a number of core pages and also found some custom files. Nothing jumped out at us, everything looked pretty normal. We determined to do some testing with and without the custom code to see if that changed anything. Steve will do that later on based on his time.

The last hour of so was spent with Steve and Brandon going over their business model, going over ideas, and lightly pitching ideas back and forth about adilas as a trust, profit sharing, coop type options, and other business decisions. Trying to figure out the best approach and how we would handle investments, employees, ownership options, etc. Good meeting.

Today is Memorial Day. Pretty quite on this front today. Steve and I were the only ones on the meeting this morning. We ended up chatting about enterprise and aggregated systems. We need to make sure that the traffic and flow of data can go in both directions - up and down (to master and from master). We also talked about tons of other topics and lessons learned. We are constantly refining our model, what we offer, and how we do things. Just part of the game.

Some of the topics that we were chatting about were things like:

- Flex bubbles and concepts of the data assembly line - trying to keep operations and accounting running parallel and allowing flex to enter the equation as needed. Bring things back together with checkpoints, permissions, dates, and known phases. 3D depth, stacking, and layering to record and let the story play out. Lots of data assembly line concepts.

- Helping our developers move from the snow owl theme towards fracture. We are currently working on a look and feel them of snow owl (just a name for the current version and look and feel). What we really want to do is keep building in such a way as to get to a future project called fracture. This is where everything starts breaking into smaller and smaller pieces that may be configurable and controllable. The whole thing keeps sub dividing. So, we plan on accepting that and are planning on capitalizing on that natural occurrence of things splitting into smaller and smaller pieces. Everything is headed into sub level of controls.

- As we move forward, what would that take and how does it roll out (current to future projects)? Trying to get our minds about how this whole thing will unfold.

- As part of the conversation, we were talking about how accounting and CPA's help keep things together, once operations have taken place. Eventually, everything ends up as accounting. If we can help in that process (from operations to accounting), that helps companies become more sticky (wanting and needing our products and services) through their accounting and CPA's.

- A big part of our job is pioneering the vision and bringing both operations and accounting together. It takes a lot of hard work, ideas, good data, and lots of dreams. Steve and I love the dreaming and brainstorming and problem solving parts of the puzzle. Good stuff.

- Once you get some motion and momentum, it seems to be easier to go in certain directions. Part of Steve and I's job is to help get things started and get that motion and/or momentum going in a good direction.

- We need to give Wayne some more power in order to do everything that he needs to. He is doing a great job.

- This is silly, but we went to the corp administrator page and talked about some older pricing and verbiage that was on that page. Here is some text from there. Just for fun...

Submitting Ideas, Custom Code & Developer Rates

The adilas staff are constantly adding to and improving our business platform. We love your feedback and ideas! Just email us or let one of our reps know if you have any needs or suggestions. Many of your ideas may be incorporated for free and then passed on to all other users and companies free of charge. This is how we share the love and give back to the community. A huge portion of the adilas platform has evolved from great ideas from different users like yourself.

When you submit an idea or suggestion it will go into the general adilas "to do list". We then pull from this list according to priority, time, and needs. There are no promises as to the specific timelines or release dates for when or if ideas will be used. All changes we make that come from our general to do list are completely free to everyone.

Entering the "custom" or "priority" level...

If you have a specific idea that needs priority or needs to be custom-built, just let us know! At this level, we do charge for these changes.

Here is how things work in the custom code arena... Adilas, LLC. retains all rights and possession of code, assets, functions, and features (including custom-built code). Your data is yours, but all of the code assets and code libraries belong to Adilas, LLC. As much as possible, it is adilas's goal to reuse, resell, and permission out new projects and features to other adilas users. This becomes part of the free upgrade process that all adilas users benefit from.

We use the following as our general guideline on rates and fees:

• Submitting An Idea or Suggestion - Absolutely Free! :)

• Hourly College Intern Time - Quote or $35 to $50/hour. This could be for either design or development work. This is great option that both saves you money and helps one or more college interns get the skills to pay the bills. Adilas interns work directly with the main adilas staff to get the work and projects done.

• Hourly Adilas Development Time - Quote or $100/hour.

• Custom Interfaces - Quote or $100 and up. A simple page with 10-15 buttons will run about $100. If it gets more involved, we'll give you a quote that fits your needs. We also allow you to literally "dream it up, and we'll help you wire it up!" We are happy to work with paper and pencil mock-ups, sketches, digital diagrams, or schematics, and even designs from 3rd party designers. No problem, we'll help you wire it up!

• Custom Data Imports (parts, inventory items, customers, vendors, etc.)
Quote or $100/hour. Most imports, from Microsoft Excel, come in between $100 and $200. You provide the data file.

• Simple Custom Documents or Forms
This could be any simple Adobe PDF file, custom report, MS Excel document, or CSV file. - Quote or $100/document. Advanced documents or processes are by quote only.

• Full Day of Development Time
Block of Time (at least 6 hours and up to a max of 8 hours) - Quote or $500/day. Must schedule with developers and get approval.

• Full Week of Development Time
Block of Time - 35-50 Hours - Quote or $3,000/week. Must schedule with developers and get approval.

• Full Week with a Developer Onsite
Up to 6 days at a time - Monday/Saturday - Quote Required - $5,000/week. Must schedule with developers and get approval. This option may also include a place to stay and airfare if needed.

• Full Project Match
Quote Only - We figure out a project together and Adilas, LLC. will match and/or exceed what you and/or others put into the project (possible group effort). We, at adilas, need to see a pretty good value in the projects or features that take this route. :)

These rates and fees are "ballpark" only... They are provided to help you get an idea of what is possible and to help you determine rough budgets. If you can dream it up, we'll give it a go and see what kind of magic we can do... We love this kinda stuff! Yee Haw! :)

As a reminder, the only required fees and costs to use adilas.biz are your normal monthly fees to use the system. All other costs are done at your consent to play in the custom code or priority arena.

Copyright © 2020 powered by adilas.biz

Both Eric and Wayne popped in. The main topic was going to be going over a new feature called flex attributes (similar to sub inventory or parent attributes, but for all of the main 12 players inside of adilas). However, we started in and both Wayne and Eric were pushing us to go in a more normal, standard, or data normalization type approach. We still may end up coming back to the flex attributes, but for this project, we can do it without getting super deep into the flex attributes and full on in-line database extensions.

Very interesting... there is a progression of how things get developed and how things progress. Some of the guys are trying to help us take smaller bites and bring quick value that gets finished quicker and allows for frequent deliveries that build on the prior pieces. Sometimes we dive deep and take everybody else with us.

Phone calls, emails, and tech support. I ended up on a phone call with Russell to go over some things, payments, questions, and project management stuff. He is doing great, but feeling some of the weight of project management vs just doing your own simple projects (helping others along the way). Russell is very good at catching and then sharing that vision. That is awesome. We are excited to see what he and his team come up with.

5/25/2020: see attached quote and documentation

Emails, recording notes, and research.

Steve and I were the only ones on the morning meeting this morning. We started out just doing our own things and working on small projects. After a little bit, we ended up talking about some of the challenged of doing custom code verses doing more specific and/or rigid specs. We have a lot of concepts and dreams that play into what we do. That is really hard for certain developers (black and white thinkers) to grasp. We sometimes code to the flexibility and potential of a project vs the exact need or output. We like that, but it does make it difficult at time.

This whole conversation started due to a report that a developer called me yesterday and said that he had decided to take a certain project in a different way than what was planned. Originally we had proposed three options and were leaning towards options number three. Unbeknownst to me and the other developer, Steve and Cory had quoted a few other projects based on the fact that certain prep pieces would be in place from this other project. To us, the other developer and I, we could go any direction that we wanted (we had multiple options in front of us). We didn't know about the other plans. This conversation between Steve and I got us talking about direction and vision and who is managing all of this... it gets pretty deep, pretty quick.

We talked about all of the different phases and how things either need to and should flow through certain processes. We talked about R&D, look and feel, mock-ups, project management, wire-ups, custom code, database design, servers and deployment. It gets pretty deep.

As a side note, one of my new emails was email 4 for the Star Wars - adilas ecommerce email campaign. I have copied in some screenshots from the email. Once again, both Chuck and Marisa are having fun.

Meeting and going over Cory's tick list. This included questions on projects, update reports, new projects, and quotes. She is doing a great job. Here are a few notes that I wrote down during the meeting. Just trying to record things.

- On add/edit parts (general inventory items), we may not want to allow updates on part categories. That could have lots of cause and effects - both upstream and downstream

- Currently there is a duplicate check error message on certain payables sections. That message is good and well, but we may need to move it to the end of the process. We had some reports where that error message (even through it is good) stopped another process from completing correctly. We may need to just delay that message until the end of the process vs as soon as it is encountered.

- We also spent some time talking about projects and which ones are deep, shallow, or somewhere in the middle.

More brainstorming on ecommerce and how it playing into one of the 12 main business functions that we are trying to do and help with. See attached for the outline for the presentation gallery project. Most of the session today was refining things and getting the ecommerce section more organized. I think we have about one session left on the business functions stuff.

5/26/2020: Database change, validation, not super tough.

5/26/2020:Brandon approved adding a switch on the API to flip between showing web only and all inventory

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

Wrapping up a phase of Chuck's CSI project. We are going to be transitioning it into a new phase and pass it on to another backend developer. Chuck has taken it about as far as he could. As a side note, each developer has strengths and weaknesses (not bad things, just strengths and weaknesses). We need to had this project off to another developer. If not, poor Chuck will literally be on the side and not knowing what to do and what comes next. It goes beyond the reach and/or scope of the skills and talents currently available. More good stuff to come but currently maxed out.

Chuck will be going back and working on some other projects like the presentation gallery (sales tool and visual outline project) as well as some other projects that have been assigned.

We finished up our meeting and got some code and notes ready to pass on to the next developer who will run with the wire-up portion of the project.

Paying bills and small to do list stuff.

Working on some code management stuff and project management for the CSI project. That project is a custom employee/user profile page that deals with custom photo scanning to check employee temperatures when they come in for work. Chuck and I finished up his part of that project yesterday and now we just need a backend developer to help with the rest of the wire-up job.

After that, I spent some time recording notes from yesterday. Transferring post-it note scribbles into elements of time (developer's notebook entries).

Going over projects and touching base with Chuck. He is working on the new corp-wide settings pages, a thing called "dev docs" - new section that deals with code snippets, style guides, naming convention, and other standard type stuff. We chatted for awhile and talked about WanderWays (camp adilas project) and other current and upcoming projects.

Weekly check in with Alan. We went over a few of his projects and what not. He is just about ready to launch some new code for Metrc (state tracking system stuff). That has been a long time coming. He will also be working with Russell and his team on pulling out and refactoring code that deals with the shopping cart here soon. That is still building up, but on the horizon. The other project that he is working on is the QTI project (between quote, transition invoice, and normal invoice). This deals with taking the transition invoice window out to dates and times vs just days without the time block to help with the transitional invoices part.

We also briefly chatted about work loads, pressure, and how things are going - generally. Good report.

After our meeting, I went back and recorded more notes from yesterday's meetings and such. Over half an hour of this block was recording notes.

5/27/2020: Client paying downpayment to get in queue. Wants it to work by 7/1/2020, but we are pretty far out in our queue.

1. We would need to know the exact format - columns, numbers, and layout.

>> 2. I've included a raw sample of what it looks like. If you look, you
>> will see that there are no column headings and tons of blank data (back to back commas) 3. A CSV (comma separated values) file has data separated by commas. For example: column 1,column 2, column

3,,,, - we would need to know what every possible column needs to be mapped to. In the example, we can see data in columns 1-3, however columns 4-7 are blank. We still need to know what would go there if there was data.
>>

4. Once we know the real format, we can then build a tool to pull in the data, parse it (break it apart into usable pieces), and then do bulk inserts into the database.

I got a reminder email about the ecommerce training session tomorrow. See attached for some quick screenshots.

Phone calls, text messages, emails, and working on the duplicate expense/receipt project. I got it finished and merged into master. New files were pushed up to all servers.

Working on tracking down a small rounding bug. Looking for 1/2 a cent in a certain scenario. Needle in the haystack routine. Made some notes where I left off. Going through code line by line.

Six of us were on the morning meeting today. Eric started out with some questions about the wholesale customer and cross corp inventory transfers. After that, Wayne had a number of questions about servers and where things are going. He is doing great and getting some of the old servers moved over from older dedicated boxes (spinning on metal drives) into virtual servers (VPS environments) and using SSD (solid state drives).

As part of the conversation, Wayne was pitching test driven design and even charging some of our clients who really want to be able to check or test key functionality points with their own automated tests. This would be an extra cost, but it would also give the companies a level of comfort that they could run some automated tests to make sure all systems were go and good for whatever their reasons are. This would be especially true for custom functionality and custom features and processes.

We ended up talking about the need to pay for additional services... if you want it, you just have to pay for it. There is also a side of that that allows us to be paid to help enhance the system based on needs. That is always a good strategy.

Other subjects were dealing with real test case scenarios, what test driven design means, end of the life cycle (being supported) for Adobe Flash, and planning for the future. As a side note, I'm really sad to see Flash going away. We have used Flash as a part of our development going way back. Currently, we have 4-5 major Flash widgets inside of adilas. We have all of the my cart favorite buttons (user defined point of sale buttons), the adilas barcode generator (free barcode and label program for adilas users), and the adilas check write application. Their are also a number of fun navigation options for main homepages that use Flash. We will miss it as an option.

One of the last subjects of the meeting was between Dustin and Steve. They were going over API socket information dealing with Metrc (state compliance and tracking system for medical marijuana and cannabis regulations). There is constant needs there and it almost feels like we have to code two different systems to keep up with the changes. We also have a number of clients who really use that feature and rely on us to help them keep synced up and fully in compliance. Quite the balancing act.

Special training event put on by Marisa Shaw, from marketing and sales. She did a great job. I wish more people had participated but she did a knock out job and we covered tons of ground dealing with adilas ecommerce. She did record the event, so I'm hopeful to get a copy of the recording.

Here is a light overview:

She started out going into the main adilas system and showing how a good setup inside of adilas reflects and translates to a good ecommerce setup outside of adilas (customer facing ecommerce area). Marisa went through corp-wide settings, customers, invoices, items, locations, settings, permissions, discounts, photos, vendors, bulk tools, special reports, exports, taxes, etc. I really enjoyed it. Very logical approach and showed tons of examples of changes on one side and how that translated to changes on the ecommerce side of the puzzle. Super cool.

There is a follow-up, second training session, tomorrow from 10 am to 12 noon. That should be good. She will be going more into advanced settings and options.

Review of projects on a Zoom meeting

12/18/20: Adding $700.
11/20/2020: Adding $1600 to project. Total=$6226.90
10/21/20: 10/9/20: As of today: 4626.90. This includes work on projects #1764 and 1765. These two projects have another 31 hours ($3100) allocated to them so still within budget. ($5800)

9/25/2020: Fix/add sort option in e-commerce (currently doesn't work).

Some other settings that Steve mentioned and is trying to get money for: Notes: you can leave it blank so the customer can enter a note, or there can be a drop down for them to choose from. It would be nice to have both.

5/28/2020: sent to client to complete their project scope.

5/28/2020: Complete the wire up and dynamic selection of customers to buttons

5/28/2020: Build out api connection with metrc to create a new template

Recording notes and then moving into more chasing down a rounding error or bug on the restore quote to cart functionality.

Working with Bryan over a Zoom session on adding in "on account" payments (no money down) for ecommerce. This is a new setting that allows the companies to decide that they want to go into full invoice mode vs quotes, and then to allow the people to pay later on (say upon pick-up, drive through, or delivery). We made some good progress and he was going to finish up a small little bit and then we were going to launch it. Getting close.

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.

Recording notes and looking into sub inventory API sockets and defaults.

Marisa did a great job on the training. I took another full page of notes. She went through the advanced settings basically one by one. She also recorded it and I'll add that link when I get it.