Looking into server page stats with Wayne and Cory. Small bugs and tracking down sources. Wayne has released his new monitoring services on data 0. We were looking at page views and what not. The top page was the view cart page with over 22,000 views in just the first 5 days of launching the monitoring service. This is just on data 0, not even that busy of a server. Our servers get hammered, daily!

Cory had a number of questions for Wayne from emails and other projects that are circling around. We spent some time talking about memory issues on both the server-side and the client-side. This is kinda new, but we are starting to see more client-side memory issues. A normal page, the server handles all of the memory stuff. We can mostly control all of those pieces. On some of the new and fancy heavy JavaScript pages, it gets to be a big client-side load in order to keep all of that data quickly at hand (data loaded on the client-side in the browser). We will keep working with stuff, but may have to break things down into smaller and smaller pieces.

Some of our pages may need to be refactored. They are doing too much and/or requiring the browser to work too hard or store too much info. This may be something that we need to be aware of for our future fracture project. We have to balance both client-side and server-side memory management stuff. Just because we can use AJAX and JavaScript and cool data tables, that may not always be the answer. At some point, even those things fail. We need a good mix of both and make it as smooth as possible.

Recording notes from yesterday and today. Making a few entries in both the adilas shop (these entries) and some over in the main adilas site for subs of time and project timeclocks. Emails and other clean-up stuff.

Finished up some changes on the custom data export and data extract for a client. Pushed up a temp file and did some testing. Sent an email with information and plans.

Good phone call with John. We were going over progress on his discount engine project and touching base on general business stuff. We covered all kinds of topics. Most of it was dealing with changes, communication, direction, plans, carrots (rewards), and punishments. We also got into topics dealing with budgets, changes that are coming, and numerous upcoming projects and details about those projects. I thought that it was a good call.

Emails, recording notes, and small bug fixes. Working on some pagination issues when doing customer searches - both basic and advanced. Bug was reported by Sean. Trying to clean off my desk a bit.

Emails and then working on the custom data output or export for a client. Pushed up a new file with some changes and sent them an email.

Emails and going through things. Wayne joined the meeting and we chatted about the cfinvoke tag (code inside of ColdFusion that calls a method or a function in a library of code). We also got into how if it (the cf invoke tag) is used in a loop it uses a lot of system resources and memory. Basically, it has to copy the whole CFC (coldfusion component or class) every time that it is used. If it used in a loop, it won't be able to cache it and it rebuilds it every time, however many time it loops. Anyways, we have a number of these spread throughout the system. Wayne was saying that we could speed things up if we made some changes and used the Application.cfc to setup the initial component or classes and then refer to that in our loops vs building it every time on the fly.

We went over some samples and he showed me what it could look like. He is going to start making some changes and we'll go from there. Eventually, we'll need to cascade new code all around the system. One little step at a time. As a side note, our whole conversation this morning was having a "progression over time" type feeling. Basically, we start out with something, then it grows, then we modify it to make it better and faster. All part of the process.

Next, we got into some other talks about memory management and efficiency of certain tasks and procedures. Wayne was talking about some new try's, catches, default error throwing, and some new flow. Part of Wayne's desire to make these changes deals with automated testing. If we change things, it makes it better for automated testing. Currently, a couple of the things that stop the automated testing is hard aborts and page includes. If we can get rid of those and just use catches and throws, it becomes better for testing.

The goal is continuing to tighten things up and refine things and processes. Wayne is playing with some global trim functions and how best to push those pieces through our code. Right now, we trim everything that a user may interact with (URL and FORM scope variables). Basically, Wayne is "salting" little pieces of experimental code throughout the system, trying to help speed things up.

Recording notes from my meeting with Wayne this morning. Lots of refinements and memory management stuff going on. Small tweaks every day. Slow and steady.

Back working on the bulk flex grid tools. It took a little while to get back into the project. That makes it tough. It's been a couple of weeks and then a couple of weeks before that since we worked on this project. You sort of lose a little bit of traction due to time away from the project. Anyways, got it back going, reviewing code, and slowly making progress.

Most of the work this morning was dealing with gathering and organizing the bulk edit process. Lots of data coming across, some of it is the same (no change), and some of it has been changed. Trying to keep track of what has been changed and what pieces need to be taken care of. Lots of dynamics and looping to get the dynamics to all work out.

This might be kind of techy but, the big bulk edit page keeps track of each line item id number, each field is named so that it has the line id embedded into the field name. We also track what has been changed based on some JavaScript on that page. The JavaScript keeps a list of values and then passes it to the action page. Once on the action page, we build a structure to hold all of the id numbers to keep it organized. We then loop over what has changed and figure out field names and corresponding values and place them in arrays that are assigned to the correct line id's. Once everything is sorted out, you have to loop over the correct arrays and do database updates to make things stick. Imagine if you had a hundred fields being passed back to you through a bulk edit process. If you only changed 5 fields, you only want to update those values, all of the other data needs to stay as is. It can get pretty deep, very quickly.

Deep in action land for the bulk edit flex grid tie-ins. Tons and tons of crazy dynamics. Getting closer and closer to what we need the page to do. It's a refinement type process. Start with a jumble of data, then slowly whittle it down to usable pieces, then actually make the rubber meet the road and make it stick in the database.

Finished up the first round of the bulk edit flex grid tie-ins page. Lots of testing and small tweaks. Pushed it up online and let a few people know about it to go in and do some live testing.

Steve and Sean were going over sales and issues syncing up with Metrc values. They are working on some changes. That seems to be an ever-moving target.

Steve had some code questions for me, and then we went over some ideas and options dealing with when to loop and when to not loop over arrays, based on the values needed. Light code help.

I spent the rest of the morning doing emails and recording notes from yesterday.

Steve and Cory were talking about looking up projects in bit bucket (code repository stuff). Being able to check on commits and branches. They were then talking about different industries and how they are financing some of their developments. Lots of games that people play and how do we fit into that mix. While Steve was still on with us, Cory was reporting in on some meetings that she had had with Kelly dealing with the adilas label builder and sub inventory attributes. Both of those subjects seem to be heating up a bit.

Our current goal is to focus and try to get some small victories (projects being done and across the finish line). Cory and I spent some time going over projects. We talked about the need to test everything. Even small stuff. We have had it bite us before. Next, Cory and I looked into a possible bug in some settings. We looked and looked and couldn't see anything quickly. We may have to jump in deeper, when we get a chance.

Shari O. popped in and had some questions about getting a new internal email server. Our current solution has been giving us some problems lately. We don't change any code on our side and it works great, all of the sudden it will be down, and without any changes on our side, it all of the sudden starts working again. Kinda crazy. Shari O. calls it the gremlins or email gremlins. As a side note, later in the meeting she popped back in to let us know that it was working again. Random.

Wayne joined the meeting and got Cory and I up to speed on a few things that he is trying to work on. Performance tweaks.

Cory and I then started going over her list of possible projects, quotes, and estimates.

- Need quotes for inputting sub attribute data all at one time upon PO creation (start with build page)
- Bulk update sub attributes interface
- Mapping of EOT (elements of time) data to sub attributes (settings for cultivation and manufacturing)

Along the way, we were talking about options and settings that relate to the concepts of the data assembly line, recipe/builds, showing subs in the packaging and production pages, and managing recipe/build output better. Lot of talk about bulk edit tools for sub inventory attributes, batches, phasing, sub locations, and moving subs along a known path or virtual assembly line.

Dealing with the data assembly line concepts, I was telling Cory how we setup both rules and assignments for smart group buttons (tiered pricing buttons). I was mentioning that we could use something similar to help setup and do the mapping between elements of time, sub phases, sub locations, sub groups, and monitoring the progress of certain things. We need the rules (what or how to do things) and the assignments (who or what to connect or monitor). Using the two pieces in combo (rules and assignments) we could then have the computer and/or system help us monitor progression and progress. They are good at that, they just need instructions and the who, what, when, how, and why and they can do those jobs over and over again.

As we keep rolling more and more towards the concept of fracture (future adilas project) I would really like to keep working on the data assembly line concepts and using rules and assignments to get the correct flow and mapping in place. I see that as important as we keep going forward.

Recording notes from this morning's meetings. Something is always going on.

Phone call with a client. Passing on some updates and information. Spent some time looking into a bug that Cory reported. Found the bug and pushed up new code. Emailed both Cory and Steve about what I found with the bug. It ended up being a date sync thing. One of the custom pages had a date sync option tied to the settings. Every day, the sync would check the stored date to see if it had the latest info. It would resave the settings and thus refresh itself. The auto process was saving most of the old settings but setting some of them to a default value vs holding the older settings. That was the problem.

Took the rest of the time and worked on pushing up Chuck's new code to expand the time - sub date/time notes field. It was limited to 255 characters. We expanded it and allowed for HTML in the new text field (65,000 character limit). Ran the database update on all servers and pushed up code and did some testing.

Wayne was unable to attend today. Just Cory, John, Sean, and I were on the call. We started out and I reported on some of the projects that I had been working on. Two of note were the first round of the bulk update flex grid tie-ins for the bike shuttle company. This is dealing with persons being attached to a calendar event or element of time. I also reported on the update on the time sub date/time notes and expanding the field to allow HTML and more characters.

Cory had some questions about servers and memory management stuff. We talked about projects, costs, budgets, and skill levels of the developer who were assigned to certain projects. One of the side notes here was the high cost of code maintenance. It's part of our game. We just need to charge enough that we can continue to keep things up. Often we get tricked into just charging what the project costs (at the time of development) and totally forget that later on we will have to do maintenance on that code as it becomes part of a bigger whole.

Chuck joined the meeting. Cory was still on from the last meeting. She quickly reported to Chuck about the video for the adilas label builder that he had done. Cory had showed it to kelly and had gotten some good feedback.

After that, Chuck and I talked briefly about 3D printing and building in supports for more complex projects. This was just for fun.

We got into a small session and talked about financials and available hours, based on projects and budgets. We hopped into the system and looked around. After that, Chuck and I spent some time looking at his new code for the working with time page for elements of time. Lots of layout and UI (user interface) changes. It is looking good. Big lift and Chuck is adding tons of new code to help with the layout and such. He is somewhat experimenting with different layouts and formatting options. I thought that it was looking good.

The last topic of the session was dealing with maintenance costs going between the older classic code and the newer snow owl look and feel theme. Some of our pages are doubling due to the amount of code to handle both versions and/or themes. Once again, a maintenance deal - hidden costs.

Meeting with both Bryan and Chuck and going over the progress on the ecommerce side for client facing scheduling. Bryan is further along than I thought. That's awesome and we'll be hitting this project harder in the next few days.

Emails and recording notes. Helping Bryan with some merchant processing settings. Email back to the guys at Hoodie about one of the custom data export projects.

Use for general project management stuff. Add details to the notes.

Phone call and then jumping on the GoToMeeting session with Eric. Going over some FORM and URL scope variable stuff for the gift card project.

New changes to the output for the Hoodie guys. We changed how the sub attributes were displayed, took off some URL encoding formatting, and forced some of the JSON object keys to all lowercase. Other light changes, at their request.

Recording notes from earlier today during the different meetings. Both here in the shop and also added some inside of the adilas system.

Emails and clean-up from the day.

Steve and Sean were going over gram controllers and all kinds of ratios and scenarios. It sounded like a deeper need for real mini conversions dealing with ratios, sizes, weights, packaging, units of measure, and such. They were kinda going in circles and ended up making some decisions to just fake it a bit. Basically, they (an outside party) was not providing them the correct information, so our guys (Steve and Sean) were just going to make it work and make some assumptions. The communication back and forth has been non-existent between the state compliance service and our company. That makes it really tough. So, we are just going for it.

I was working on coding in some updates for the bike shuttle and auto updating budget counts based on flex grid tie-ins to certain events and elements of time. When Steve and Sean got finished, I ended up giving them a demo on where the online scheduling is going and headed. They enjoyed the demo and saw some good potential.

Steve had to take off and Sean and I looked at a small marketing video that Danny was working on. They are trying to make a number of small adilas tip videos to help with some of the marketing and sales efforts. Anyways, we will give a few of those a try to see what kind of response we get. After that I spent some time paying some bills.

Meeting with Bryan and going over the flex grid tie-in portion of chaining elements of time and flex grid assignments together. This is how we are virtually claiming seats or availability on the bike shuttle project. After the meeting, I finished up some code to help do a bulk update of the budget numbers that were tied to the flex grid record counts. Currently, this file is not part of the master branch but Brandon has it on his computer, if ever needed again.

Working on custom code to keep the budget counts up to date on the fly. Lots of testing and distributing code around to where it goes. Pushed up new files.

Quick GoToMeeting with Chuck to go over assigning flex attributes to elements of time and how all of that stuff works. Text messages to developers helping and pointing them in a good direction.

Paying bills and recording receipts.

Steve and Sean were doing another bout and going over BioTrack API sockets and connection stuff. They are making plans and trying to see if they can get other doors to open up. Some of these integrations with State compliance systems are pretty deep and keep changing. That makes it tough. It also changes from state to state and that makes it tough as well.

We switched gears and were talking about servers, stats, and traffic. We had some slow down on data 0 over the weekend. I showed Steve and Sean a couple little reports that both Wayne and I have made to help monitor certain page usage and application flushes.

Cory joined and she and Steve were talking about Metrc and their servers getting maxed out and having timeouts. We are so tightly integrated, that when we are up and they are down (Metrc) it makes us look bad, even though it is completely out of our control. More talks about BioTrack and other 3rd party solutions. They keep popping up here and there.

Cory had a list of questions and things that she wanted to go over. She asked about how the top 15 customers were figured out on the some of the dispensary homepages. We went into the code and looked around. We went over invoice due dates, how to allow customer/client terms to show up on invoices, and other projects.

The next major topic was parent attributes and parent attribute sorts. We talked a lot about reworking all of the sub inventory pages and our virtual wish list with regards to sub inventory and parent attributes. It is super flexible and very needed. It currently works but could use some enhancements, polishing, and refinement. Never ending process.

Along those line, there has been requests for better bulk tools for both parent attributes and sub attributes, better reports and advanced searches, and ways to speed things up and make it even smoother.

Cory and I went over some quotes and talking about the need for better project management for our internal projects. We are really good at doing just in time project management but some of our project really need some more base level requirement and expectations out of the gates. Sometimes we hand our developers a simple one liner and then they take off. They just need a little bit more instruction and direction in writing vs just talking and verbal. If good notes weren't taken, things fall through the cracks.

Cory and I going over the quote for the upgrades to the adilas label builder. Cory had the quote open, we talked about each line item, and she asked some questions from a meeting with Kelly.

Small demo on the automated budget settings for the bike shuttle company. We also talked about testing and tech support demands.

Use this time id for work done to help promote and do the custom code work for the Bear 100 Mile Race for 2022 and 2023.

Meeting with Bryan to go over questions on the client facing scheduling project. He had a few questions and we went over possible options. We will reconvene at 3 pm today to work more on the code.

Going over post-it notes and recording entries from last week and this morning.

Bryan and I jumped on a GoToMeeting session. We were doing code review and taking a really detailed look into why certain things were added. We were making notes and plans and trying to streamline things. Good session. Planning on another one tomorrow afternoon.

Phone call with the new race director for the Bear 100 Mile Race. His name is Cody Draper. We went over aid station changes, when I need runner data and bib numbers, and how the invoicing will work. The plan is to invoice him after the race at $4/runner that starts the race. He's excited.

Clean-up, text messages, recording notes, and logging time for the day.

Pretty quiet morning meeting today. Sean popped in for a bit. Checking out options and classes (training sessions) for the upcoming Adobe ColdFusion convention in Las Vegas. Flipped over and did some work on a customer data extraction project for a client.

Working on the custom data extract project for 710 Labs and Hoodie Analytics. Made the new formatting changes more permanent. Sent an email out to Wayne for him to do some of his magic.

Working with Bryan over a GoToMeeting session. We spent the whole time working on the client facing scheduling and going over code, AJAX calls, and detail work on the project. Good work and review session.

Small demo with Cory and Sean going over the upgrades and progress on the client facing scheduling stuff (10-15 minutes). Wayne joined the meeting and we jumped into our weekly server meeting. First off, Wayne gave us a report on his wife's progress (health stuff). Going over a number of different subjects. See the attached notes. At the end, John gave us a quick report as well.

Chuck has been feeling under the weather for the last couple of days. We spent most of our time going over the new code on the working with time (elements of time) page. It is looking good. He had a number of to do list items and we were going through them. Making some decisions and helping him test some of the data driven code options. As a side note, some of the pages are getting really big with the new display code mixed in with the older classic theme. This page is over 8,000+ lines of code just for the working with time page. That's getting pretty big, for just one page.

Light talk about the Bear 100 page and using the mobile ready version this year for the public facing race stuff. We need to get the events page up and going.

Working with Shari O. on the USAePay accounts and settings for a client. She has been working really hard to get things going and fully set and done for the client. Trying to get some of their API socket keys to work and play through for their virtual terminal payments. On and off mute, conference calls, tech support, and GoToMeeting screensharing. Kinda all over the place. We had two different sessions totaling about 45 minutes in total.

Phone call with Eric talking about gift cards and USAePay accounts. Running ideas and scenarios between ourselves to make sure that we have things covered.

Emails and then working with Bryan. We did another multi-hour work session on the client facing scheduling stuff. Going over AJAX calls and refining the pages to handle errors better and make the process a little bit smoother. Good work session. Mostly working on the time helper page.

Emails and recording notes from both today and yesterday. Recording in both the shop and on certain adilas specific projects.

Steve and Sean were talking about merchant processing and where we are headed. Good ideas and plans. Shari O. popped in and we ended up on a 2 hour call with Newtek and USAePay. We were debugging our integration with the USAePay virtual terminal - merchant processing stuff. We originally did that integration back in 2009.

It got a little bit frustrating because it would work if we only had a single account with the correct API keys. Once we got into two different accounts, then it fail depending on which account was first (alpha sort order based on the account name). We ended up finding a small bug dealing with how the system choose which account to use, in the multiple account environment. An account id was being passed on to the correct pages but it wasn't sticking. At one point, we had Shari O., a guy from Newtek, a lady from USAePay, Eric (one of our developers), and myself on the meeting. We just couldn't figure it out. We were doing traces, testing, creating new accounts, trying it from different servers, you name it. I'm so glad that we ended up finding it.

Phone call with Eric to go over what we found from our earlier meeting. He and I were lightly looking over the code, without jumping in too deep. After the phone call, I jumped in deeper and spent time chasing down the bug that dealt with the look-up value for a single merchant account.

Got on a GoToMeeting session with Alan to work on and fix a bug in the USAePay integration. We got pretty deep into services and then cascading new code around to 20+ pages. Good little work and training session. Pushed up new code and did some testing.

Working with Bryan and going over the customer facing scheduling stuff. Lots of code review, testing, and refining things. Today we were dealing with the elements of time look-ups and new add to cart buttons. Other small tweaks and refinements.

Emails and light clean-up from the day.

Recording notes and time for the past couple of days. Logging things in both the shop (more details) and inside of adilas (summary timecards).

New week. Sean joined the meeting and we were just touching base on happenings over the weekend. Steve joined the meeting and the three of us were doing a little bit of catch-up. Steve has been working on the gram controllers over the weekend. Small report there. We talked about how we are constantly rewriting our software, daily tweaks and modifications. Good stuff.

Steve showed Sean and I a huge PDF proposal that he and Mike from Herbo and Eco Science have been writing up and getting ready for a possible big contract. The Herbo pitch uses adilas as the backend accounting and frontend POS (point of sale) system. Interesting mix and Mike is really pushing on things.

As we were talking about pitches and sales, Steve and Sean were rolling over ideas of selling or pitching smaller pieces and doing some local marketing on certain parts of the system. Sometimes we pitch the whole thing and that is so big it scares people away. We do tons of little things, we just join them all together to make up the whole system or platform. Depending on the situation, we may need to only expose smaller pieces at a time.

Everybody else left and John and I were doing some back merging of the master code branch into his local code branch. We were manually comparing old and new files. Trying to keep things updated.

Eric and I going over progress and questions on the gift card project. We spent some time looking over code that was trying to mix both client-side and server-side logic. We decided to keep them completely separate. Making plans and decisions.

Good work session with Bryan. We were looking over code for the client facing scheduling project. Pushed up new code. Bryan is going to keep advancing the ball tomorrow. Most of our work was following the add to cart process and watching things all the way through to the invoice creation and adding the correct flex grid values. We also started to work on adding scheduling from the view item detail page (second pathway through ecommerce). The full path from the shop homepage is already done. This new stuff is a second way of doing it.

Towards the end of the meeting, Bryan was asking some questions about his other project to show/hide customer terms on all of the invoices. We went over a few things and he took some notes.

Working on the code for 710 Labs and Hoodie Analytics. Small output changes to get rid of counter sale (dummy) data. Sent out a few emails and tried to run the historical report.

Steve and Sean were talking about sales, display booths, and conventions. We had a couple of people staffing a live event this past week. They are going to be talking with them today and going over questions and what not.

Steve was asking for updates on a number of projects. They (he and Cory) are going to be starting to implement some due dates on some of the projects that just keep going and going. We need to find a good cap or breaking point. This will be a new change, on some of the projects. Currently, we have some projects that go on and on for months on end. Progress is being made, but the finish line is unclear and thus it just keeps going and going.

I gave Steve and Sean a small demo on the progress and new stuff that we are developing for the online client facing scheduling portion of ecommerce. We were going over things for 10/15 minutes. After that, they both had to bail out and jump on another call with one of their guys. I spent the rest of the time going over emails and follow-ups.

Touching base on projects between Cory and I. Wayne was trying to connect but was having connection issues (he was driving). Once Wayne was able to jump on, he and Cory were going over back emails, client requests, testing plans, and projects. Not sure when, but most likely we will be needing a new primary email server here soon. That topic is gaining momentum and heat. We currently have a solution in place, but it feels like we are growing out of that shell (virtually).

Dealing with the email server code, I need to gather things up and get a copy of those files over to Wayne for review. I'll just go grab them off of the old shared server and send them over to him in a zip file. He wants to look over the old code. It is not currently in our master code branch, because it gets deployed on a separate server.

As a group, we talked about the next project for 710 Labs and Hoodie Analytics. They want a good daily inventory snapshot plus info on committed inventory (items that are on a transitional invoice - at the time of the report being pulled). We will try to get to this later this week or first part of next week.

Towards the end of the meeting, both Wayne and Cory and Wayne and John were coordinating plans and meeting times between themselves. After Wayne left, John was giving Cory and I a small run down on the changes and plans for the discount engine. We are going to be putting a deadline on this one as of October 1st. We really need John to switch gears and help out with some payroll and end of year forms and what not.

Started out with Cory and I going over projects. We touched base on multiple projects. We even spent some time going over existing code and how it worked and functioned (logic questions on customer terms and invoice due dates). We talked quite a bit about merchant processing and both existing options and future development options.

Cory wanted us to look into some code on one of the homepages that showed the top 15 customer/clients based on invoice counts. We looked for a good while but didn't see anything. I took some notes down and wrote them in my digital scratch file. We may have to circle back on that one.

After Cory left, I stayed on the meeting for a bit. I ended up calling the bank and requesting that our daily limit for expenses on our bank card get permanently increased to handle some of our expenses to the hosting company that we use. We spend thousands and thousands a month on hosting fees. Lastly, Chuck and I jumped on the GoToMeeting and I helped him out with a small bug fix on his local development environment. Busy morning!

Light tech support on usernames and passwords. Recording notes and doing some clean-up and catch-up stuff. Bryan and I jumped on a meeting and went over progress on the client facing scheduling stuff. He has it working on the view item details page. We still have a little clean-up to do, but it is looking good.

Good meeting with the Bear 100 radio admin team. These guys and gals will be the data team that helps run the event behind the scenes for the live runner tracking portion of the race. We had six people on the meeting and we spent some time going over the custom Bear 100 runner interface and special custom pages. Small demo, training, and navigating through the different pages of the site. Open Q&A session. Good meeting.

As a fun side note, this is year 7 for the Bear 100 using adilas to help them track the backend runner data. This includes runner details, contact info, aid station times, running legs (between aid stations), and finishing results. The site also has a social side or what we call the public runner portal. From there the runners, their crews, and their families can watch the event, track their runner, add photos, and upload comments and encouragement. Good stuff!

Bear 100 pages and making new pages more dynamic to help with future years and changes that are needed. Changing from hardcoded values to more dynamic variables. Cascading changes.

Emails and recording notes. Pretty quiet on the meeting today.

Working on code changes for the Bear 100 mile race. Took out an aid station, changed some aid station names, and had to rechange all of the aid station numbering. Doesn't sound very tough, but it was quite a bit of work. Going page by page and making the changes.

Tons of changes on the Bear 100 files. Updating dates and aid stations. Testing JavaScript to help with the photo and image uploader. Finished up the code and pushed it up live. I also spent a few minutes and touched base with Bryan on the client facing scheduling and where we are headed with that project. It should be online here in the next couple of days. Good stuff.

Talking with Sean and showing him some stuff with the Bear 100. Looking into Chuck's event code for the events page. Demo and showing Steve and Sean the new events stuff. Small brainstorming on sales ideas and trying to do more special events and such.

Chuck and I working on the printable time page. Going over JavaScript stuff, bootstrap 5, and new stuff. Talking about investments.

Pushing on the events page. Got it up and live and ready for the Bear 100 race.

Working on some new verbage to help with a news and update for the Bear 100. Click here to see the final news and update that Cory and Marisa made.

Took the adilas events banner into town and handed it off to some guys who were going to be putting it up at the pre-race meeting, the starting line, and the finish line.

Work session with Bryan. We were going over code for the online client facing scheduling stuff. Most of our session today was inside of the public facing shopping cart. Going over all kinds of scenarios and online booking stuff. We made a list of to do list items and planning for a public release next week. Things are moving right along.

Working on the backend of the Bear 100 radio admin pages. Going over the import CSV code and working on the main custom backend homepage for the Bear 100 radio admin folks. Also working on other backend pages that go along with their custom interface and special pages.

Bear 100 files. Updating the runner counts and working on the still out running pages. Emails out to the radio admin team. Working on the manual update for a single record. The actual race had already started and I was still working on some of the backend admin pages. Somewhat behind. I had all of the start and first few aid station stuff done, but cutting it kinda close. Finished up around 10 am ish.

We flipped a bunch of aid station numbers around this year. We also dropped a full aid station. I spent a bunch of time on Saturday morning tweaking the code and making sure that the public runner portal was showing the correct information. Going line by line and doing some super deep debugging. Eventually, after checking out the underlying code, I ended up changing where the finish line aid station buttons pointed in order to fix the problem. I had to make sure that the report pointing to the finish line was fully closed vs just the start of the last leg from Ranger Dip (aid 12) to the finish line (aid 13 or finish). It got pretty deep.

Checking stats, uploading photos and comments into the Bear 100 runner portal page.

I had to join late. Steve and Sean were talking about sales, live events, networking, and different angels. They were also talking about the use of videos and stacking the model. Imagine the base of a pyramid - how to set it up, then how to use it, and at the top (ish) what we have. Let them drill-down as deep as they want to go. All of this deals with client acquisition costs and what it takes to keep and maintain a customer or a client.

Next, we jumped into speaking about client facing scheduling and where that is going. We are making tons of progress there. After that, we talked about the Bear 100 mile race and seeking some ROI (return on investment) from some of those special or custom interfaces. We talked about seeing what is next and talking with the race direction. Trying to get ideas and keep making it better and better. All part of the process.

Cory and I were touching base and checking in on a number of different projects. Talking about working through failures. Lot of talks about permissions, settings, and sub permissions or sub functions within the bigger permission. It gets deep or could get deep. Some people don't care a lick. Others want to control things at the smallest granular levels. Interesting, how different people's agendas are.

We also got into settings and sub settings. More quotes on new and upcoming projects. Planning and figuring out next steps on existing projects. Small update from John on his discount engine code.

Code review with Bryan. We were surfacing the customer credit terms on the different invoice views (mini, printer friendly, PDF, edit line items, etc.). Big merge and testing process. Pushed it up live on data 0.

Small work session with Eric on gift cards. We were adding in code to help setup the quick search for gift cards.

I got a spreadsheet from the race director to edit and update a few finish times for the Bear 100. Manually updating records and documenting with notes.

Code review with Bryan on the client facing scheduling project. Going over new changes and working on some of the dynamic naming and hardcoded variables. We had to do some clean-up with git and bit bucket. Spent some time chasing layout bugs. Good work session.

Clean-up and comparing data from a spreadsheet to what we had on the live database system. Back and forth comparing all dates, times, and values. Ended up only changing 4 records. I was wishing that I had a better tool or that the race director had flagged the ones to look at. Lots of back and forth and comparing things.

I joined late. Steve was already on and Sean had already been on and left. When I got on, Steve and I were chatting about the Bear 100 mile race and some thoughts and ideas. Steve had the idea to put some kind of stats or leader board dashboard on the public runner portal pages. A quick 10,000' overview. For example: (pretend that the letters are numbers and that it looks cool) x signed up, y did not start, z started. We then could show where everybody is at... x at this aid station, y at this aid station, this many finishers, etc. Basically, a quick dashboard type overview and add some eye candy (stats and counts). Show the tip of the iceberg and then let them drill down as they get the data.

This led us into a conversation about transitioning into graphical homepages with quick snapshots, quick numbers, counts, maxes, mins, averages, and other quick aggregate values. We would love to add this in for our fracture project or fracture concepts. Do this on every page. Alan did some small graphs on the main invoice homepage. We want this spread throughout the entire site. All of the key player groups - (customers, invoices, quotes, items, stock/units, elements of time, balance sheet items, deposits, expenses, PO's, vendors, users, etc.).

As part of the server meeting, Wayne was reporting on progress and status of his wife - health issues. We spent quite a bit of time looking over a number of requests that Cory had. I sent Wayne a zip file for all of the existing email stuff (code and assets). The email server is being more of a topic lately. We will need to do something there soon.

We also spent some time talking about the content server and the disk size of what we are storing for clients. It is getting quite large. We talked about the accumulative sized and storage costs over time. Looking into other options, costs, prices, and other servers to help handle the current and future content loads.

We got into database stuff and talking about sub inventory stuff. Tons of bulk tools are wanted and needed. Another topic that we got into was dealing with training and lack of training. This was dealing with existing features inside of adilas and/or different 3rd party plugins and libraries. This topic led us into talking about maintenance and doing the right thing. That's a constant battle. Another huge vote for maintenance and education. Two huge concepts that may end up being better than new features. Something to remember as we keep heading towards the fracture model and project (maintenance and training/education).

Chuck and I talking about automation and tech for the Bear 100. Making it cost effective and still high tech. Looking at mock-ups for the time homepage. See attached for a first round mock-up of the time homepage.

Small fix for the max characters for emails. Pushed up new code.

Switched to the client side or client facing scheduling project. Spent the whole afternoon merging in code, prepping things, and getting ready for a client demo. Lots of time working on the actual demo site to get new events, descriptions, and photos in place for the demo.

Checking in with Sean. He's been prepping for some different demos. He demoed a hair salon yesterday. They really want some client facing scheduling options. I was going over emails and doing my own prep for a demo on scheduling that we are doing this afternoon. John joined and was asking some questions about the state of business and how adilas is doing. They have permissions and can look around, but sometimes it is easier to ask someone who knows.

The final topic for this morning was talking about dashboards and good-looking eye candy - graphs, charts, and aggregated summaries. That is what people really want.

Prep work on the client facing scheduling project with Bryan. We also did a full one-hour demo with the guys and gals from High Valley Bike Shuttle. We had a number of adilas folks on the demo as well. I think that we had 12 people on the demo. I did a portion and Bryan did some training as well. Good stuff! After the meeting, Cory, Bryan, and I did some additional talking and wrapping things up.

Recording notes form the past week. I have been under two different deadlines and haven't had time to get caught up. I can actually breath right now. Yeah!

Sean and I were talking about online scheduling. We have a good one-to-many solution that just got released to the public. We would like to build out the one-to-one client facing scheduling portion of the system. You can do it inside the system, but that part is not yet exposed to the outside or client portals (ecommerce land).

Steve joined the meeting and we were talking about chipping away at the settings to help with the client facing scheduling. That ended up leading into a discussion about our developers and what size and type of projects are good for each person. We have some of our guys get lost (for months on end) because the projects are so large.

One of our goals going forward, will be to use more of a step-by-step guide or wizard type approach with check lists and crumb trails as to where we are in the process. Basically, breaking our bigger projects into super small baby steps. That way they could have one thing to do and could actually get it done. Once that is done, they could start on the next piece. Basically, a small and limited focus with defined parameters vs an huge open field.

Meeting with John and Cory to do a code review on the discount engine project. John started out by talking about a class that he is taking at school and a section called "Requirements Engineering". He is going to pass on some information to both Cory and I. One of the main goals or strategies of that requirements engineering is being able to see and quantify those requirements.

We talked briefly about taking the time to get it right vs having to go back (again and again) to do other maintenance or backing to back track. I agree with that, however, there are times that you just need to get it done and you know that you will have to circle back around and fill in the gaps. There is not just one answer for every possible solution.

Most of the meeting was a code review session. John walked us through the process and did a great job verbally walking us through his code. If we had questions, he would take and show us on the discount engine why, what, and how he was doing certain things. I thought that he did a great job explaining his code. We made a few recommendations, but mostly it was him telling us and showing us what he has been working on. He is getting really close and is starting to work on the action page to really get the stuff to stick in the database. The frontend interface looks great.

We got into caching of objects, memory usage, and memory management topics. We spent quite a bit of time going over custom JavaScript that he had to set up to make his little one-pager work. One of the interesting things that he and Wayne are coming up with deals with using the users to help run the database updates based on automation processes and usage within the system. Most of John's new code is all in script vs the older ColdFusion tag based language. He likes that style way more and it feels like other languages that he knows.

The last topic of the joint meeting between Cory, John, and I was dealing with team building and getting enough training to help us all do our jobs and help spread the love, dealing with knowledge and training. After Cory left, John had a few other questions about finances and checking on the health of the business. Great meeting!

Meeting with Cory to go over projects. Cory was asking all kinds of questions from her little list and from email chains that have been going back and forth between herself and our clients. We then moved on to some new projects and getting numbers, estimates, and quotes. One of them, a client wants a bunch of data out of the system. As we talked about it, they are wanting huge one-to-many relationships exported into a CSV file (comma separated values). We spent some time and talked about relationships and where CSV files work great and where JSON (JavaScript Object Notation) files work much better, especially if you have multiple deeper or more complex relationships.

We spent some time talking about the client facing scheduling and where we are heading. We have determined that we will end up with three different types (for now). The three types will be listed below. The main variables that we are watching for and tracking are: What is the date or date/time combo (when)? What product are they wanting (in case there are multiple options - what)? And how many people are participating (quantity, seats, participants)? Those are are three main variables we are watching - when, what, how many.

Plans for different types of online bookings:

1. Daily/weekly reoccurring with multiple participants. This deals with known and pre-set dates and times. We already have the rough schedule and just need to see who will be participating in each preset event. This is a normal one-to-many relationship with time being the one and the participants being the many. For example: like a shuttle service or ongoing event - pretend that we are going to offer a shuttle from point A to point B twice a day. We can hold 35 people per trip. This is a perfect example of the daily/weekly reoccurring with multiple participants. Think of selling seats or counts per event.

2. The next one is very similar but instead of being a daily/weekly reoccurring event, it is more of a special event or unique event. This will still allow for the same one-to-many relationships, but the dates are not as constant. That factor, the frequency of the date/times makes each event be unique. For example: Say you had one trip to a certain destination with multiple people going on the special trip or something like that. Because we have already plowed the path for the reoccurring one-to-many (listed above), this one should be pretty easy. Think of booking seats or counts for a special event (non-reoccurring or reoccurring but with special date/times).

3. The third option for scheduling time will be the one-to-one relationship. This is more of an open calendar and setting up what time slots are available. For example: Say a person wanting to schedule an appointment or get a haircut. The company or users would setup a basic template of allowed time slots and then allow for those time slots to be filled. The one-to-one relationship comes with one element of time holding info for a single client or customer. Basically, the quantity is assumed at one. This type of online scheduling could be used for campgrounds, doctor's offices, hair or nail salons, consulting services, etc.

After we discussed these options, in some detail, we talked about settings, next steps, and plans. Good meeting.

Bryan and I were working on finishing up the email history stuff. Working on query errors and debugging. The error was dealing with payee id's (user stuff) and dummy records. We were checking code and dealing with referential integrity in certain places. Lots of relationship stuff.

Prep work for Drew at the High Valley Bike Shuttle. Talking with Eric about gift cards and logic. Looking into what it would take to get to the bulk edit parent item's core values. I ended up having to ask Sean. Fixing settings and prepping for ecommerce stuff for the bike shuttle.

On the GoToMeeting session with Bryan. Working on a small code update and code sign-off for the automated emails project. Merged and pushed up files.

Prep on the High Valley Bike Shuttle site. Working and doing some clean-up to help them get ready for ecommerce and online client facing scheduling.

Phone call with Drew and walking him through some of the client facing scheduling stuff. It went live on his site today. Exciting times. Sent a few emails out to folks with links to the High Valley Bike Shuttle online scheduling pages.

Phone calls, emails, and light tech support with one of our clients.

Went into Smithfield to meet with Cody Draper from the Bear 100. We met at his house and went over pros and cons from the 2022 race that happened about a week ago. He seems pretty happy with how things went. This is his first year taking over as the new race director. We took some notes and chatted for a bit. He is looking to push the system forward. We did some consulting and will be modifying things before next year's race. Good stuff!

Emails, phone calls, and tech support. Talking with Drew from the bike shuttle company and helping him setup and save some custom reports to watch and monitor his online sales and online client facing scheduling and bookings. We setup three reports for dollars made from online bookings (invoice payments), riders and assignments (flex grid stuff), and invoice line item details with quantities, descriptions, and booking info. Also sent out a number of text messages to some of the adilas guys. Touching base and light follow-ups.