There were quite a few of us on the meeting this morning. Steve and Sean were talking about some sales leads and what not. Eric popped in with some questions. Danny chimed in here and there. After awhile, it was just Steve and I on the call. We spent some time talking about developers and how to keep advancing that ball. We want to spend some time going back in and documenting some of the projects. When they first come in, they, Steve and Cory, are trying to quote and bid the projects. Then after that, the projects tend to sit in the queue for a couple of weeks to a month. That's the spot that we want to work on... If we could circle back around and do some planning on each of the projects, it should help us speed up the development cycle.

Currently, some of the projects just sit there until a developer gets assigned to them. Then the heat is turned up and we crank it out. It might be nice if we have some other prep work done prior to turning up the heat per project. It also may help us do some prep stuff or surface tweaks before the bigger guns get in there to do their thing.

Steve and I also talked a little bit about cash flow and where we are headed there. Good stuff and making progress. As a side note, Steve is really happy with how Cory is doing and where she is taking things. That is awesome.

Emails and going through things. I was going to meet with Dustin, but he had to cancel as he was still working on a different project for the state of Maine.

Shannon and I went over a bunch of the current things that we are learning today for our meeting. Lots of drawing and sketching and talking. Without the drawings, this may seem like a random mess, but here is what we were talking about...

- Our subject is accounting and operations. If there is anything in those two topics, we are interested. Our product and platform is an operation tool that does accounting based off of the operations.

- We are seeing the role of CPA's (certified public accounts) playing a vital role is what we are doing. If a CPA catches the vision, they could potentially handle more clients and help with other services such as oversite (oversight) and other supportive services. 

- We would love to keep pushing toward more and more white label type options.

- We watch trends over time vs just making quick decisions. That seems to be part of my job and recording the story.

- Our model is moving more towards a reoccurring monthly platform plus the business services needed to support that model.

- Lots of talks about the current pain that companies have in trying to mash-up and/or marry together multiple different software packages to get the whole. We would love to keep working our whole or systemized business platform that puts all of those pieces in one place vs all over the place.

- A business decision of getting out of the way. Dealing with being able to spread the load. Talks about super man vs a series of smaller teams to get things done.

- Levels of aggregation and where we are headed. Think of a triangle. Transactional data as a base, then build up as needed... daily, weekly, monthly, quarterly, annually, etc.

- The value of flex or flexibility

- We want to work on a plan for where we are headed... Having said that, plans change all the time. We are thinking of putting together a plan with a general direction vs a hard/fast super solid plan. That may not work for us (super fixed or solid). We live on a moving, breathing, and changing landscape.

- Funnels - we were talking about vertical funnels, upside down funnels, and even sideways funnels. They come in all shapes and sizes. The concept of a funnel is take a bunch of stuff, and eventually get it going in a wanted direction. That (as a concept) could come from any direction. We have tons of recorded records and data, as we bring it together, we will virtually funnel it down and then figure out where it needs to go. Funnels are a great analogy for taking tons of random pieces, pouring or pushing them all together, and then getting something out the other end. We do this kind of thing all the time.

- We keep watching how things keep moving and trending. That is part of being part of an idea farm, like adilas.biz!

Meeting with Calvin.

Page with a bunch of GMext light videos from Calvin - https://lite.gmext.com/how_to_videos.php

See other entry for the notes. This one got double booked in the elements of time.

Meeting with Calvin, Steve, and I. Cory was unable to make it. Both Calvin and Steve were talking tons about text message marketing and possibilities to use Calvin's GMext text marking tool and combining it with adilas contacts, options, and using it as an internal 3rd party solution offering. Lot of potential there. Here are some of the notes from the meeting:

- People keep wanting things to be easier and easier. We have the same requests for text messaging and for labels. We want it, we also want it easier and easier.

- There were talks about the onboarding process and being able to do it or set things up by yourself.

- There was some discussion about text messages and the cannabis industry. The two of them went over some history, lessons learned, and some of the legalities.

- Texting deals with phone numbers. There are things called short codes and long codes. This deals with the length of the phone number. A normal number like (555) 555-5555 is considered a long code. A number like 55555 is considered a short code. They talked about pros and cons and levels of regulations for those numbers or values.

- We talked about Twilio and tying those services into adilas for different text messaging services.

- We have a 3rd party solution that is trying to leave the text messaging arena. There were talks about maybe seeing what they have and seeing if we wanted to take over any of that and/or reuse some of those pieces. Just talks and discussions. No plans were made here. Just options.

- Circling aback around to labeling - we would love to get that code on our (adilas) side of the fence.

- There were talks about how that could look and what kind of structure would need to be in place (transfer of code ownership and maintenance responsibility). Along those lines we talked about building projects and tools (one process), supporting those products (a whole other process), and extended updates and service plans (ongoing maintenance for those products - a whole other process as well). All of those things need to be considered. Who plays what role and how do we play together?

- To make super cool web-based tools, we keep seeing more and more need for high level JavaScript developers and coders. Spencer Garner, who does some adilas stuff, was mentioned. There are others and we could even potentially farm it out if needed to other or outside developers.

- The GMext product comes in a light version and a professional version. The big difference is how many texts need to be sent at one time. The GMext light version can only send up to 1,000 texts at a time. The GMext professional version is able to configure multiple long code numbers to run in tandem and thus be able to send more messages at once. Each setup of the professional version needs to be manually setup in order to get the correct number of outbound phone numbers (long codes).

- The discussion turned into topics of automated vs manual process and which scenario works best for what application and client base.

- They got into discussions about predictive marketing and even AI (artificial intelligence) stuff.

- Being able to use classic desktop software, web based version, and mobile responsive versions. Most things are leaning towards the web based and mobile versions of those products.

- Good marketing requires a plan and then being able to execute that plan over and over again. At some point, you need to pass the marketing load and decisions on to the users (until the predictive and/or AI stuff is ready to use and deploy).

- Calvin is using AWS and Lamda functions to do some of the magic for his text messaging stuff.

- We talked about being able to schedule outbound text messages. Calvin showed us a small demo. We recorded, but he asked that we not make it public. See note at the bottom of this page for more info on how to get to the video.

- This is a page with a bunch of GMext light videos from Calvin - anyone who wants to learn more may go here - https://lite.gmext.com/how_to_videos.php

- At the very end... we spent 5 or so minutes talking about the adilas label builder. Calvin and Brandon will meet and make other plans there. Most of the meeting today was dealing with touching base and text messages and GMext marketing tools and options.

We also recorded a small 7 minute video that showed Calvin using GMext light. He setup a couple quick contacts, assigned those contacts to a group, and then prepped and scheduled a text message to that group. It is inside of the adilas shop, but he asked us not to publish it via this element of time. Just go to the media/content advanced search and search for "GMext" and find the video with the date of 9/1/20.

Work session with Bryan. We spent quite a bit of time going over the flex attributes project. We were doing some planning, scenarios, research, and discovery type things. We ended up talking a lot about the concept of try storming and being willing to circle back around. The flex attributes project is a cross between four different projects. It has takes us quite a while to get to this point. We are mixing and blending flex grid tie-ins, sub inventory attributes, parent attributes, and custom field names and defaults. When you mix all 4 of those older projects, you get flex attributes. These are what we are doing and going to use for the real in-line database extensions and options. Pretty cool. This is a big project and may take some iterations and looping (on purpose circling back around) to get it done.

Bryan did record some of the meeting and he made some notes dealing with datatypes and other requirements.

Russell wanted me to push the jp-3 branch if possible. There is a database update that needs to run prior as well.

Danny and Sean checked in. Danny and chatted and talked about try storming and coming up with a solution for his project to combine and merge together multiple PDF's stored on a per sub inventory level. This would be from an invoice and the merged PDF's would end up being documentation and test results for the different products on the invoice.

Wayne joined in and wanted me to call Steve and Alan. Steve joined in by phone and Alan jumped on the meeting. The subject was how soon are we going to get to the 3 projects that Wayne needs? See attached for the notes. Here are some of them in a quick, non laid out format.

- We are seeing our model shift from small mom and pop shops into bigger and more demanding clientele

- Lots of focus on up time and server reliability

- We have a great team and much is required of all of us.

- Alan and Wayne really want us to invest in ourselves, meaning adilas as a company - plan for the next 10-20 years.

- This whole thing is a long term play.

Chuck and I met and chatted for about an hour. We covered a bunch of different topics. No special order, but here were a few of the topics:

- Decisions of a leader to get out of the way to let things happen in a better manner. Sometimes that is hard.

- Report on WanderWays (camp adilas) project - see the screenshots and this link for more info: https://xd.adobe.com/view/466071a2-5a71-49b8-9c80-b54d175dc78d-1333/

- Report on the adilas docs (internal how to manuals and style guides for developers and designers). See these links for more info: http://adilasdocs.swanhaven.co/adilas-docs-home.html and http://adilasdocs.swanhaven.co/core-components.html

- Full stack developers vs small teams and virtual departments to get the job done.

- We also talked about cannabis vs other business verticals. There are many of us who would like to explore other options and business verticals. WanderWays is a venture into one of those realms.

Met with Alan and touched base on some of his current projects. After that, we jumped in and chatted about a number of other things including the meeting that we had with Steve and Wayne from earlier this morning. Here are some of my notes:

- We really want to split some of the guys into smaller teams to see what that would do. As we do that, we know there there may be more overhead to help those teams keep going, but we are interested to start trying some things.

- We talked about making improvements to the project manager type role and filling in more of the requirements and back story before releasing a project to a developer. Ideally, smaller, bite sized pieces vs the whole ball of wax. Lots of talks about defining the role of the project manager (PM). Upfront time and monitoring things along the way. We would love to shoot for mini teams of 2-3 people.

- Alan recommended that we see what people want to do based on their input from the survey docs that we sent out a couple of weeks ago. We want as many people to play and participate where they want to. That could be very useful but may take some time to get the right mix and balance.

- If we break things into smaller pieces, that helps the confidence and the moral of our team members.

- We talked about some of the core team members and what their roles are: Steve, Cory, Brandon, Alan, Wayne, Shari O., etc.

- Having a buddy and a back-up plan

- Who is the helpers that fit under the main people (sub players with in their own roles and areas)? We need to define those roles and relationships.

- Alan highly recommended that we put in some of our own projects into the project queue so that we could reserve those spots. The project queue is already backed up a bit.

- We would like to focus on more structured teams and getting deeper into the project management side of things.

- There are always opportunity costs of doing more of one thing than another. We need to get in there and start figuring things out. Opportunity costs are what you loose and/or can't do if you do something else.

- As part of where we are going, we would like to start using some more agile type sprints and agile development cycles and practices.

- What is the next important thing?

- We have been defaulting to Steve to be our leader. We all love what he does and no one really wants to pick up that ball (and all that it contains) and really run with it. Sadly, it almost feels like a poison ball (the full on leadership role).

- Alan and I poked around the adilas site and looked at some business numbers and stats for a few minutes.

- It really feels like a major cross road is before us... make it simpler or go even bigger.

Part of this session was a meeting with Calvin. He and I went through some of the differences between the desktop and the web version of the adilas label builder. We also talked about the difference between test and live (data and setup configurations). As we go forward, we are going to need a sharp JavaScript developer for the adilas label builder app and web version.

Calvin showed me some web based canvas and layout programs. Here is a link to one called flowSharpWeb. Not exactly what we are looking for but it has some of the concepts that we are looking for. Basically a full blown web layout program to allow our users to build and connect all of their custom labels designed and entered into the system.

There are always multiple ways to do these things. We just have to figure out our way and style.

We had some talks about outside consultants vs the primary developer. The new guy doesn't know the product as deep as the original or primary developer. Sometimes that is good and sometimes that is a disaster. We are going to work on creating a stepped plan... Going from a working Windows app to a full featured web app.

Calvin and I looked at some database tables of what we have and what we still need. We will need some of his sheet label specs and sizes. As part of this process, both Calvin and adilas will be passing different sections and pieces over to each other to get this plan and process in place. As we move forward, we would also like to get some training for the label builder and what the user expectations are/could be. We also talked about recording one of our next meetings as we try to transition existing code from Calvin over to the adilas side. We want to capture what we can without having to make Calvin do the same things over and over again.

After Calvin and I were finished. I did a bunch of emails to finish out this time period.

Going over some bulk print and PDF merge files with Danny. We did some training and some prep work on a project that he is working on.

Meeting with Brandon, Steve and Alan to go over vendor aggregation project.

The three of us met and chatted about a project to create a master vendor catalog for a company. This is not system wide, but more of a master list for a subset of companies. The topics varied and we chatted about a bunch of different things. See attached for our notes and a small drawing that we did. I'll also include some other notes here below.

- Steve is happy where things are going!

- Human factors - if you don't have to think about something, it makes it easier - for example: push or pull the door handle. That could be easier than twisting, sliding, or some other complicated process. What do people expect to do or not do... lean in that direction. It requires less education and less frustration if it does what you think it should do.

- They talked about putting on guard rails and helping our users. The more we help our users, it actually creates "sticky users", which is a good thing, meaning that they like and use what we have to offer. The more they use it and depend upon it, the more they want to stay - thus a sticky user.

- Alan and Steve were reviewing a number of recent projects and how they are helping. Sometimes that is good to remind ourselves that we are doing good things. I hate to admit it, but often our job seems to be finding the problems, the tweaks that are needed, and constantly looking to refine things. Sometimes, all we can see is the "need to be fixed" stuff vs the stuff that is already fixed. Part of the job.

- We should would like to be able to help our clients see what is available and what new changes have been made. That is very tricky sometimes. It is amazing what our clients don't know (but could use, if they knew it).

- Customer support and offering other services. We are seeing a small shift in our model and leaning more towards support and other services.

- Currently, we are charging $100/hour for custom code work and $65/hour for training. At some point, we may need to increase those fees.

- We talked about the concept of kicking back to the core.

- This is the opposite of client fees, but at some point, we would like to up our own wages and/or pay rates. There was also some talk of future company allocations like computers and/or vehicles, and other perks and bonuses. Still a dream, but hopefully coming closer and closer to being realized.

- More project management with a focus on being and doing better project management. Helping our guys not spin their wheels and/or getting stuck. Keep things going and flowing.

- Steve and Alan were talking about having a special developer's meeting and talking about project management and see what the guys say or what ideas we can harness.

- Dealing with try storming... we may need to start in, get as far as we can, and then have someone else get in there to help finish things up. We would love for things to go full circle and be completed perfectly the first time, there is a cost to that as well. Keep playing the try storming game and be willing to circle back around as needed.

- Selling when the iron is hot... it really helps to sell things when there is some pain or a need.

- Talks about working off of bids and estimates vs hard fast quotes or fixed dollar amounts. Some of these things, we just don't know until we get in there and kick around a bit.

- Steve was saying, it may take a couple of years to make these transitions and changes. Sometimes we want it next week, next month, in a couple of months, etc. In reality, it may be a couple of years (plus), depending on what the changes and transitions are.

Lots more notes in the attached txt file with other meeting notes.

SaaS (software as a service) and how being able to do custom work is really changing what we do and who we serve. We are seeing the size of our clients change as those who want and need the custom code work tend to be a little bit bigger. We can still really help the little guys, but there is a definite switch to a slightly bigger client, but not too big. Too big means crushing...

Steve was talking about being super grateful for steady work and having enough work. As we were talking, the subject of different approaches came up. We want to come at these projects from a bunch of different angles. That helps to round things out and opens up options.

Towards the end, Steve and I jumped on a custom code project, API socket usage report, and did a small joint project and/or work session. Just like the old days.

Russell and I merged in some new code for the user permission templates. This allows you to create, name, and assign whatever permissions are needed to a single template. You can then use one or more permission templates to assign the permissions to the users in bulk or with preset permissions. Good stuff. We got it all launched and Russell was going to test it.

Reviewing the responses and making a series of summary statements (just starting). This deals with the questionnaire and/or survey that we sent out to some of our core team members, about what or where they thought that we should head/go for a business plan. Nothing stands still, the ground is constantly moving underneath us. It keeps growing and morphing and shifting. This is where we live and breath.

Recording notes and emails.

Small bug fix for Kelly with expense/receipts, splits, and back tracking through the voiding process with multiple subs and smaller pieces. Recording notes and emails.

Recording notes from the week. Lots of good ideas and things happening.

Working with Danny to build a page that combines PDF's attached to sub inventory into a single document to serve as documentation for a customer's invoicing purposes. Today we were prepping and building an array that holds the document names.

Recording notes from last week.

Progress is being made on the flex attributes project. Bryan is following the flow from sub inventory attributes for the new flex attributes. The flex attributes will end up being new database columns for all of the 12 main players. It is currently just in prototype mode but looking good (for its level). Bryan and I went over his existing progress and did a light critique. I authorized him to spend another 10 hours and see where we end up.

Built some database updates for Calvin and the adilas label builder app. The new updates deal with getting all of the single label sizes and Avery label sheet label specs. This is all part of the adilas label builder app. We are working to get the whole things on the web and being a full blown web app vs a desktop app. Cool.

Danny checked in and said that Steve and David had to go to Denver for a family medical issue. Sean popped in. Eric and I had a great little discussion about operations and accounting and how to allow things to flex and bring them back together. Eric was coding some of the new ACV (actual cash value) changes for customer loyalty points. He was trying to keep the ACV and points proportional and that was getting tough. We came up with a solution and he will be adding it in. He was close already, he just needed that approval to be flexible with some of the math. Most programmers really like to keep everything as equal as possible. In a moving and dynamic environment, that is really tough. You can do it in a perfectly static environment, but life is not like that. It has to be able to move or flex.

I was going to meet with Dustin but he sent me a text saying he didn't need to meet. I did emails and paid bills instead.

Shannon was sick today. We will hit it later this week. I took the time to catch-up on recoding notes from last week and doing emails.

Planning, on paper, for the red light - green light game for the cross corp mappings for cross corp invoice to PO section. The red light - green light is going to be a check for a go, no go on doing the cross corp actions. If all is green, we can do it. If not, we wait until everything is green (meaning user action is needed to help map and prep things).

Danny and I did a full two hour work session and covered a lot of ground today. It was part training, part building. The current project is a mix between custom labels and custom paperwork (combining and merging in PDF's tied to inventory items and sub inventory). Anyways, our project today was building out the page to handle both shopping cart interactions and after the fact invoice operations. Making good progress. Good stuff.

Danny and Sean were talking sales and options. They have a lot of fun things going. Danny had some code questions but also did a great job working and interacting with Sean on the sales side. After Danny left, Sean and I went over some custom paperwork options and just played around with ideas and solutions that already exist inside of adilas. I took him on a small tour of the custom documents section of the site (system admin permission levels for document management and assignments).

GoToMeeting session with Chuck. We went over some of his existing projects and I got updates on each one. He is still working on the adilas style guide - backend document for adilas developers and designers. He is still chipping away at the WanderWays (camp adilas) project. We also talked a bit about the presentation gallery or sales tool that we started a few months ago. We also talked briefly about bills and invoices. Good little report.

Did some prep for a meeting with some High School kids from California. My brother Jason is a High School teacher out there and he is teaching a college prep class. We got on a Zoom session and I presented for about 45 minutes. We talked about mixing fun, work, and education. We also talked about getting skills so that you can do what you want to do without having to work every second of the day. I showed some fun pictures, did a small code writing demo, talked, asked them some questions, and had a good time on the meeting. I was on cloud nine once we finished. I really had fun talking with the students and talking about what I do and like to do.

We were going to have a weekly check in, but it didn't happen. I was on the GoToMeeting for a half an hour, but nobody came. I spent the time prepping for another meeting. No harm done.

Emails, tech support, and recording some notes.

Working with Bryan on the Hypur ecommerce payment stuff. We already have a form of this custom payment type inside the main system. This one is on the outside and integrated into the ecommerce processes. Going through code and making small tweaks. Light talk about flex attributes and flex extensions (another project that Bryan is on).

Sean and Danny checked in. Pretty casual morning. I did emails and other general stuff.

We had a good work session and worked on the merge portion of Danny's project. We spent the whole time building and testing, building and testing.

Shannon had to cancel. She is still feeling under the weather.

Did a bunch of emails and some light tech support stuff back and forth with Wayne and dealing with the different servers and news and update stuff (WordPress account). Also worked on a small bug fix on some media/content reports and filters. Sent an email to Craig and Steve dealing with funds and plans.

Emails, WordPress stuff (this is in constant need of updates and patches), and helping Bryan with Hypur API socket connections. Bryan will most likely have to ask Alan for help, I went about as far as I could based on my knowledge.

Two hour work session with Eric and I. Small tweaks, checking code, making suggestions to tie things together, checking output values, buddy testing, and talking deployment strategy. He is working on switching over the customer loyalty points form straight point values to real ACV (actual cash value). This is a pretty big switch in the logic portion of the loyalty point calculations and display.

9/1/2020: Need two labels per corp for 4 corps.

There were a bunch of us on the meeting this morning. One of the first topics was the passing of David Berkenkotter. He was one of the adilas founders and in the adilas ownership circle. He suffered a stroke last week and ended up passing away on Saturday, September 12th, 2020. We were all talking about it and thinking of ways to help out and just be there for Steve and the family. David was Steve's brother. We had Danny, Sean, Dustin, Eric, and I on the meeting. All expressed their condolences and thoughts. 

On a different note, the other time spent today was doing emails, clean-up, and working on small bug fixes. Pretty quiet this morning.

Steve was unable to join us, which is totally understandable as their family is mourning his brother's passing.

Cory and I met for half an hour and went over a number of small questions and projects. We also talked about scheduling more time and going back into the project queue and prepping as many of the projects as we can. We are looking at booking a couple hours a week to go in and get the guys started with better frontend project management, stuff happening before the projects are assigned to the developers.

Once our meeting was done, I worked more on some report bugs on the advanced expense/receipt line items searches. We added in search filters for balance sheet items and elements of time, tied to expense/receipt line items.

9/14/2020: Allows OR dispensaries to report caregiver sales through API to METRC.

Uploaded to Maritime and Oregon Bud. Need to have the new METRC API interface to use it.

Emails, uploading new files with a couple small bug fixes, and general to do list stuff.

Great little work session on the combine sub PDF's into a bigger master PDF for sub inventory, carts, and invoices. Danny and I spent most of our day today going over an intro to API sockets and how things work. We also did some logic tweaks and building structures and then flattening those objects into JSON for the API socket calls. Good training session today.

Bryan and I worked on flex attributes and lots of dynamic formatting. Today we were working on standalone dates, date/time stamps, decimals, and integers. All of this was based off of findings and assumptions. Basically a lot of if statements to help dynamically format things according to what the user entered or didn't enter. His flex attribute project is going well. As part of our meeting, he wanted to know where the cutoff line was (this project could be huge...). We set some basic requirements and decided that the rest of the wish list could come later. We may need to touch base with the client, but things are looking good. We will for sure have to circle back around, but a great start.

Recording notes from the day.

Some of the guys checked in this morning and then went about their ways working on projects and what not. I was checking banks, payables, and doing odds and ends. Steve checked in for a few minutes. Busy times. I was also building a list of special reports for Shari O. to help monitor client usage, images uploads, and file uploads (media/content) stuff.

Dustin was working on a project so we didn't meet today. I ended up doing more emails, putting some rough budget numbers together, looking at financials, and other small tasks.

Working on summaries for the company culture and what people like about what we are doing (topics from a questionnaire). See attached. These summaries are from team member input and feedback.

Meetings with Shari O. and Steve. Shari O. joined first and we went over some email questions, email account stuff, and went through a small tick list of questions and things that need to be done and/or looked into. We also spent some time talking about staff and some of the adilas team members. Light report from the field...

Steve joins us at 2 pm ish. We chatted with Shari O. for a bit and then just Steve and I worked on finances, budgets, and ideas for how to raise more money and capital. We have a really good thing going, it just keeps taking virtual gas to keep driving the car. This is the constant battle for most small businesses. I guess that we'll need to get creative and come up with something that works for us and fits our style.

Craig joined us and we talked more budgeting, ideas, and cash flow stuff. Steve had a list of ideas. We recorded many of them on an Excel document that we were working on. We'll make them public later on, as things develop.

Back on the switch over from loyalty points to loyalty as an ACV value (actual cash value). This was recommended by Steve and a CPA that said that companies need to attribute an actual cash value to the number of points that are being extended and renewed. This is still going to be an off balance sheet item, but at least it will have an ACV value to go along with it. Eric has worked for a couple of weeks on this change over and logic switch. We spent some time today reviewing code, making small verbage tweaks, and planning the deployment and switch over roll out process. Good stuff. The project is looking great.

Recording notes from the day. The daily transfer from post-it notes to digital.

Touching base with the guys. Emails and cycling through a small tick list of stuff.

Meeting with Chuck to going over projects and what not. We talked about some changes to the WordPress stuff that we need (updates, back-ups, and new pro level theme headers). We also went over some of the adilas docs project that he is working on as well as some of his JavaScript training that he is working on. We are seeing more and more needs in the JavaScript developers role. Very marketable skill set.

Alan and I had a longer session today. We did some testing and debugging on some new expense/receipt services and DAO's (database access objects). Some of the older expense/receipt stuff has special ways of getting to it that Alan didn't know. For example: Making expenses after payroll, PO payables, reimbursements, paying things on account (splits), making stock/unit payments (base prices and floorplans), and other custom expense/receipt stuff.

After we got done with that, we jumped over to a project that he is currently planning. It is dealing with his cross corp vendors stuff and doing cross corp mapping and top-down controls where an enterprise system would have a master list of vendors and the sub or transactional systems under the master corporation (enterprise system) would only be able to use the master list of vendors. We would have to map things, and also monitor changes and updates (cascading changes). Pretty deep but should be a good project. This is the first of many on that master/slave (enterprise to transactional systems) level. Currently, he is still in the planning stage and hasn't started coding yet.

Rework the news and updates section (WordPress stuff) with security, better headers, new theme, logo swap, and maybe even code for white label stuff, etc.

Phone calls. Started out talking to Steve over the phone for about 45 minutes. We were talking about options for funding and making things happen inside the adilas company. That is a constant battle, keeping the business going, moving, and growing.

After that, I jumped on a phone call with Russell for a bit. We were talking about different projects, WordPress, news and updates, user templates, and page level CSS and JavaScript. Russell helped us out all summer and we got a bunch of great projects done. He is back at school now, so we get a smaller portion of his time right now. We can't wait until he comes back, full time again.

Danny and I are slowly building a new API socket to help with a custom request to gather up and merge all PDF documents per invoice on a single PDF document. Basically, imagine sub inventory with each batch having special testing results and what not per item. Then, when the invoice is fully built, they need all of the underlying supporting documents that have already been previously uploaded to be merged together into a single document. We are making progress, and it is coming along. A good portion of what we are doing is team building and doing some training to help Danny out with this project. It is a little bit over his head.

Working with Bryan on the flex attributes project. Reviewing code, cleaning up comments and code from a past copy and paste action (adapted from previous code but not really cleaned up - tight).  Linking to new pages and building in navigation. Other small clean-ups and organization stuff.

Sean, Danny, and Eric were checking in. Eventually it was just Eric and I. He was going to be my 10 am appointment, but since nobody else was in the meeting, we just switched over.

Great little work session on the off balance sheet stuff, ACV (actual cash value) on customer loyalty points, and getting everything queued up and ready for launching. We are shooting for Monday night at 9 pm to launch some of these new pieces. As part of our work session, we had to move files between branches, recorded an error with JSON and going between JSON and ColdFusion (deserializing) and between ColdFusion and JSON (serializing). We also added some new filters to pages and methods. Great little project and it is coming along nicely.

Danny and I spent a couple hours working on the merge PDF's project and new API sockets. It is great training for Danny. Towards the end, we got pretty deep flip flopping between lists, arrays, structures, objects, and merging PDF's together.

We have had a couple of issues with parsing JSON objects. We use JSON to hold and store all kinds of special settings, custom configuration stuff, all API sockets use JSON, etc. There is a simple way to check to see if a JSON object is valid or not. It is a ColdFusion function called "IsJSON(someVar)" substitute out for someVar. It will return true or false and then we could go from there. We may want to search all of our code and search for "SerializeJSON(someVar)" and also "DeserializeJSON(someVar)". Serialize JSON means go from ColdFusion structure to JSON. Deserialize JSON means go from JSON back into a ColdFusion object or structure. We may want to make sure we have valid JSON before storing it in the database, when pulling it out from the database, and also when doing some kind of API socket call. If we go through the code and add the IsJSON function before working with the JSON object, it will help us not get a parsing error. This is somewhat of a big project, really simple, but kinda big just due to the number of pages that would need some minor tweaks.

Steve and I got on a GoToMeeting session and talked about funding, options, and direction. We had MS Excel out and were jotting things down in Excel and hashing out ideas. We were going to keep going, but ended up helping to fix a bug on one of the servers.

Cory, Wayne, Steve, and I got on a meeting to fix a bug on one of the servers. It was an unknown bug and we had to get into the code and move a data dump around to find it. Not very straight forward. It ended up being a dependency issue on a CFC (coldfusion component) that wasn't pulling in. All other servers are currently running the same code and not having a problem. Those ones are tough.

Anyways, we ended up getting Alan on with us and finally got things figured out. By the time we got it all sorted out, we were all pretty tired. Wayne and Alan want to reach out to an Adobe ColdFusion master to get some consulting. I told them that I would run it by Steve and let them know. We need some bigger brains on this one - funky memory and object dependencies stuff.

At the end, just Alan and I were on the meeting. Alan and Wayne will be on the call with the consultant. Alan is thinking that it has something to do with the Java garbage collection stuff (this happens behind the scene and helps free up memory in the application). When things get really deep, we have to pull in the big guns.

I sent an email off to Steve to request permission to let these guys setup some meetings with the ColdFusion consultant. Other email stuff.

Bryan popped in right at 4 pm. We were still in the middle of the bug fix for that server and the memory stuff. Bryan and I will have to hit this stuff later, next week. Our first priority was getting that server back up and going. Not all bugs are equal and some are really tough when it feels like it is out of your immediate control (part of the code that runs your code).

Emails and wrapping up things from the day.

General catch-up from the week. Transferring notes from paper (post-it's) to the developer's notebook. Sometimes it gets too busy in the heat of the battle to get everything fully recorded. A quick scribble sometimes is enough to jog the memory to remember what was going on. Paper and pencil (pen) are still one of my personal favorites, as far as quick and easy tools that we use.

We have a company that uses adilas for a 100 mile running race every year. Making a few tweaks to their custom pages to handle the new race this year. Due to Covid-19, we have to handle a rolling start vs a mass or group start. The Bear 100 starts in Logan, UT and end up in Fish Haven, ID (by Bear Lake). 100 miles of mountain running. 13 aid stations spread throughout the course. We track the runners, their times, their check in/outs, the length of the legs between stations, and the length of the stay per aid station. We also have a runner support section that allows family members and friends to watch their runners, upload photos, and chime in with comments of encouragement. This 100 mile race only last for 36 hours, but they use the system pretty heavily during that time. We charge $3/runner for this event. Kinda fun.

Prepping and changing files for the new race. Combing data for a new runner upload.

There were a bunch of us on the meeting this morning. Eric was reporting on off balance sheet entry calculations and changes to the customer loyalty points based on ACV (actual cash value). Danny, Sean, Steve, and I were asking Eric questions and having a conversation. Lots of talks about compliance and future state of what will be required for accounting for customer loyalty points. Lots of talks about intentions, tax liabilities, and auditing potential. Seeing a truer picture of where things are at.

Steve was mentioning, maybe just trying to sell the loyalty points as a solution. You get all of adilas, but you buy it so you get these good customer loyalty points. How do we get the sales message out there... we are looking to really fire up the sales engine.

Alan popped in and gave us a quick report on meeting with the ColdFusion expert. He and Wayne met with them this morning and Wayne knows what to do. Good stuff.

Talking budgeting and finishing the whole projects. We are making great progress, but we need to keep finishing things up and really releasing what our clients want and/or expect. Basically, in order to move a project off our tick list, we really need it to be fully finished.

We were talking about developers and holding them accountable and how to virtually hold the pay until we get the deliverable. We know that most of our guys are pretty good, but we have had a few that virtually disappear and/or we aren't sure what they are doing or working on. Sometimes the communications break down. We are seeing certain requirements that need to be met, including weekly check in, committing code and projects, and allowing Cory to help manage projects.

Lots of talk about normalizing data and getting master lists and master catalog entries. As things increase and grow, we are seeing more and more needs for the base transactional systems linked with a master or enterprise/aggregate system.

One of the projects that we have docket is dealing with users and their permissions. We just barely launched some new user templates (named preset permissions). We have some clients who already want the next step (called user roles and auto updates of the permission). It is crazy to see how quickly, our clients want the next logical step. Speaking of the next logical thing... our project queue is really growing.

We need to get more into marching orders and better project management. We keep getting pulled into multiple different directions. As a side note, we are seeing more and more needs of a full development shop and working and building out our software package.

Working with Danny on the merge PDF stuff. Debugging and testing code.

Emails and coordinating meetings and action items with the Bear 100 folks. Research on PDF's and merge options.

Meet with Cory and Steve at 2 pm - Going over a project review of flex attributes and where it is heading. We also talked about the use of templates at different levels. If we could setup templates (at different levels) we could really speed things up. Once again, standardizing data inputs and data outputs. Some of the topics were dealing with master catalogs or lists that could help standardize the data that is available. Make it simple, make it standard, and then use it over and over again. The old build once, use many concept.

Some of this stuff, master lists and master catalogs, enterprise or aggregate level systems, are really important as soon as you have multiple locations or multiple systems. If not, it might be cool, but not as required or as needed. Our model keeps going out into more of the medium sized businesses vs the just the mom and pops. We are seeing a pull for this sized businesses and what they are needing. Interesting.

Working on the combining of sub PDF's with Danny. We had a full work session. I had Danny's branch on my computer and was doing some testing and playing around. We were trying to go the API socket route, but it kept having errors occur. We switched it up and even used the same code and now it is working. Slightly different path. Pretty crazy. Sometime you have to go down a road and hit a dead end before you know that route is not the right one. Part of the game.

To document what we ended up doing... we switched from an internal API socket to a direct URL driven design. The process goes, they click a button, we look-up everything and build a list of sub PDF's that are needed. We then take that list and pass it off to the server that is storing all of those files. Once it hits the other server, it loops over the file names and puts the final PDF together (merging the sub PDF's into a bigger PDF). This seemed to work better.

Bryan and I spent some time going over flex attributes. We were reviewing code and working through some formatting and logic flow. We made a small list of things that are still needed, but we are getting close to launching this first round of stuff.

Late night session with Eric. We ended up doing some pair testing and debugging. We put his code on my machine and we did some testing. It was good to see it running in a different environment. I had a few more variables and we had to make some light tweaks to help it out. Minor stuff, but good all the same. Eric and I have had a lot of fun testing things back and forth. I'll test, he'll fix it, repush it up to the branch, I'll pull it down and retest it. Great little process. This project is getting really close to going live.

Speaking to a client's level and verbage, calling things what they call it. That is a huge key for getting in the door. For example, instead of saying ecommerce, you could say client portal or customer interface. They are the same thing, but the terminology changes and thus the ideas and/or direction that it could go. It is all angles and speaking their language.

Danny, Sean, Steve, and Eric all checked in this morning. Towards the end of the meeting, Steve was having me show Sean around on some of the custom interfaced and functionality that we have done. We looked at the Bear 100 runner site, special events, GPS tracking, time tracking, event tracking, etc. Lots of fun discussions where we could go and how we could help these different clients.

As a side note... some of what we pitch is vision and potential... what if's and ideas and solutions. That's fun.

Dustin texted me and was working on other projects. We did not meet. I ended up just doing my own things, non business related.

Work session with Shannon going over team responses to a questionnaire that we sent out a month or so ago. Prepping for part of the business plan. Summarizing data and ideas. See attached.

9/22/2020: See spreadsheet. Is dependent on the development of #1862 prior due to some of the pages needed.

If client wants the "6" fields to be dynamic ie not set in certain spots on the invoice, each setting goes up from $300 to $1,000. If they want more than 6 fields, it is an additional $100 per extra field.

Emails and working on a fix for the photo upload API socket. Added in the outbound photo name and special corp-specific path name. Pushed up some new files.

I got a link from Cory dealing with Flash and end of life stuff. Soooo sad! I really liked Flash.

https://www.upsidelearning.com/blog/2020/05/18/can-you-play-flash-after-2020-this-is%20how/

I got this link from Chuck - dealing with the adilas docs. Some new updates.

http://adilasdocs.swanhaven.co/adilas-docs-home.html

Emails and checking out Chuck's new changes and small video on the adilas docs (SOP's - standard operating procedures) for adilas. This includes meetings, code conventions, style guides, etc. The current adilas docs can be found here:

http://adilasdocs.swanhaven.co/adilas-docs-home.html

Also worked on some prep stuff for the Bear 100 mile race. They use adilas and will be running their event this coming weekend.

Sean checked in and we briefly talked about all of the different "lands" inside of adilas. Merchant processing land, ecommerce land, API socket land, invoice land, sub inventory land, etc. Lots and lots of completely different environments - like lands or virtual worlds.

Back working on more Bear 100 tweaks and custom code changes. They have a need for a rolling start this year, with the virus stuff.

Chuck let me know that he wouldn't be on the meeting today. He is dealing with some moving stuff.

I spent the time working on new tweaks for the Bear 100 race. Custom code for the rolling start and new finish line queries.

Alan checked in and we chatted for half an hour. I showed him what I was working on and he reported on a number of projects. One of the projects that he is working on is a master list or master catalog of vendors per corporation group (enterprise or aggregate level). He showed me some planning that he is doing on an object manager and using both application (server level) and session scope (user level) settings and objects. Pretty cool and we talked about getters and setters, managing our own memory usage, and controlling updates and changes. Good stuff. We also talked about unit testing and other projects that are heating up and coming soon.

After Alan left, I went back to doing more custom work for the Bear 100 race event.

10/1/20: This project deals with how the auto barcode for subs is pushed into the database. This process is mostly done on the add mode. The new setting would allow you to set the precursor for the sub barcode. The current code adds a b-5555 where 5555 is the sub id. So, basically, they want to be able to set the frontend string such as a ~ or some other string in front of the sub id.

- This will be a new corp-wide setting (corp_wide_settings.cfm) - Thinking of making a new sub setting under number 9 called "Barcode Options". Then underneath that, we would add 9.3 "Replace Sub Barcode (b-) with ~" Then a checkbox. See below (we made some changes)

- We were thinking of making it a varchar and allowing the user/clients to enter their own string. The default would still be "b-" but it could be "XYZ-" or whatever. Also, we thought that the verbage should say something like: Auto Sub Barcode: b- (in the field by default).

- Once that setting is done - meaning we have added a database update and scripted the new changes. We need to be able to add new, edit existing, and then use that setting on the edit_sub_part.cfm page as well as the add_edit_sub_inventory.cfm page. There are action pages for both of these main pages.

9/23/20: See attached spreadsheet. Would allow for a setting to have ~ replace -barcode

9/23/20: Will create a new permission that enables a user with green item permission to also be able to print. Essentially this is splitting id=61 into two parts (the admin and the printing) so the id=55 user can print. Need Brandon input

4/9/21: BD: 13hours=$1300 (45), DS: 8.5= $300 (35)

9/23/2020: Add settings for parent core value defaults

Working on Bear 100 functions and time calculations. The new tools will use total time vs a physical ranking system. We have to do this to allow for a rolling start this year.

Working with Bryan and doing some clean-up on the flex attribute project. We ended up doing some rewriting of the create database code and small formatting tweaks. We added some indexes and other small database field size changes.

Danny and I were working on the merge PDF project. We can do it just fine with simple PDF's. We then tried it with some super complicated PDF's and it was failing. We then tried to flatten, sanitize, and other PDF tweaks to try to make it work. It will take a little bit more but getting close.

Working on code to help calculate total times in seconds, minutes, hours, and days. This is going to be used for the Bear 100 mile race, but we will also use this to help with other time based reports.

Great meeting with the Bear 100 radio folks. We went over some of the event features and made a small little to do list. Most of the requests were dealing with the bulk start tools and the full race view report.

Eric got on the call much earlier, but we were still on the Bear 100 meeting. After we got finished, we chatted about the customer loyalty points stuff and decided to postpone the launch until Monday evening. Busy week, this week. Anyways, we chatted and talked strategy. We also talked about pros and cons of outside 3rd parties. That is a mixed bag but part of the game.

Working more on the bulk start tool for the Bear 100 mile race. We added in a bib number filter and some other fields to help with the process.

A couple of the guys joined the morning meeting. The general topic was sales. We had Steve, Sean, Eric, and myself on the meeting. Steve is really trying to get the sales engine started up and going. We have a bunch of things circling around, just need some of those things to fall into place.

We talked about using Chuck in sales and redesigns of certain pages and flow. Eric brought up the need to convert some of our Flash modules into HTML5 or JavaScript. We know about that, but still haven't figured out what to do there. There is a constant need for more refinement and development.

As a company, we give a lot away for free. It could be consulting, custom code, design work, training, systems, upgrades, server stuff, or whatever. If that starts becoming required (meaning our clients expect those handouts), we end up losing the battle. We have to charge for our time and efforts. I am as guilty as anyone else. I love to see things happen, I'm not really good at numbers and business decisions. Eventually, we have to bring in more money than we are spending and burning. The old earn and burn ratio. It's part of business.

I think that both Steve and I really need some help, it's a hard burden to bear.

Wayne came on right around 10 am. We spent the next 30 minutes going over a bunch of things with Wayne. He is taking the servers to the whole next level. He is doing a great job. We went over some of his new fusion reactor stuff (adobe coldfusion monitoring), pingdom (web stats company), tracking server errors, code debugging, and talking about billing and support from our hosting companies.

We got into some discussions on ColdFusion mappings to help with revolving paths and variables in those path structures. We may end up looking more into this.

Finally, we had a small discussion about taking time for self and family. Important things.

Shannon and spent some time going over our structure and who we want to be as a company. We were going over some questionnaire answers from some of the core people on the team. Our main consensus is, we all like the independent dependable type model but we are seeing problems with that as we grow and scale. Eventually we like to become a community. Somewhat of a limited core with unlimited opportunities within the community. See attached for where we are working. Trying to make decisions and summarize input from the others who are helping us along this journey.

We ended with a small thought from Frozen II - do the next right thing. That's about all we can do or hope to do. Focus on the task at hand.

Danny reported in and showed me some research that he was doing on advanced PDF documents. We have some great code that works for simple to even moderately complex PDF's. This is all part of the merge sub PDF's project for a company. We found that even Adobe Acrobat, the main Adobe PDF product, couldn't handle the crazy complex, encrypted, password protected, postscript, you name it, files and be able to combine and/or merge them. That made us feel a little bit better. Danny will be reporting back to the client to show them what we are running up against.

Recording notes, emails, and more code work on the Bear 100 mile race event stuff.

Meeting with Cory and Steve. Talking about billing ahead of time. Doing a deeper dive into some of projects and prepping things for the developers. We made a couple of small fixes on the fly (quick code changes) and pushed files. We assigned a couple projects to developers. We still need to refine and figure out internal doors and gateways. We all get blasted with emails when they should just go to one person. We waist a lot of time not knowing who is doing what. We spent the rest of the time doing project management and prep work. Good session. We'll keep getting better at it.

I got an email from one of the race directors with some bib number and data changes. It took about 45 minutes to delete runners, change bib numbers, and alter contact info. Quite a few changes. After that, I spent the rest of the time working on the scenarios for the new bulk start page for the Bear 100 mile race. That event is this weekend. They use adilas for about 36 hours pretty heavily and then don't touch it again until the next year. Kinda interesting.

https://data0.adilas.biz/bear100/ - click to view the public runner portal for family and friends of the racers

Custom code work for the Bear 100 mile race. The race started this morning at 6 am. The new code was for calculating the finish based on new logic this year. Code was tested and pushed up.

9/25/2020: There are currently three fields in e-comm (two for quotes and one for invoice) that allow for messages once the customer has completed their order. This quote would enable the fields to be unlimited characters. This quote will also add the text editor function to the fields.  

Danny and Sean were on the meeting and wanted to get a report on the Bear 100 mile race from over the weekend. Fun report and they did great. They have used adilas software for 6 years now to run and track all of their runners, legs, and aid station timing. Over 900+ runner support comments were added by family and friends from the runners. Lots of good stuff.

Eventually Eric, Cory, and Steve joined the morning meeting as well. After everybody else left, Steve and I dis some light talks and sharing of some ideas on funding and management. We also pitched a couple of options dealing with adilas shares.

As a side note, we haven't done this yet, but in some ways, we are seeing more need to lean more heavily on the PO and invoice line items table. This could (potentially) allow for multiple locations, multiple dates, and other things on a per PO or per invoice level. This needs to be expanded more and detailed out. Currently, we control all dates and locations from the main PO or main invoice. Those values are cascaded down to the PO and invoice line items. We have seen needs where the line items may need more control over locations and dates, but we have not made that jump at this point.

Cory rejoined and we went through projects and other tick lists. As a general overview... we are seeing topics dealing with advanced accounting, sub permissions, and more requests for additional settings and functionality (mostly on the operations side). Steve once said, our focus is: "Does it deal with operations and accounting, then we are interested." I know that is broad, but that is what we do, operations and accounting.

We covered a number of different projects including: cash flow statements and deeper accounting needs, sub permissions, mixing new functionality with older permissions including view only permissions, age verification for ecommerce and new settings that are needed around the system.

We have Chuck, Danny, Steve, Sean, and I on the meeting to talk about gun shops, gun shooting ranges, and other business verticals. We have a big shooting range in Arizona that has been using our system since February 2014. We made some plans to contact them and setup a meeting to see what else they could use and/or would like to add. Just trying to find as many different angles as we can.

Towards the end, it was just Chuck and I left on the meeting. We ended up talking about operations and accounting and how you have to have the horse (operations) in front of the cart (accounting) and how that all works. Light training and chatting about options.

Emails and then meeting with Steve to talk over ideas and options. We spent some time talking about our ownership structure and options in case we wanted to see if we could get some more funding by offering a certain percentage (basic share stuff) and what that may look like. Just talking and playing around with ideas.

- Businesses - going up the chain

- Our optimal size seems to be high side of small and low side of medium. Basically, small but almost to medium.

- We are really good at building stuff on our platform

- Light talks about the adilas trust, adilas café and community

Working with Bryan and going over some of his Hypur payment stuff. We ended up talking about things, flow, and getting things all cleaned up and ready to go. We also looked at some of the other projects that he will be working on. Towards the end, Cory jumped in at the end and had questions about custom payment options.

Eric and I spent a bunch of time doing the launch of the customer loyalty points and the switch over to full ACV (actual cash value) of the associated points. Lots of co-testing and then pushing the code to all servers. We on purpose did this launch after hours. Late night session.

Eric and Sean were in the meeting talking about auto testing, good testing environments, and actual configurable testing servers. Sean was also talking about the need on the sales side for a good demo site that has all the data that is needed for the demos. They were talking about the difficulty with setting up data and keeping the data good. It may sound weird, but data can go bad if it isn't being used or if is not completed or missing key pieces. You have to have good data to really see the whole picture.

We are living in changing times. Talking about schools and other social changes that are taking place.

On the phone with Dustin and touching base on projects.

Shannon and I were going over our model and talking about structure and who we want to be. See attached for some of our work stuff.

Meeting a couple of guys from LetterPress Consulting. We had a lunch meeting to chat and talk about training, learning, and technology.

Their website address is: https://www.letterpressconsulting.com/

Eric, Cory, and Steve started talking about getting lined out on the item catalog. They started around 2 pm. I didn't join the meeting until just before 3:30 pm. I was at a different lunch meeting. We really need to talk with Alan, as he is working on the aggregate vendor list and master vendor catalog.

Bryan joined the meeting to help me push the flex attributes project. Steve, Cory, and I were still in our other meeting. So, Bryan left and we ended up talking on the phone for a bit.

Steve, Cory, and I were talking about scheduling and billing for direct time that clients need for deeper support or training needs. Not quick questions, but more in-depth stuff. We are getting booked out there a ways and some of the smaller time blocks are used up by normal day to day stuff. People still need help, but it is getting harder to just fit them in. We need to schedule them and bill for that time. Once again, this is for things just beyond a simple text, email, or quick question. We have to keep coving ourselves.

Emails, bug checks, and other to do list stuff.

Met with Chuck to go over things. We covered a bunch of his projects. We talked about the adilas docs (style guide, coding conventions, and expectations) project and did a little bit of work there. We went over some new WordPress theme changes and what that is going to look like. We use WordPress for our news and updates. We are going to make plan to launch those new pieces. We also talked about a raise for Chuck. That goes into effect on 10/1/20. Good stuff. The other topic was adilas financials and where things are going and/or heading.

Alan and Wayne jumped on the GoToMeeting session with me. We were looking at servers, git stuff, bugs, and auto update processes. After the meeting with Wayne, I called and talked with Alan about a raise. That will go into effect on 10/1/20. Well deserved.

GoToMeeting session with Steve Palmer and the Euflora team. We went over API socket questions, looked at some data, talked about logic and sub inventory stuff. We then switched gears and talked about security on images, uploaded driver licenses, signatures, and other customer based uploads. Towards the end, we talked about getting a custom report that shows all of the items and pieces associated with parts and general inventory items. This includes, normal parts/items (parents), parent attributes, part categories, web descriptions, product photos, and other related info. Good meeting. There were 4 of us on the meeting. Tamas, from their team, was very sharp and had some great questions.

Eric and I jumped on and worked together to get some new code launched for a client. The new code was actually putting an end date on an older custom loyalty points system. We pushed up the changes and did some testing.

After that was done, I recorded notes from the day and did email stuff.

Bryan circled back around and helped me launch round one of the flex attributes. It is only tied out to customers right now, but that is the first round of what we have done. The new code was pushed up to all servers.

As we keep going, eventually, we want to expose and release flex attributes for all of the main 12 players inside of the system. Some of the main 12 players are things like: customers, invoices, deposits, expense/receipts, vendor, users, parts and general inventory items, stock/units, quotes, elements of time, balance sheet items, and PO's. Exciting. This is part of a bigger project called real in-line database extensions. Step one is up and live as of today.

Working on a new tool to help exports final race results for the Bear 100 mile race. Working on a new tool that exports the final results.