Cory and others joined the morning meeting. Since no one else had anything pressing, I helped Cory with answering a survey from one of our 3rd party solutions. I did emails, follow-ups, and got ready for a scrum standup meeting. I took a few notes. It was good to see the guys coordinating and trying to move the ball forward. One of the challenges is timing and getting schedules to match-up between the developers. Making progress.

Chuck and I did a small work session. He showed me some progress on that pages that he is working on. We spent some time going over his to do list on his project. He is doing great, getting things prepped and then asking for help where he needs it. Seems to be a good flow. Towards the end, he and got did some training on images, loops, logic, and using advanced datasets (arrays of structures). He was working on the view parts page inside the system to make it into a tabular layout vs just scrolling from top to bottom on a single page.

Wayne joined and was asking if he can switch the dev testing branch to another branch that is needed for testing servers. We said yes, and thanked him for asking. Cory and John were going over updates on John's projects. He is going to be more focused on the tax stuff and year end payroll pieces, the month of December. He will most likely be sitting out for the next sprint. He and Cory were coordinating and getting things planned out for other projects as well. John gave us a small demo on his progress on the discount engine and what else is needed on that project.

Working on user stories for the AWH project. Cory started out the session with some light training that she had found online. We are trying to think more about the "why" and the "who" is using these new changes and features and really putting those pieces into our stories (smaller pieces of the bigger projects). We did some more review on scrum and agile training stuff and then got into a good work session. We are currently going from bigger stories into sliced stories and then into acceptance criteria for the smaller sliced pieces. It is a process and takes a lot of refinement along the way. Great little work session.

We started out trying to put things into elements of time, but it was too disorganized at first. We ended up using some Microsoft Word docs and then then moving pieces around there first. It was much more open work area. Then once we got things nailed down better, we started transferring the data over to elements of time. That worked much better. Anyways, a good little work session and we felt pretty good about it.

Merged and pushed up some new code that Bryan was working on for one of his older custom projects.

Custom data upload for Euflora 3D. They added a couple of new parent attributes (daily limit and ratios). I spent time combing and cleaning up data. I did three separate data uploads. One for short item or normal part descriptions. One for long web descriptions. And another for all of the parent attributes (7 custom attributes per item). Sent the client an email update.

Started out with Steve and I chatting for a bit. Then Steve and Sean started talking about some sales, leads, and networking strategy. Things are going good in that avenue. They were also talking about growing organically and what that looks like. We ended up talking about MVP for sales and growth. Sometimes we have our aim set so high, we can never reach the mark. MVP can stand for a lot of different things. Most commonly it is most valuable player (sports), minimal viable product (business), etc. We had a business consultant that was explaining that MVP could also be things like minimal viable person, minimal viable plan, minimal viable player, or whatever. Basically, having enough of something to get the job done. Sufficient for our needs.

Along those lines, we were being silly, but if you could swap out what the "P" stands for in MVP, what if you just changed it completely. For example: MVG or minimal viable growth. Talking about some options and possibilities along those lines. For me, I can see the small things and try to grab what I see. If things are out there too far, I tend to lose focus.

We had a sprint standup meeting. I took a few notes in the main adilas system, on the project. Alan and Wayne were talking about progress and communications. Also, there was some talk about the need for testing and how it gets accumulated over time. Working towards a good continual integration process. Some of the guys are questioning the need for unit testing. They are so used to doing their own, just in time testing, that taking the time to mock-up and fake data and write tests is challenging their minds. I think that most of them are starting to see the value in it and helping them realize that there are other benefits vs just speed on a project.

Helping John with setting up an enterprise system (multiple linked corporations) on his local environment. After that, Cory wanted me to look into adding some buttons and small layout changes on a thing called the short and sweet cart. This is a custom shopping cart that was created by Spencer, an outside independent developer. We made a few tweaks and pushed up the files.

Work session between Shannon and I going over more changes and content for the adilas core concepts and the intro to world building document that we are working on. Fun work and brainstorming session. We talked more about the MVP model and options to getting things to the "sufficient" level. See an earlier entry from today to see some other comments on MVP models. See the attached document for our progress from today.

Work and planning session with Cory and I, going over a manufacturing project. It contains elements for multiple pieces of the system. We were dealing with settings for recipe/builds, elements of time (calendar events and planning), inventory planning, inventory thresholds (mins, maxes, lead times), forecasting, scheduling, and other pieces. We have some existing stuff, but it will need to be rooted out and new code added in over the top of the existing pieces. We can do it, what we are trying to do, but it will need more meat and power to be fully optimized. Cory and I spent time drawing, recording notes, planning, running through scenarios, and pitching ideas back and forth. Good work session.

Brandon has a word document on his local computer that we were working on. Still in somewhat of a scratch mode (planning and brainstorming).

Going over the year end payroll project and needs. We did some light review, listed out some tasks, and even went into files and looked around. Lots of review and good little work session. John took some notes and I did as well. Towards the end of the session, John and I chatted a little bit about the new scrum and agile development stuff. We talked about the need of a middle level programmer (someone who understands both frontend and backend code and likes to play in that role). We also talked about lessons learned thus far and where we think things are going. We also want to get Dustin some help so that he can get some of his big projects finished up and out the door (deployed onto live servers and being used).

Recording notes from the past couple of days. Also did some emails and general catch-up stuff. Lots of stuff is going on.

Fixing the recipe/build link builder. This is a new part of the inventory and component planning stuff. I also built a small clean-up page to help update some of the older recipe/build links. Ran some manual updates on a couple of servers. Emails back and forth with Chuck on some different projects.

Having some audio issues. I ended up rebooting my machine, jumping out of the meeting and then rejoining. Worked with Chuck to help with his local setup for a multiple corporation (multi-corp) testing environment. Cory and Steve were going over logic for gift cards. We have a client that wants to use some gift cards and was wondering how that gets booked (financials). We would really like to automate the process, but for now, the users would have to keep track of things manually. We can't wait to jump back on that project. We will use special accounts and will be running things clear out to the balance sheet and tracking the correct liability. We got a few other small updates from other developers on projects.

We had a standup meeting for the scrum sprint. I took some notes and added them to the correct element of time. Bryan and Alan were talking back and forth and making some plans. Towards the end, Cory was coordinating different people and parties and what not. The two stars for the day were Alan and Cory. Good stuff going on.

Meeting between Cory and I going over different projects. We jumped on a small bug fix for updating and setting the max or new starting invoice number. This feature has existed for years, it just needed a small update. What happens is, you take the last known invoice, you get the invoice number and then you use a special page to increase the last invoice number or the auto increment number. For example: Say you were creating invoices and had invoice # 150 (done and in front of you). That would be the last old or current auto increment number. If you wanted to take invoice # 150 and change it to 1000, you would have to use this special auto increment tool to flip the old invoice to the new number. Then, once in place, all new invoices would add one to the new max or last auto increment number. In our example, the next invoice number would be 1001, then 1002, etc. This feature is handy if you need to get to a certain number, migrating between systems or you want to make it look like your invoice numbers are set higher than naturally counting from 1 (starting number). It allows you to virtually set the new starting number. Then, once in place, the new invoice numbers start from there and work up.

Anyways, I had to do some google research and added in a small fix. We pushed it up live and Cory did some testing. We then did some drawings and talking about a custom API socket project and mapped out some flow and options. Cory will take some of the questions back to the client and we'll go from there.

Backlog refinement meeting with Cory and Alan. Alan was reporting on the current sprint and some take aways (lessons learned or observed) that he is getting from working with the other developers. As a side note, the good connections and progress seems to be tied to, he and the other developers, are somewhat having their own mini standup meetings between themselves. This extra communication really seems to be helping, when it happens. If not, progress seems to be slowed (lack of communication and direction).

One of our challenges is figuring out bottlenecks and who is going to do what. We talked about unit testing and virtually drawing lines for when we need it (unit testing) and when we don't. Not all projects are the same level or same importance. It really does depend on the page and the functions per page. We have to evaluate the need and then decide how deep we want and need to go, per page or per function.

We spent some time talking about error handling and plans for that. We have a current plan in place, however, some of the developers are proposing changes, updates, and being able to catch and log errors higher up on the page or at an application type level. After that, there was some talks on continuing education and getting some training on new techniques and what not.

Cory and I were showing Alan some of the next user stories for the next sprint and getting his feedback. Alan recommended that we refactor some existing code and reuse things where possible. We got into talking about the enterprise part category project and even having two different sprint teams going at the same time. Alan and I would take care of the recipe/build stuff (production and manufacturing) and we would have Eric and Wayne lead out the enterprise stuff for part categories. Alan and I also had some discussions on how we would like to deal with part category images (part of the bigger enterprise part category project). We talked about adding in a new field that would have a full path to the category photos, so that we could share photos between corporations as needed. The current system only allows for each corporation to have their own photos. The enterprise system would allow for sharing a single category photo as needed. That saves storage space and allows for things to be more standardized and/or data normalization stuff.

While Alan and I work on the one sprint, we would have the other guys work on the models, unit testing, and wire-up jobs for the other sprint. We booked some time to work on the side sprint between Alan and I. That is a huge part of the puzzle. If I don't book the time, it will just get claimed (other developers needing help or other meetings) and it doesn't happen. Anyways, good stuff and a good meeting. Nice breakthroughs.

Recording notes from earlier meetings. Looking over bills and accounts. On the phone with Steve going over developers, projects, updates, plans, and funding. Back to recording more notes and clean-up for the day. All part of the process.

Online Adobe ColdFusion Seminar and Conference - Summit 2021 - 2-Day Conference

I took 12 pages of notes - handwritten - I scanned them into this entry. See attached. I also got some notes from Bryan Dayton (Word Doc), another adilas developer who participated in the conference.

I attended virtually both days. My favorite speaker was the day 1, keynote speaker, Ashley Willis, on developer relationships. Tons of great information on API's, community, and influencing products, and creating content. I really enjoyed this presentation. See my attached notes.

I don't have time to rehash all of my notes, but it was great to get in there, hear, watch, learn, participate through chat, and see what others are doing and what tools are available. I attended talks and presentations on static site generators (SSG's), object oriented programming and strategies, security, database classes, queues and microservices, CSS courses, logging and visualizing, blogging tools, modern security approaches, PDF document tools, JavaScript frameworks, using underlying Java code, and a discussion on the future of ColdFusion.

Good conference. See my notes for more info and details. Looking forward to next year!

Busy morning. All of the meetings kind of just blended together. Here is what I have from my quick chicken scratches on some post-it notes.

- Working with John on some bugs dealing with paths, custom CSS and custom JavaScript for adilas pages. We were looking into other bugs that had been submitted through email and tech support. Wayne and John had released a big change by switching from Application.cfm to Application.cfc. It may sound small, but in ColdFusion, that switch affects every page in the entire application. The old was an automatic include with linear (top to bottom) code that was run on every page. The new way, through cfc's or components, everything has virtual triggers and it is setup to allow a more object oriented approach through methods, functions, and global variables and triggers. Anyways, they launched those changes and most everything was going well. It was just the little side or one-off deals that were having issues.

- Wayne jumped on, you could tell that he had been up for hours (different time zone, he lives in Europe - Portugal). Anyways, we went over a few things but you could tell that it had been a super long day.

- We did a standup meeting, and I took a bunch of other notes, on that project. See elements of time # 1865 inside of adilas for details.

- We got into a semi heated discussion on standards and using the adilas docs (public place for snippets, adilas sign-off tips, and style guide info). John was really pushing hard to get people to buy into that. It exists, and we need to use it more, but some of the developers don't like to take the time and would rather just keep asking people or doing their own stuff. There is a need for better compliance, but it may need to be done differently vs trying to force parties to play as we want.

- We did some developer training and showed them how to get to the adilas docs and lightly browsed around so that they could see what was there.

- Cory and Alan and I did a review of the AWH project and I took a ton of new notes. We were heading in a direction, and the new information will require us to rethink some things and even put prep steps prior to where we were heading originally. Small little twist.

- At the end our meeting (just Cory, Alan, and I), they asked for a small review from the ColdFusion Summit Conference. I gave them a recap of the meeting that was the keynote startup meeting from day 1 of the conference. I haven't done it yet, but I will record my notes on that summit conference entry. I really enjoyed that first talk about developer relationships.

- After Alan left, just Cory and I chatted about other projects. Cory has a need to be able to copy certain vendors between corporations. We have been working on an enterprise level vendor tool. That works great, but this little tool is more flexible and doesn't require the other enterprise to transactional corporation setup process. I told Cory that I could have a small tool done in a couple of hours, if I tweaked and modified an existing page. We will build that out, and keep it as a backend tool for now (not customer facing, only to be used by adilas backend persons).

- The last note was dealing with a need to be able to copy expense types, deposit types, and balance sheet types (chart of accounts) between corporation. We haven't done that yet, and it will require some mapping, but that need is coming as well. The deeper you go, the more the need for cross corp tools and enterprise level functionality becomes apparent and very needed. If I were to predict, I would say that the terms enterprise and transactional corps (or corporations) will be used and developed deeper as we go along. The needs are already there, they just haven't been funded and fully voiced yet. We'll have to see how it all plays out.

This got skipped due to other meetings flowing over their allotted timeslots.

Shannon ended up texting me later on, but she forgot about the appointment. Cory and I ended up using the time to talk and chat about other projects and needs.

I took a bunch of notes for both the sprint review and sprint retrospective meeting. See elements of time # 1865 inside of adilas for more details.  We had a small show and tell session followed by a good discussion on lessons learned and direction to head. Once again, see the other notes for more information.

Didn't happen. The other meetings went too long.

Working on building a new vendor copy tool from one corporation to another. I already had a bulk copy tool for vendors, between corps, but I needed one where I could pick and choose (checkboxes) and then just copy certain or selected vendors between the corporations. Working on the new tool for Cory (adilas backend tool).

Going through tons and tons of emails.

Paying bills, emails, and doing an update for the Bear 100 runner portal. I got an email that the public Bear 100 runner portal was showing an error. I went in and looked, and it was dealing with some of the major application changes that had happened over the past week. I had to go in and pull up some old code and refashion a new include file to help with some missing global variables. Got it all done and pushed up new files to the web. Sent an email to the race director to let him know about the changes.

Steve and Sean were talking strategies and talking about some client needs. We have a number of clients that have a ridiculous number of inventory items. They need help either importing those data pieces or being able to provide us with lists and we then help them get them entered into the system. Shari O. popped in and had a few questions for myself, John, and Steve. She was checking on some of the year end forms, state payroll tax calculations, and other small items. After she was done, a number of other developers popped in and did a quick check-in and small update. We finished before 10 am and all of us jumped off the meeting to work on other projects. Lots of stuff going on.

Recording notes from last week. Also went through my notes from the Adobe ColdFusion Summit Conference 2021 - from last week. Scanned in my notes and uploaded some other notes from Bryan that he sent to me for the conference. Here is a link to those notes.

Sprint planning meeting with Alan, Wayne, Eric, Bryan, Chuck, and I. Alan had setup a new Jira board to run the sprint through. This was a request from the guys. We were trying to use elements of time, but they guys wanted a more visual layout. Because time is of the essence, that is ok for now. Somewhat of a bitter/sweet thing for me. Eventually, we want to get all of our projects and project management pieces fully into adilas. That is my goal, at least.

Anyways, we started out and Alan pretty much ran the whole meeting. He was introducing the next sprint with an epic, issues underneath the epic, and then small notes and comments. He also gave a light demo of the what is the what in the enterprise part category project (current/next sprint). He was giving out assignments and talking with the guys. They got into some UML charts and graphics. UML stands for universal mock-up language. Kinda like a flowchart for data and objects. They were going over class diagrams, extensions, inheritances stuff, naming conventions, getters, setters, and trying to shorten things up.

They spent time going over plans for the object models, methods, public and private functions, etc. Some of the guys were requesting some training on the UML stuff and other topics. Open conversation and some of the guys were chiming in and asking questions and making suggestions. Felt pretty good.

One of the things that we are trying to do is - learning as we go and taking the time to inspect and adapt as needed.

Lots of new variables today. They added in Jira, UML, plus all of the agile and scrum stuff. It seemed like a lot at first, I think that it got better as we went along. Chuck volunteered to help with some code review. I was also happy to see the guys pulling from the past two sprints and learning from what we just did. That is awesome.

We spent some time assigning and talking about story points (estimations on time and complexity) for the user stories. As that progresses, we took a small detour and talked about where it (the enterprise part category project) is going in the near future (say the next sprint or some future sprint). We got deep into some image stuff and ended up telling the guys that we will push that off until the next sprint, so that we don't complicate this too much. Lots of talk about images, where to store them, current functionality, and future plans. This was one of our only major side tracks for this meeting. Pretty good.

Towards the end, Alan had the guys go in and play with the Jira board, move things around, make assignments, claim things, etc. Eric really wants us to focus on the standup meetings and keep them tighter (more on task or on target vs all over the place).

Once everybody else left the meeting, just Alan and I chatted about a few things. Light review and making some plans. We also talked about possibly switching between GoToMeeting (currently using this online meeting environment) to Zoom and paying for a pro license. Anyways, we did some comparing and make look into some options. Not to bash GoToMeeting, but it does cost more and doesn't have some of the same features. We started using GoToMeeting in 2013. No decisions have been made yet, but we'll see.

Emails, tech support, and recording notes from earlier today. Felt like a busy day. I will say this, I'm very grateful for others who are helping. The size of this whole project (building and supporting adilas) would completely crush just a couple of key players. You really have to have a team to handle this.

Danny, Sean, and Steve were talking sales strategy stuff when I joined. We got a few light updates from some of the guys. We then had a standup meeting for the scrum team. They are just starting their third sprint. They seemed in good spirits and knew where they were going. Alan was leading them. Light bit bucket and git training at the end of the normal standup.

Small side note, they all finished their meeting, made some connections and then hurried off to their other meetings with each other. All of the sudden, it was just me on the meeting, everybody else had left and was starting to go work on their projects. Pretty cool. It kinda shocked me. So quiet.

Worked on the copy selected vendors between corporations tool for Cory. She wanted a tool to pull one or more vendors from a corp to another corp by selecting it and saying copy (virtually). Finished up the page, merged it into master and pushed it up to all servers. Sent Cory an email with instructions.

Working with Shannon on some verbage and copy for the world building piece inside of the adilas core concepts and origins section. It's not finished yet, but here are some things that we are working on: See attached for the other parts of the story.

So, what is world building? And how does it relate to business software? We would like to answer this in three different ways. First, we would like to answer the question. Next, we would like to explain it a little bit further and give some examples. Lastly, we will try to explain how it has influenced our decisions and direction as a company.

1 - Answering the questions, what is world building and how does it relate to business software?

World building is the process of creating a unique environment for each business entity.

Often software tends to be built for one industry specifically. If you only have one industry, the whole package is built to support that business model, or world, and there is no need to diversify it. But what if the software package allowed you to diversify it to all kinds of business models and verticals. This allows you to customize the environment to meet your needs.

As you setup and create this unique environment you end up answering a number of questions. Some of these questions could be where are you located at? Does your business deal with time, products, services? Who are your customers? What do you call them? Members, clients, patients, students, etc. Basically, you are determining what you want your world to be like and what you want it to do. The Adilas system is flexible and able to handle all kind of choices and decisions. As you mix these together this is what creates the customized landing area for your data. As soon as you can start seeing that every single business is technically a different world - it starts making more sense.

2 - Explaining world building further and giving some analogies.

The author who introduced us to the concept of "World Building" was Brandon Mull, a New York Times bestselling author. He was giving a presentation for young writers and artists at a university and one of the co-founders and his children happened to attend the seminar. In his presentation on world building, he stressed 5 key components. They are characters, relationships, trouble, decisions, and consequences.

To further explain this concept here is a small analogy, or example, he gave as part of his presentation. A good science fiction author may come up with the concept of a flying car. But a really good science fiction author thinks at the level of world building. What are the causes and effects that occur with having a flying car? What is the technology that allows that? What are the traffic laws? What things keep it in check? What happens if there is a traffic jam? A wreck? How are they powered? How are they stored? How are they fixed? What are their speeds, capabilities? Are they armed? Etc., etc., etc.

Think of your favorite movie or book. What different things make up the environment that makes it unique and special? Some of the best books and movies are those that are able to create an environment that is so rich it almost feels like a real place you can be transported to and participate in.

These same concepts apply to the Adilas application. Imagine one of the richest environments you will ever use, ready to run standard out of the box, or customize it to meet your business needs. Think of custom naming conventions, toggle options on and off, settings, permissions, tons of tools and business functions at your disposal. The ability of the Adilas system to adapt to any business world is incredible! That is what Adilas has been created for.

To start your mind thinking along the lines of world building, here is a little exercise. Consider answering some of the following questions whether you are creating a world for storytelling, or creating a world for your business entity:

General World Building Questions

- Where is your world located?

- What special features does your world have?

- What does your world have an abundance of?

- What does it have a lack of?

- Who is on your world? Different civilizations? Friends? Enemies?

- How diversified are the civilizations, areas, or locations?

- What are the reasons they are separated or diversified?

- Who are the characters and the groups?

- How will they interact with each other?

- What kind of things are they trying to overcome or accomplish?

Okay, now let's transition into business world building questions:

- What do you call your business?

- What type of business do you have?

- Where is your business located?

- What is your company size? Mom and pop, small, medium, large, enterprise, custom?

- What do you call the people who work for you and work with you? Salesperson, staff, associate, team member, or whatever you may call them.

- Are you doing things alone or as part of a team, department, etc.?

- How many different locations do you have? What do you call those? Locations, stores, clinics, departments, jobs, facilities, or other?

- Who are the people that buy your services or products? Clients, customers, members, patients, students, etc.

- Do you sell labor, time, services, subscriptions, perishables, non-perishables, little items, big items, bulk items, serialized items, or custom?

- How do you distribute what you are selling? In-person, online, call-in, internal manufacturing, wholesale, delivery, etc.

- What are your pain points or challenges?

- Do you have certain processes or a special flow in your business world?

- Do you already have certain pieces in place and need another software to fill in the gaps? Do you need the whole package? Are you required to use certain software or applications?

- Do you have state, government, or industry requirements?

- Do you have paperwork, documents, forms, scans, contracts, or other files to capture and record?

- Thinking of data and reporting needs. What do you want? What do you need? What key data points are you interested in?

- What are some of your goals? Financial, physical, personal, etc.

Still working on content below this, but having fun... :)

Met up with Alan and we went over the outline and overview for the AWH project (production, recipe/builds, elements of time, reserving items, etc.). Good overview and we made a light plan. I will be finishing up some PO line item rounding stuff and Alan will be taking all of the existing notes, brainstorming, client video, requests, and requirements and helping to put them into a plan. Lots of prep work has been done, but it still needs to be put together.

Eric called and had a few questions about things on his local development environment. We got him pointed in the right direction. I also did some emails and recorded notes from earlier today. I'm now ready to jump back into the PO line item rounding project. Busy day today. Lots of bouncing around.

Spent the rest of the day working on the PO line item rounding project. Working on the JavaScript for keeping track of running and rolling extended costs in the recipe/build page for internal build PO's.

Wayne and I met up to go over some questions and get a general update on some of the new stuff that is going on. He had a question about some dynamic checkboxes and pulling in the dynamic data choices on the action page. He then showed me some of what he is doing for custom public variables inside of the master Application.cfc methods and functions. A bit of a show and tell session. In a way, he is building a number of smaller internal microservices and making everything more modular.

He also showed me what he is planning for the error messages, error handling, and validation routines. Currently, the pages rely on a number of sub dependencies. He is trying to relieve that dependency in order to get rid of certain include files. This helps him be able to test local pages and not have things fail based on the outside dependencies. The goal is to test the main logic of the page vs all of the other pieces. Also, some of the other dependent pieces, have a hard abort attached to them, if there is an error. If that abort happens, it also aborts his unit and page level tests. Anyways, going over some of the new changes.

The other guys joined in and did their sprint standup meeting. I took some other notes on the main element of time for the project, inside of adilas. There was some good dialog after the meeting on some new layouts and designs that Chuck was working on. It is fun to see the guys doing so well at coordinating between themselves. I really like that part of the puzzle.

Chuck and I met up and went over some projects and sales ideas. He reported on some of what he is doing and where things are going with his current projects and some others that are still being kicked around. We talked about the Bear 100 site and helping to promote our services to other races and events. He is going to bring this up this Friday in the sales meeting. Trying to push things forward.

John and I looked at some payroll and yearend stuff. We booked some time going forward so that we have time each week for the next few weeks to work on more forms, taxes, payroll withholdings, and yearend stuff. He is doing some discount engine stuff and server maintenance tasks as well. Not a huge report, but making progress.

Meeting with Alan on the AWH project. We had our own mini standup meeting and then I showed him what I was working on the PO line item rounding stuff. I was using Alan as a virtual sounding board and we went through a number of good scenarios. His plan is to review a bunch of documents, videos, and notes from elements of time to get a plan together.

Checked my email and got sucked in to over an hour of answering emails and doing some internal tech support stuff. Sometimes, that, email, is a virtual black hole or time sink. Anyways, that is where my afternoon went. On a positive side, I saw some great interactions and coordinating between Sean and Marisa. They were doing a great job (following the email chains) and they had some great info that was being passed back and forth. That made me happy.

I also did some recording of notes and trying to stay caught up on normal day to day tasks.

Steve and John were talking about using Docker images and how that whole thing works and is playing out. As an update, we now have a number of our developers who are running things on a Docker instance for their local environments. Things are coming along there. Steve is going to be meeting with the server guys tomorrow to talk options and strategy. A client will be joining them.

Sean had received a bug report through tech support. I started looking into it. Wayne and Alan then used the meeting and were talking about the ability to refresh session, application, and client object models - as needed. Those two are able to communicate on a higher level than most of the others on the team. The others may be able to follow along, but both Alan and Wayne are batting ideas back and forth and talking on similar wavelengths.

The guys had their standup meeting. I took some other notes on the actual project. One big thing that I got out of it today was the concept of refactoring and even refactoring and adjusting the plan. Refactoring simply means, taking what exists and modifying it so that it is able to be used or fits other scenarios. Very interesting.

After the meeting, Wayne and I looked into some automated tasks and checking the scheduling of those automated tasks. We popped in to two different servers and made a few minor tweaks.

Next, John and I went over some payroll info. Mostly getting his local environment setup and ready to go so that he could build and test with real data. Part way through, I got a call from a neighbor who needed some help. I was able to help them over the phone. John and I finished up and I started working with Shannon.

This timeslot got eaten up by other pressing matters. Wayne and I did go over some of the pieces on the server side, but no time was spent going deeper into the code. We'll have to pick it up later today. Basically, this appointment or timeslot got merged into the other stuff happening this morning.

Work session with Shannon. We were reviewing some of the verbage and copy for the adilas core concepts documents and coving some origins of how we got introduced to world building. See attached for where we are working. Today we started into the section dealing with how learning about world building has influenced our decisions and direction. Lots of brainstorming today. We'll keep refining it until it fits in with the rest of the story. As I think about it, the concepts of world building are huge in what I do personally and what I'm hoping to help our company do as a whole. It, being introduced to those concepts, was a paradigm shift for me and adilas. Kinda fun to rehash some of that.

Quick meeting with Alan to touch base and move on. Both of us got pulled off of the project yesterday. I was doing emails, internal tech support, and other tasks. Alan got pulled off on a bug fix and doing code sign-off for another developer. Sadly, or not so sadly, that is how it goes. Lots of moving pieces.

Working through my tick list of things to do. Trying to get back to the PO line item rounding stuff. Reviewing code on the reoccurring expenses and the code that schedules those and marks the tasks completed.

Going through older code and bringing it up to current standards. The original pages were created by a different developer back in 2015. Dealing with the reoccurring expenses or scheduled duplicate of expenses functions and code.

Emails, reviewing code for the reoccurring expenses and other small projects.

Steve and Sean were talking about different race events and reaching out to that vertical to show them what we could do for them. They were talking about some of the custom stuff we have done for the Bear 100.

Wayne and John joined us and Steve was asking about some of the big projects that we have in front of us, in order to be able to cluster and push out bigger and more powerful servers or groups of servers (clustering). We did some planning and brainstorming. I was taking some other notes on the side.

Here are some of my notes:

1. Storing files and images locally on the data boxes

- move things to the content server

- there are 12 photo galleries

- logs, watermarks, alternate images

- ecommerce stuff

- csv files, pdf's, and other custom projects

- waivers, signatures, timeshare docs

2. Database stuff to get all of the pieces in the correct engine format - two big tables that need to be changed up

3. Saved or possible stored sessions - being able to mix session across servers

4. Database and datasource project

- Trying to get to the cluster level

- Eventually... 1 server for code (could be clustered), 1 server for database (could be clustered), and a 3rd server for files, content, images, and other media

///////////

After all of that, Alan and the scrum team jumped on and did a quick standup meeting. I took some other notes there as well (project 1865 inside of adilas). Towards the end of the meeting, Alan was helping the guys with some training and on merging code, pull requests, and bit bucket stuff.

Wayne and I went over some new tweaks to the Bear 100 pages and stuff. Working through some small bugs.

Meeting with Cory. John and I jumped in and merged in some new data tables for the year end payroll pages. We did some light testing and pushed them up to all servers. After that, Cory and started talking about projects and updates. We added in a new corporation for the enterprise level stuff for data 20. Checking on the reoccurring expenses and other projects. We also went over some tech specs for setting up a company with some API socket testing credentials and a testing server.

After that meeting, Wayne and I did some light changes to some path variables. He was running server updates and I was doing emails and recording notes from this morning. I also had to call the bank and ask for an increase on the daily limit (cap) for one of our vendors. More emails and such.

Meeting with Cory, Alan, and I. Alan was showing Cory some of the Jira scrum board stuff and going over some of the new flow and what not. Alan wasn't feeling very good, so we decided to all just work on our own projects. Before we ended, Alan said that he was going to do some planning on the AWH manufacturing project, dealing with recipe/builds, yield multipliers, extended cost totals, inventory transfers, etc.

Once Alan left, Cory and I talked briefly about tools to copy multiple items per vendor between systems. We already have some code and tools that do that, we may just need to beef things up and reuse and refactor where needed.

Helping Bryan out with a login issue on his local machine. Merged in some code and push it up to all servers. Emails and then working on the reoccurring expenses code. Trying to bring that section up to speed and in the way that we normally do things. It was developed by a different developer, years ago. Trying to clean things up and make it more stable and standardized. 

Emails and paying bills. Back on the reoccurring expenses code review and project. Phone call with Steve to go over things. We talked servers, team members, finances, and plans. Lots of good stuff going on, yet, there are still some big rough waters ahead. Trying to figure out options and strategies.

Looking over code on the reoccurring expenses code and project. I'm ending up rewriting a bunch of it.

Looking over task management code for reoccurring expense/receipts. Working on a rewrite.

John and I talking and going over a few things. We went over some year end payroll stuff, tax table copying, servers and sessions, and talking about an overview of history and servers.

We then rolled into the standup meeting for the scrum team. Alan was running it and helping to lead out for the guys. They are getting better and better and faster and faster at some of the tasks. That is good and encouraging.

After the standup meeting, Bryan and Cory were talking about projects. They are working on year end save as PDF, multiple 3rd party payment solutions and multiple terminals. Wayne and Cory then chatted about some other updates including database traffic patterns and being proactive on monitoring servers and usage. Some of these companies really pound the databases and push hard on things.

Going over a new plan for building and assigning out multiple EMV chip reading devices for companies. Bryan will be using some existing code and then refactoring things to make his own new pages and features. His current plan is to use this smaller project to practice some of the things that he is learning in the bigger scrum sprints.

Cory, John, and I on a check-in meeting. I started out and gave Cory an update on the reoccurring expenses project and where I am at with that one. I would say that I'm a good 75% done and hoping to make more progress later today. After that, John reported to Cory and was reporting on his projects. He is working on some year-end stuff, payroll, forms, 1099's, W-2's, state withholdings, etc.

John was asking about pro accounts for Zoom and Jira for each of the developers. We told him not now, budget wise. He thinks that it would make things more efficient and productive. Not that we find fault with that, it just gets super expensive.

We ended up talking about who interacts with who and who supports what (dealing with internal products and 3rd party solutions). Cory sent John a list of snow owl data tables that we need on different pages. This is a small side project, if he needs filler projects. We then talked about the value of user feedback and what a resource some of our power users are, to us as a company.

We looked into a small bug on the sort order of a certain report. Cory and I will look deeper on that tomorrow. Cory left and John and I went over the code to help with copying in the federal tax tables and making updates.

Phone call with Chuck to touch base and chat about life, lessons learned, and progression. Working on code for reoccurring expenses and scheduled tasks.

When I joined up, there was a sales meeting going on. There were 8 people on the meeting. I was mostly a fly on the wall, but awesome to listen and hear what was going on. Marisa was leading the meeting and had an agenda, notes, follow-ups, etc. Awesome stuff. These were the people on the meeting: Brandon, Marisa, Steve, Audrey, Chuck, Danny, John, and Sean.

At 9:30, the sprint scrum teams joined up and had their daily standup meeting. We had Brandon (me), Bryan, Marisa, Alan, Chuck, Eric, John, Cory, Sean, and Wayne on the second half of the meeting. I took some other meeting notes and recorded them inside of adilas. Towards the end of the meeting, they were going over some light trainings and what not.

Two small meetings with some of the main players within the adilas system. Both sales and developers teams.

The morning meeting went over a bit. After that finished, I was looking into a sorting issue with user-maintained balance sheet items. The value that was expected to be the main sort value was buried a few levels deeper than expected. I couldn't just change it. I have to see how deep it goes and what else it will affect before just flipping it. Alan and Wayne were going over things on the main meeting. Once they were done, I showed Cory what I found on the balance sheet sort and then jumped into helping John verify some numbers for new federal tax tables for 2022. Other small little to do list items.

Emails and then changed the user-maintained balance sheet item sort order criteria. I also showed the actual sort value on two of the balance sheet reports so that users could see how things were sorted. Pushed up files to all servers and let Cory know.

I switched back over to the reoccurring expenses and task scheduling project. Working on code and some testing.

John and I merged in some code and went around to all of the servers and ran some database updates to help with new federal and state tax withholdings for tax year 2022. John had prepped some of the files and it was really smooth just to go through and run things on all of the data servers. Easy meeting and small work session. We also looked at the calendar for next week. We've got a number of hours planned for next week.

A couple of guys were in and touching base. We all chatted about Christmas and plans for this next week. I had a ton of emails that I needed to roll through. The other guys joined in and did their standup meeting. I recorded meeting notes. All of the guys chimed in and touched base. Seems like things are going pretty smooth.

After the standup meeting, Wayne and I went over some global variables and how best to handle them. The other guys were coordinating and splitting off and meeting with each other. Good stuff.

Cory and Steve touching base on funding and projects. It got into a discussion between Steve and I on our current model and defining things more tightly. Basically, making some of the verbal discussions more official and permanent. This will help all parties involved. Cory and I will work on a plan and get it back to Steve for review. After that, Cory was going over questions and projects that she had on her list.

We really want to get the sales tax aggregate project launched and merged into master. Currently, it is somewhat in a stalemate on a separate branch right now. Cory texted Eric and he joined the meeting for a bit. Small conversations about some plans. The main holdup right now is how to deploy the new code on all servers and also on the developer testing environments? The new code requires some higher database level permissions and access grants. This gets into a conflict between automation and security. We don't want a super enabled database user on the system but we still need to get some things done.

Merged in some new labels for Danny, Cory, and a client. After that, we briefly talked with Steve and Cory about the gift cards and special accounts stuff. We are running into some bottlenecks and how to get around those pieces. Some deals with talent, code, and permissions.

John showed Steve some of the Jira boards and then talking about some of the current sprints and using/allocating the correct resources. As a side note, we are getting pressure from some of our 3rd party solutions to do upgrades and required maintenance. John was also expressing his opinions on some current processes and executive decisions. We talked a lot about extra costs and budgeting.

Wayne and John are really wanting us to move away from Adobe ColdFusion and Hostek (as the hosting company) and move towards Lucee (opensource ColdFusion engine) and AWS for hosting. That is still just talk, but on the radar. Just talking numbers, savings, and possibilities. Eventually it comes down to decisions and then communications to keep all of us on the same page.

We actually fixed this last week, so we just kept the other meetings rolling in its place.

Cory, Alan, and I on a meeting to talk about upcoming projects and make some plans. Cory and Alan were going over some numbers and projects. The first two sprints were very heavy and cost a ton. We knew that we needed to do some training, but it came in pretty expensive. We still have to hold hands with a lot of the developers. They need help with training, help, guidance, and experience. We are gaining on their comprehension and cooperation, but it is still a heavy lift. We talked about the value of teaching them the vision vs just teaching them the skills.

We talked about current progress, momentum, and time and energy costs for transitioning from project to project. That lead into some talks about trying to help standardize the local development environments and working through issues to help that process out. There is a balance between paying projects (client funded) and internal wants and needs (adilas funded).

Next we talked about some bottlenecks in training and how to help the guys with some of their problem solving strategies and skills. Sometimes, when they hit a blockade, they just stop, vs figuring out some other solution. We really need the guys to be able to fake things, mock things up, and even be able to jump out of the sequence(s) and do the next thing. Talking about strategies for problem solving.

I did some quick searching and found some stuff on overcoming a writer's block from a seminar that I attended. Here are some of those notes (element of time 4437 for the full notes).

- Writer's block - something went wrong with the story... how do you fix that...

>> Backtrack to where the disconnect happened

>> Put a plug in... something amazing happens here... keep going - do what you know

>> Push through to the end and you may need to circle back to fix some things - there will still be time, even if everything isn't fully fixed

----------

Next, we switched back to our current sprints. We are getting things done and we want to slow down and really get things fully integrated and tested before blasting forward. We may need to switch gears and do some smaller projects for a little bit. Helping our guys take a break and hit the pause button. Often, there is a huge value in having a buddy along to help get things finished.

We really want to keep pushing things up so that our users can start playing with it and using the new features. Another topic that came up was dealing with 3rd party solutions and their upgrade requirements and maintenance. Sometimes we just add in the 3rd party solutions and go forward. There isn't really a huge plan as far as future maintenance and required upgrades. Most of those things haven't been fully negotiated at this time. We will try better in the future. We'll try to pick up what we can and may have to do some of that our own, to keep things compatible.

Our last topic for the meeting was routing things and future projects through Cory as the coordinator. As part of that, Cory, Alan, and I are planning on our own little mini standup meeting to help improve daily communications.

Recording notes from earlier meetings today. After that, I switched over and worked more on the reoccurring scheduled tasks for reoccurring expenses. Lots of rewriting and testing the new code.

Emails, light research, and listening in on the morning meeting. Steve and Dustin were going over some new requirements and changes from Metrc bulletins and announcements (state requirements). The other guys joined for the daily standup meeting. They are getting close to wrapping things up for the enterprise units of measure and enterprise part category projects. They should be done with the current sprint by tomorrow. Just light clean-up left.

Wayne, John, Steve, Cory, and I talking about servers and such. Wayne was showing us some potential time and CPU processor savings if we change the way we query for text-based values. In SQL (database language - structured query language), we use a lot of what are called "Like" statements. This allows us to search for partial matches and includes a number of wildcards to help the search results be more open. Anyways, Wayne was showing us that if we change some of our code and do full text indexing on certain fields, it may be much, much faster to get the same search results. We chatted about that and made a plan to experiment with it.

Some of our biggest tables that have flexible searching are customers, parts (general inventory items), and sub inventory tables. This includes customer look-ups, basic part searches, barcode searches, RFID tag searches, and tons of other flex search options. The goal is to speed up some of those flexible searches by 10 times and make things more snappy. As a note, the new searches would use SQL syntax that did the full text index (settings on the tables themselves) and then use SQL commands of match and against commands to line things up.

As a fun side note, Wayne is using Fusion Reactor to find slow pages and pages that get ran a lot. That data will help us find queries that we can tweak and speed up. Good stuff.

We are trying to get Eric's sales tax aggregate project merged and pushed up to master and then deployed on all servers. We will need Wayne's help for that. Some of Eric's code will require some deep backend database scripts. We'll work with Wayne and Eric to get those pieces pushed up.

After Wayne left, Cory and John were talking about the discount engine and trying to get Eric to help with part of the cart logic and wire-up stuff. The subject then switched to John asking and chatting with Steve, Cory, and I about the Jira boards. We plan on using that product for the time being but would really like to keep pushing on elements of time so that we could do even better project management inside of adilas. We have a bunch of the pieces. It just still needs some loving and may require some tweaks and changes. We want to head in that direction. Steve was mentioning a hybrid solution and working to get the adilas project management stuff, even more up to speed, to help us internally. We really want this functionality, but it just takes time and resources.

We talked about some of our developers being pulled in so many different directions. Almost like being pulled in half (just overloaded). Some good conversation here. As we were switching gears, John was asking and lightly pitching options for a small contribution type project, where his time would end up being translated into a form of investment, into the adilas company. We talked about a few options.

Steve really wants to find something that will help us all out and really provide a good positive ROI (return on investment). We want to keep pushing on more and more of the scheduling and project management (planning) type pieces. We see some great potential for good ROI there, in scheduling, appointments, rentals, reservations, and project management and tracking.

Dustin joined us and gave Cory, Steve, and I a report. John was still on the meeting as well. He, John, was helping both Dustin and Steve get some of their mappings and local development environments setup and operating more smoothly. Along those same lines, there are always challenges with server updates and trying to make sure that everything keeps working together.

After the other guys left, just Cory and I were left on the meeting. We looked into a small issue with units of measure and the stored sort values. We are going to make a global change on that section and see if it helps. Cory and I also spent some time talking about other adilas team members. Each one brings a different skill set and flavor to the mix. That is good.

John and I going over payroll flow and processes. John is starting to help me out with this part of the system. He has expressed interest but hasn't really used that section of the system before, other than simple expenses and 1099's. We went through the whole process of payroll, how it ties into users, timecards, overtime, invoices, commissions, salaries, departments, settings, paycheck stubs, financials, expenses, etc. It gets pretty deep. We spent almost an hour going over flow, processes, pages, and other key points. I did a lot of drawing, and we went through setup, using, populating data, and then finally running reports on what was stored in the database. Lots of interwoven pieces.

We ended up looking over some of the year end totals and stuff that we need to work on in the next couple of weeks. Making plans and setting priorities on what pieces need to be done first. John and I also looked at the schedule and calendar to make sure we have some future meetings planed out and timeslots allocated for more year end and payroll type projects and meetings.

Spent some time and recorded notes from earlier today, other meetings and such. Busy times. Going to be flipping over and working on some code stuff next. Ended up cancelling an old hosting account from way back in the days of Morning Start Automotive (MSAI). We used to use an old database for backup and storage, we just don't use it anymore. Kinda sad, but we can't hold on to everything.

After that, more work on the code rewrite for reoccurring expenses and automated scheduled tasks. Pushed up changes to bit bucket (code repo).

Wayne was showing me some new query code changes. He is playing with some full text indexes and new searches that play with match and against vs our older like SQL queries. Wayne has pushed up some code to the developer's testing server so that we can play around with the changes. If all works out ok, we will add the full text indexes and new dynamic searches to customers, parts, and sub inventory. Those sections get hit really hard, every day, multiple times a day, per corporation. We'll start there.

Wayne is also working on some other deeper database admin scripts for the sales tax aggregate project that Eric was working on. We are trying to get things pushed up, while maintaining high security credentials. Before the standup meeting, I asked Wayne to show Alan what was going on and a small demo of the new changes. Making progress.

The guys joined and did a sprint review and a small show and tell for their current sprint. It is super close to being all the way done. You could tell that someone still needs to go through and do the last-minute tweaks and what not to basically sweep the floor and fully deploy it. On the positive side, you can tell that the sprints are going much smoother and faster. Other than the semi buggy demo, it really was looking good. Like I said, just a little bit for polish and finesse and it would be perfect. You could tell that the main pieces were there.

During the sprint review, some of the guys were showing some of their creativity and on the fly code building and custom functionality. That was fun and cool to see. The main look and feel was looking good. They are using tons of object oriented code with models, services, DAO's, classes, sub classes, etc.

Alan was showing and talking about some new integration tests and how he was using real database tests on a dummy database, but it was able to use real services, real DAO's, and real flow without hurting live or production databases. As part of that or those tests, he was also doing some clean-up functions during the testing, if he was making extra records for testing. Basically, things are getting better and better, smoother and smoother, and more real life like testing. This helps us look for real bugs and find them quicker and make things tighter and smoother.

We also talked about some of the next steps along the sprint path. Some of this was dealing with planning, testing, bug fixes, and all the way to full deployment. One of the current missing pieces is going through different scenarios and doing some deeper user level testing. We'll get that figured out and push things forward from there.

Cory and Wayne were still on the meeting and were talking about getting some closure on some support tickets and such. They were talking about upstream network connections and how we deal with service interruptions, that we can't control, sometimes. Wayne was showing some server monitoring things that he is doing. Cory had the idea of selling some sort of service package that used the tools that we are already using, but help the clients have a level of control over what is going on with their dedicated serves or boxes. Sadly, we can't control all of the variables. Some of the things happen upstream from us or before we even get to trying to execute a page or a request. My take on it was, we just need to increase our prices. We do soo much for soo little. We need to get our prices up to match what we do.

Cory would like to know what kind of time is being spent watching and monitoring servers. We don't really have a super clear picture on this right now. It isn't like someone is just sitting there watching the servers. They bounce in and out and look at things if they get alerts, warnings, or a tech support issue comes in. They are doing some monitoring, but it is somewhat passive vs super hyperactive monitoring.

Towards the end of the meeting, Chuck and I did a quick check in on his add/edit parts pages and facelift project. We didn't end up with much time, due to the other conversations that were going on. Small checkup and we cascaded some meeting times into the adilas calendar for next month.

Cory, John, and I on a check-in meeting. John was reporting on what he is working on and all of the little side things that he gets pulled into (servers, year end payroll changes, support issues, bugs, and normal projects). We all feel like that sometimes. Lots of things pulling for our attention and time. "Work with what you've got!"

John left and just Cory and I stayed on the meeting. We were doing some planning and put a meeting in for next week to discuss and plan out some new developer rules and processes (small SOP's - standard operating procedures). The new rules and processes will be for custom adilas coding and internal projects. We are doing fine, we just need to define some of the rules, expectations, and procedures a little bit better. After that, we did some other light calendaring for upcoming projects. Cory has been a huge asset to the whole adilas team. Steve and I have really leaned on her, big time. Thank you Cory!

Sprint retrospective meeting with the crew. I took a bunch of other notes. See elements of time # 1865 inside of adilas. Look for the retrospective notes from 12/29/21. Overall, the guys were pretty happy with this last sprint and how things are flowing and going better for them individually and as a team. The biggest request for upcoming sprints was dealing with a better communication tool like Slack or Discord. Anyways, see the other element of time for more notes. Good meeting.

Merged in some code for a custom black box, out in ecommerce land for a custom gram controller page. Bryan and I also looked into another project for year end - save as a pdf - functionality. Bryan needed some help getting payroll stuff all setup and ready to use. We ended up finding some older data that he could use for testing. After our meeting, I did some emails and light tech support stuff.

Recording and transferring notes from post-it's to digital for the day. Busy day with lots of meetings and some good progress in different areas. It is amazing to see how quickly things change from day to day. Things change inside of adilas and, in general, in this digital world that we play in. Constantly a moving target. That is a challenge sometimes. Anyways, recording notes form earlier today.

Research and doing some estimates for Steve and a client. Ended up pitching ideas on the whole development team for a certain amount per month or on a per project estimate basis. The per project, especially without full details, is more of a risk to us. The other way, we get the whole team involved and can move the ball forward better. Just some thoughts. We have a great team. If we could pay for all or even half of what we do right now, that would be a benefit to us and the software application.

When I joined this morning, due to the holidays (new year) there was a sales meeting going on. There were 8 people on the meeting. Danny was helping to run it and Marisa was taking notes and going over the agenda. They were talking about a bunch of different things. Good stuff.

After that, Steve and I were chatting about some upcoming meetings that he has. We are pitching some estimates to some guys that Steve has been working with. We talked about the advantages and costs of having a fully developed team and what that brings to the table.

Wayne had launched some new code to help with full text indexing and matching partial values (flexible customer searches). It was working great for basic names and values. It was somewhat failing if we used any special characters. We ended up on a Zoom meeting with Wayne, John, Cory, and I. Eventually, we decided to roll back the new changes and stick with the old way. We may take a different direction and see if we can get the special characters to work better. The full text searches were faster, just not quite as flexible (out of the box). We will check it out and keep poking around.

Looking at some code with Bryan for the year end totals and save as PDF option. We made a few changes and then merged and pushed up the code. Shari O. had requested this feature, as she is the one dealing with 1099's and W-2's and other year end totals.

John and I had a good work session on year end forms. We started out the meeting going over some XSS (cross site scripting) stuff and how to protect some of our pages and features from the cross site hacks and such. We removed a portion from one of the database updates that was potentially dangerous. The rest of the meeting was used grabbing PDF forms from the IRS website, flattening them, and prepping them for use in the adilas system. By way of a random note, we got clear to the end and realized that we were dealing with forms for 2022 instead of 2021. The current date is 12/30/21 and we needed to get the 2021 forms up and live prior to Jan 31, 2022. Anyways, we tried to find the 2021 forms but couldn't find them on the IRS website. Almost like they skipped 2021 and jumped right to 2022. Anyways, it threw us for a small loop.

I merged in some code for Danny and reached out to Russell for some help with the snow owl theme (CSS and theme stuff).

Small bug fix on the invoice homepage with the graphs and charts. Some of the page level variables had been moved around and we were missing one of them. It took a little bit to see why it was failing. Pushed up the small change and sent some emails to notify a couple of clients. Other emails and light tech support stuff.

Emails, reporting a session timeout error to Wayne, and doing some database clean-up from old API socket usage and samples. Recording notes from earlier meetings today.