Working with Shannon.

- Whatever brings us to certain points... lots of ways and similarities (commonality and overlap).

- Going over the working genius results with Shannon.

- Overviews for the value add-on core model.

- Concept of boundaries. Boundaries are different than rules. Self-ruling... only able to create those for yourself.

- My personal limits or ways to keep myself in check when things get crazy.

- General and culture specific norms.

- Personal boundaries are set by you... allowing for flex, when needed.

- It's not the hours... it's what is going on during those hours.

- Markers - if, then's - looking through the lens... (how am I doing?)

- Cycles

- I get to define the areas and parameters

- Power to make a change and make a different choice.

- I don't like to be micromanaged - personally.

- If this starts to happen, I need to take this course of action...

- It's more about what I'm planning to do.

- Practice and learning.

Quick meeting with Bryan. Reviewing his progress on tying in PO's and flex attributes to elements of time. Conversation about classic vs snow owl (visual themes inside of adilas).

Switched over to payroll stuff. Working on payroll and pub-15 tax withholdings for 2024. Working on entering withholding tables.

Quick meeting with Cory. We went over a small recap and small check-up on how things were going on different projects. We talked about some of the next and upcoming projects. Super short meeting.

Working on payroll updates for 2024. Did some dynamic looping and math inserts for database look-up tables. Started looking over login on the calculate payroll page.

Going over the federal tax and payroll withholdings in the calculate payroll page. Ended up on a quick phone call with Eric to help him merge in some code to check on a live server. He needs to show someone the new page tomorrow morning.

Back on the payroll withholdings. As I got deeper into the mix, I found that they, the federal government, had changed how they did their withholding lookups. I had to alter some table values. Originally, I had done the wrong look-up tables out of the Pub-15 document (offical tax table document - 70 ish pages). They, the federal government, took off the pay frequency for the automated payroll systems. Previously, we have always added tables that had the pay frequencies built into the tables (daily, weekly, bi-weekly, semi-monthly, monthly, quarterly, semi-annual, and annual). The new tables that we were supposed to use didn't have that. I had to do some light tweaking of our code.

Anyways, got everything in and done and push up new code. Merged in the branch with master and ran some database updates. The new code will go out tomorrow morning with the auto deploy.

Three different sessions, spread out throughout the day. Emails and checking payroll settings (new changes that got pushed up). Meeting with Bryan. Looking at a small bug on the data 10 PO reports. We got into a mix of old school values and new school code. The error ended up being a query loop without a start and end row value. Thus, it was duplicating form fields. We made the changes and pushed up new code to all servers. In the afternoon, more emails and setting up a client meeting for tomorrow.

Meeting with the Cannapages guys over GoToMeeting. We started out by debugging an API call. We tried a few things. I then had to login to the client's site, flip some switches, and then try it again. They are pulling menu info, but we had to turn on some ecommerce settings to let the pages (API sockets) play through.

They also expressed a desire to get two more API endpoints for pulling sub inventory attributes (list of values) and parent attributes (list of values). They then take that data and loop over it to populate their menu forms. I sent an email out to Cory with an update.

Great meeting with Shannon. We were working on project # 3, education and training - aka adilas university project. We spent the whole time going over things and putting together a number of pages, just brainstorming ideas, needs, and direction. See attached for where we are working.

Great little meeting with Russell. We are working on some mock-ups for a mini project that we are going to build together. The mini project will end up beign a dashboard of sorts (somewhat limited, but just for practice). We were working on the mock-ups today. We are going from a super simple paper and pencil drawing to a layout with boxes and placeholders (wireframe). The wireframe is great for conversations and being able to ask questions without going into crazy amounts of detail.

We were working in Adobe XD and putting different notes in different places. Russell was making a place for notes for interactions (how it works) in one place, notes for functionality (what it does), and then other interactions and user experience stuff (UI/UX). We ended up having a good discussion about budgets, dreaming big, but keeping things within a budget related scope.

We ended up jumping in to Snagit and going over quick ways to grab and build a quick mock-up. Russell also showed me how to download Adobe Fireworks (substitute for Adobe Photoshop - much easier). That is awesome, I loved using Fireworks. So much faster and better for simple web graphics.

Anyways, we got the wireframe mock-up done and then started moving into a more realistic version. He was calling it a high-fidelity mock-up (more true to form and even prepped with fake data and charts). We built a basic mock-up with headers, footers, navigation, and backgrounds. We then started to duplicate that basic template to make the other pages. One step at a time.

Phone call with Cory to go over some questions and then check up on priorities for what project is next. Recording notes from today and the past couple of days. Quick phone call with Bryan.

I joined the meeting late, but Alan and Steve were going over SG&A costs when I got there. They have a client that is wanting to virtually plug the SG&A numbers. Steve was talking about how that is playing with fire and not good accounting. After that, Alan gave a small demo of his production and advanced recipe/build process for sub inventory. It looked great and had lots of heavy client-side JavaScript stuff going on.

We covered a bunch of topics. Here are some small notes that I picked up from the discussion. No specific order.

- Steve and Alan were discussing settings and adding more settings for production and manufacturing.

- Steve was asking for input on direction, on the sales side of things.

- Alan was proposing some industry specific skins to help with sales.

- Alan was also saying that we should circle back around and build out more reports or even dashboard level pages to show all of quick data, counts, and totals. He was saying, we should stick to our name - Adilas - All data is live and searchable - stay true to that slogan. Along with that, we were talking about some places that still need some help and a little bit of loving. Sub inventory was a big topic along with other histories.

- Steve mentioned that he is working on some job costing options and reports. Tying in expenses, invoices, deposits, PO's, and time cards to elements of time (the job or projects).

- Small observation - both SG&A costs and job costing are dealing with deeper tracking of sub pieces and components that make up a bigger thing or item. Kinda interesting. That's some deep terrain and more than just simple inventory tracking. It's a mix of operations being tied into accounting.

- There have been more requests for more charts, graphs, and eye candy type stuff. At one point, we really wanted to do some graphical homepages to show and highlight some of that data. We have all of the data. It just isn't presented in an eye candy and easy format to see and look at.

- Alan is thinking that people (our clients and users) are going to be looking for more and more efficient ways of doing things and tracking things. There seems to be a draw or trend towards efficiency.

- We spent some time talking about AI stuff (artificial intelligence). That is a big buzz word right now. What if we redid some of our homepages (made them more graphical) and helped to show trends and month over month, year over year tends and patters. That could be really cool!

- We talked about the history homepage and how it shows a great overview of what was done or worked on throughout the day. That is some great information and a great daily summary of what happened in the system. Steve was showing that piece to a perspective client and they were super impressed.

- Back to AI stuff. We may use some verbiage like, we do such and such, similar to how AI works, without actually saying that we are using true AI. We already do a lot of that type of stuff. We feed data in, we then train the system to do certain things with it. As we go along, we can see areas that we could work on and turn our interface into a more AI oriented type product. We're not that far off, even right now.

- More talk about comparing patterns, comparing trends, and showing business intelligence (BI) level stuff.

- Mike, would like us to work more on the backend accounting pieces to help round out the system. Mike is a CPA that Steve has been working with for years.

- We could gain a lot, even on the virtual AI level, if we started to build out reports that show the known issues. We have a whole page that lists places and scenarios where things can get off the tracks or in the ditch (virtually). Date problems, number mismatches, disconnects, cart before the horse stuff, etc. That would be super cool to get those pieces built into the system.

- We circled back to sub inventory and possible ways of fixing things up there. We would love to add part id's, part category id's, and other key attribute id's to help the retrieval be faster and smoother. We can get the data in, it's the getting it back out that makes it a little bit harder (current database relationship structure). Anyways, some talks about ways to sure things up and fix some of the underlying pillars in the system.

- Quite a bit of discussion about Biotrack and Metrc (state compliance systems). We spend a lot of time and money trying to keep these connections up to date and working correctly. It's a moving target. We also want to pass on some of the costs to our clients and users.

- Our clients have some great ideas and tend to tell us what they are wanting and/or needing. That is awesome! We just need to figure out how to charge them for those upgrades. Basically, who is going to pay for the changes? Sometimes that can get tricky - either way, it's still part of the game we play.

- Most of our clients want real-time data going back and forth (live - not batched or staged).

- Alan and Steve were talking about ways to simplify the current API connections.

- Light talks about what some of the other developers were working on.

- We would love to be able to bill for real usage and what features our clients are using.

- We keep seeing costs increase. This is costs to us, costs to our clients, and even costs that 3rd parties are pushing and/or passing on. Everything seems to be in a state of upward flux. Along with this conversation, there were talks about some of the 3rd parties limiting throughput and/or limiting the number of API socket requests without a price increase.

- We talked about changing some of the file names. Some of the pages started out as a cannabis related page. We are now making those things more general so that we can use them (the pages and features) for our other clients.

- Going where the money is (based on client requests).

- Steve wants us to quote/estimate some new code for a client. Alan was recommending that we break things into phases and stages. Good discussion on this topic.

- Steve is doing some high-end business consulting for some of our clients. Helping them make decisions and plan for the future.

- The last topic of the day was thinking and finding ways to harvest the services (service byproducts) that our clients want or need (adilas marketplace stuff). If we help our current clients, that is an avenue of funding that comes from inside vs having to get new clients. Basically, help them get what they want. Steve put it this way - make your choice and then build up that choice (meaning software choice and pushing that software further along).

Meeting with Shannon. Looking for and seeing trends and patterns. Some of the hot topics right now are building industry specific skins (customer interfaces), BI or business intelligence reporting, AI or artificial intelligence options and marketing, job costing, manufacturing, and harvesting services and byproducts that adilas creates.

We spent most of our session reviewing and working on notes for the adilas university project dealing with education and training (No. 3 in the adilas lite or fracture plan). See attached for our notes and progress.

Just for fun, Shannon and I were talking, and we made an analogy of chasing a ball down the hill. It just keeps going (out in front of you). We talked about communications and collaboration options. We, our goal, is to stay out in front of the guys/gals with some rough plans. As the guys/gals get to the next levels, they will be looking for the next thing. We will keep feeding in the pieces that we have done or roughed out. We will let them interpret those plans and make them (the plans) their own. Basically, help to point and influence a direction without directly forcing it.

We also talked about how we learn by repetition and relearning things over and over again. It seems to really help to write things down, then re-sharing it back to someone else. That helps it gain clarity and makes it stick better.

Sometimes we present our clients with tooooo many options. We love that but it can be overwhelming and distracting to someone who is brand new. As part of our discussion on education and training, we talked a lot about industry specific skins and matching training and verbiage to those industry specific skins. See our attached notes for some other ideas.

Lastly, as we were talking, I mentioned to Shannon that Steve has a dream of offering basic business classes (business principles) to cities and communities. He would like to use adilas as the teaching tool. The class would be on the business principles, we would just use adilas to show those principles (how to do it and how easy it is to do it using adilas). I also wanted to record that another dream that Steve has is jumping in his plane and flying around and talking to CPA's. If CPA's really used adilas and adilas for their clients, they could do way more tax returns and also offer other ongoing oversight services, consulting, training, etc. It could be pretty cool! Just wanted to record those ideas from past meetings with Steve.

Emails and then meeting with Bryan. Going over an API for a 3rd party vendor. We were checking messages, record counts, and adding up totals. We made some changes and pushed up the new files. Recording notes form the day.

Meeting with Hamid. We were having fun talking about the analogy of chasing a ball down the hill. Just for fun, we were saying that we better stay out of its way so that it does not squish us. Sometimes it feels like the ball is going faster and faster and getting bigger and bigger. Just being silly.

We spent our time looking over Bootstrap code and CSS changes. Bootstrap and prebuilt templates are pretty cool. However, you can get layers and layers deep, and you tend to find yourself going down a number of rabbit holes. Lots of moving pieces and dependencies. We end up needing someone who is good at doing frontend code (designer) and someone who is good at doing backend code (database and code developer). You almost need a small team or a buddy. It's hard to be good at everything, to a master level.

Small bug fix on the master time templates. Recording notes from today and the different meetings.

Email to Wayne about ways to improve or fix the tables for storing sub inventory attributes and parent attributes. See attached for a copy of the email. It has some light plans on how we could change the columns on the custom_text table (and other custom attribute storage tables - numeric, text, date, and json).

Fixed the error messages and moved the unique id/error code to lower on the error message. Trying to make it look better. Wayne just added the unique id/error code a couple of days ago.

Started to work on an advanced search page that shows parent items, parent attributes, and sub inventory attributes, all on the same report. Bryan originally made the report. Just going over things and lightly cleaning things up. Refining some of the logic.

Started out doing some emails and recording some notes. Then meeting with Cory and Shari O. Looking at a small convert to PDF error on data 1. Other systems seemed to be doing fine. Just a problem on data 1. We also looked at a possible error out in statement land and math dealing with tips. Also in statement land, we had a request to apply a data filter to what was going to be on the statements based on amounts owed (paid or pending invoices).

We then spent some time looking at payroll settings and checking code on bit bucket (code differences between old and new code). We couldn't find anything that really stuck out. We then went and tried it on a play site, and it worked great. Cory is going to check the settings for the company in question. Also dealing with payroll, Cory and I jumped into a couple of state websites and pulled new tax and withholding tables and formulas for a couple of states. We need to update those values inside of adilas.

Lastly, we went over some priorities and talked about other projects. I've got the top 3 priorities written down in my notes on my computer. They are checking some older bad data for a report dealing with sub inventory, helping Bryan with the custom project to connect PO's to elements of time, and updating some state withholding formulas. We also know that a custom data import is coming towards the end of the week. Busy times.

Meeting with Bryan to work on automating some time template settings. We ended up fixing a small bug on his current code. We then started looking at the next steps to make the tie-ins even better (tighter). We ran out of time. We will meet later today to finish up.

Back meeting with Bryan to go over the auto tie-ins for PO's to elements of time. We spent some time working on the flex attributes and how they are tied in to time (new settings). Small work session. We made a small to do list and started going through the different pieces. I did lots of explaining and drawing to show where we are hoping to go. Plugged a small hole (in the data) and pushed up a small change to permanently plug that hole. Ran a quick update to update any past or older data.

We ended with ideas and instructions on automating the setting of the master time template settings when creating a new element of time. We went over a couple of options. Our main goal is to make the function of creating a new element of time lighter for developers and later potentially for API socket users. Because we are under a budget crunch on this one, we'll tone it back a notch. We may have to revisit it again later. Making progress.

Small little bug fix for a new shopping cart. It was erroring out on a page include (sucking in variables from another page). I made a few changes and pushed up new code. Sent an email to Steve and Cory. Recording notes from the day.