Phone call with Steve to go over some plans. We are trying to find the sweet spot and cater to those who want our product and services. We've been getting some great feedback from some CPA's lately. If they spend the time, they really like what they are seeing. That is awesome. We have a meeting later this week with a new CPA that wants to learn more. Steve has also been pushing harder on stock/units and serialized inventory pieces. Very interesting. If you rewind the clock, we started with stock/units and serialized inventory way back in 2002 and 2003. That is where we started this whole journey.

We are trying to switch gears and pick up the low hanging fruit and focus on where we can help our clients - right now. It's fun to look to the future, but we are a viable product and viable solution right now. We don't have to be everything to everybody. Sufficient for our needs.

From Steve - "What you think about, you bring about!"

Merging and pushing up code for custom labels for Danny.

As of 3/16: 39 hours

3/1/21: Steve already has 12.5 plus hours in as of 2/22. 

Meeting with Suzi and her team from iAnthus. We were checking on progress on a custom report that Steve had built for them. Suzi put it through the paces and everything looked great. We talked about a number of other requests and projects - virtual wish list. Towards the end of the meeting, John from adilas showed some design concepts for some cultivation and industry specific tables and reports that we are looking into building. It is amazing how much people love the flexibility of adilas, but eventually, they want things really pared down and customized to their processes - speed and efficiency - very interesting.

After we got done with the client meeting, we all met back over on the adilas GoToMeeting account. We were going over ideas, processes, and plans. One of the things that we want to keep pitching is hope, a big part of what we offer is potential, vision, and hope. That is part of our marketing plan.

There were four of us on the meeting for the first part. We had Sean, Cory, Steve, and I on the meeting. We were going over different projects, possible API socket solutions (outside parties using the adilas API sockets to build their own apps and products), and other options.

The last hour and half were just Cory and I doing project planning, documentation, and prep work on projects. We were working on a project to help with default part status as a corp-wide setting. Currently, the system assumes that the user will choose if they want a normal parent item or a parent item with subs or children. The new setting will help them control that option via a setting verses choosing every time. We also did some work on ecommerce and show on the web settings for items and parts. We are hoping to do settings on the corporation (world) level, the part/item category level, and the individual item level. Settings already exist on the lowest level. The other two level have existing settings that we are going to add to and make it tighter to help control the flow of things.

4/14/21: 1550

3/2/2021: Dustin will add this in to help with speeding up harvest.

Phone calls with Calvin. We were talking about internal and external API socket calls and best practices for each. After that, I did some emails and checked on some funding options. Looking into a business line of credit or something like that.

Russell and I jumped back into the invoice due date project. It originally started almost 4 years ago, and then we got pulled off of it, due to other fires. We are circling back around and pulling from old code to mix it with the new existing master code.

Steve and I met up over a GoToMeeting session. The main goal was to touch base and chat about options, ideas, and plans. It ended up being almost a two hour meeting. We started out looking at numbers, financials, and trends. We talked about gaps in our management style and how we could work on filling those gaps. Nobody is perfect and we are well aware of some of our shortcomings.

Lots of talk about R&D (research and development) and how we play that game all the time. We are virtually a huge R&D company. We build, we break, we rebuild, we rebreak. Over and over again. One of the accountants that Steve was talking to was saying that we might qualify for some R&D tax credits, due to what we do everyday. Interesting.

We are really happy with what Cory is doing and how much she brings to the table on the project coordination and project management side of things. We'd like to do the same thing (making improvements and progress) in a couple of other directions. Some of the other things that still need some help are servers, deployment, training, and overall communications.

One of the next major topics was servers and the impact of new systems and new software to that environment. It gets deep quickly and the new layers of complexity make it even more of an unknown. We would like to get ahold of those processes and figure out a true cost per server, with all of the extras, monitors, analytics, watchers, logging, reporting, and rollover options. This is still a tough spot and tough subject for us. We want to be involved but it gets super deep and crazy technical extremely fast. That makes it tough.

We were talking about some of our developers and how to get them all transferred over to paying or funded projects. We tend to do a number of big lifts (improving our own product) but that costs us and taxes us as far as cash flow. Our goal is to make it 3/4 funded projects and 1/4 core updates and maintenance. That would be awesome.

We ended up getting into some planning and talking about ways of getting better communication and better levels of responsibility for what is going on and what is happening. It is constantly a moving target. We talked about billing for everything that we do. Currently, we take a bunch of it right on the chin, that works to a certain level, then it just becomes crushing. We are planning on charging $65/hour for deployment, training, and setup. We will stick with $100/hour for development and custom code work. We also talked about picking up other services that we could offer and/or charge for. There are clients standing in line with money, but we have been too busy to pick up those pieces. We need to make a switch there.

Steve and I made a small 3 month plan and will be making and taking steps to put that plan into action. That is awesome. Our current goal is - Work the plan! Shooting for an MVP (minimal viable product) type approach.

On the phone with Calvin going over AJAX and JQuery calls and how we use them. Also got some recent bank statements and sent them over to some funding companies, just shopping around.

John was reporting on servers and tech support stuff. When people report errors or bugs, it sure helps if they give us more info then so and can't do this or that. We need to know who, what server, time of day, what where they trying to do, what the error was, can we replicate it, etc. The more information, the better.

We were also talking about trickle down costs and hidden costs on the servers and what impact certain software and hardware choices and what cause/effect that leaves on us. Trying to get control of some of those pieces.

Steve had some code questions and then we went on to serialized inventory and discussions about mini units (serialized child inventory items).

Chuck and I looked over some of the adilas financials and who we owe and who owes us. Trying to keep the guys in the loop. After that, he took over the screen and did a demo of the progress on the new website. We are estimating that it will cost between $5K and $10K for the new website. It is looking good and they (Danny, Marisa, and Chuck) are making great progress. As a fun side note, Chuck is moving beyond design and mock-ups into real code and mobile responsive design and custom code work. Pretty cool!

More emails and tech support stuff, once Chuck left the meeting.

Working with Danny on starting a new project #1876. This project is dealing with setting new default corp-wide setting values for parent or subs inventory items. We reviewed a Microsoft Word document (project details and requirements) and he started coding on things. I then went on mute for a bit and was working on other projects and recording notes.

Alan popped in and we touched base on a couple of the projects that he is working on and also doing code review and testing on.

At the end, Danny and I touched base and looked over what he had finished during his work session.

Emails and recording notes.

Phone call with Steve to go over servers, communication stuff, and trying to figure out what is going on and how to get a handle on things - on the tech or server level. As a side note, we are not playing on the porch with the puppies any more, we are out trying to run with the big dogs (virtually). There is a difference. We used to have 3 dedicated servers, all manually updated, physical machines, running on metal drives all within one server. We are now looking at 30-40 servers all trying to be synced up and automated. You have multiple servers talking to other servers. It's a different ball game, different rules. Growing pains.

Met up with Bryan to go over some of his code changes. We merged in some code and pushed files up to servers. We also went over some other project needs that are coming down the pipeline. We may end up meeting tomorrow to go deeper into those other projects.

Emails and putting together a list of server questions for Wayne and John. Prep for a meeting for next week.

Guys were checking in. Steve was helping John with some personal balance sheet stuff. It turned into a small training session for those on the meeting. Learning from the master (Steve and doing financials). At 9:30 we had a CPA come on the meeting. This is a guy that Steve knows that is a CPA for one of our clients. He wanted to show us a time clock and payroll tool that he uses and would like to tie-in and integrate with adilas. Basically a tie-in with a 3rd party payroll system. We took a bunch of notes and talked about some possible options. The guys stayed on with him for another hour after I left, I had a 10:00 appointment.

the other subject of major note was dealing with direct job costing, linking out to unitizing costs, and the precision that is needed to really get all of sub costs correctly attributed where they need to go and when they need to go and/or be counted.

Working with Russell and back on the invoice due date project. While we were working, we were talking about all kinds of stuff. These are some notes between Russell and I and also, along a similar vein, notes from me talking with my hiking buddy this morning.

- What do you want to be? or become?

- How big of a company do you want to be?

- The bigger you get, the bigger the competition is as well.

- Make time and learn new code and keep learning

- The choices and consequences of indecision

- You could sell off your shares and then go in a different direction

- Make each industry pay for itself

- Like a crab, growing into a new shell - the privilege of rewriting your stuff due to people using it and wanting more and being willing to help pay for it

- Small little changes are easier than big huge ones

- Having a buddy and someone to bounce things off of

- Build on what you have - keep building towards the dream

////////////////////////

Notes from a small morning hike this morning

- Keep helping our team and team leadership to learn and act accordingly

- By adding a new tool, it can save us from adding a new employee (person costs)

- If you are stressed and fighting things off without being aware of the whole situation, you can actually get in trouble even if you fend off everything that you are fighting - you have to lift your head up and look around

- We are at a crossroads - we could do small and custom, we could move towards small-medium, and/or go big and still play custom

- Being able to say "No" - sometimes that is hard

- Helping to sculpt the story and shape the outcome

- Growth and growing pains - continuing to evolve

- Realizing that there is a burnout ratio and guarding against that and at least being aware of it

Getting Bryan on a new project to help with security and helping to prevent XSS (cross site scripting). He will be adding in a bunch of cfqueryparams into the SQL statements that we have in different pages.

6/18/21: $700

As of 4/26/21: $3072

Two different projects

1. Changing out the raw dynamics in the SQL/database statements. This deals with changing variables from raw values into a thing called cfqueryparams. This project deals with XSS (cross site scripting) and security stuff.

2. Changing the permissions from database checks into session/memory checks - traffic and efficiency stuff.

Meeting with Steve over a GoToMeeting session. We were talking shop and going over budgeting and funding and different things. Here are some of my notes:

- CAS Accounting - Client Accounting Services - aka compliance and oversight - new accounting buzz word and service offerings - Basically, the client run a system and then the CPA's provide oversite and guidance

- Offering full services to our clients - setup, consulting, data imports, training, servers, IT, development, custom, design, etc.

- Steve was talking about how he describes the "inventory stack" - 3D inventory stack - relational model

- On parts and items, parent categories - can cross over between part categories

- Looking back, we used a thing called "usage classes" for stock/units - basically a way of adding flags and tags - being able to search by those things

- 2D vs 3D - searchability 2D (this or that) or searchability 3D (this, this, that, or whatever) - allowing for a deeper search or more a connected story based look at numbers and values.

- We are doing more deployment stuff - working more on that - that is awesome. We used to always push that work out to outside or independent reps and consultants

- Just an idea - having Brandon and Steve be a bug fixer - Monday through Thursday - have Alan cover Fridays

- I'll run some projects and Steve will run other projects

- Setting goals for our guys on what they could generate coming back in - see excel spreadsheet - budgeting both inbound (what we/they bring in) values and outbound (what we pay out) values

- Even though we do custom... what if we switch the focus and just keep building out the main core? This is always been a question. Often, we spend a lot of time that we could be building our own thing out, but instead, we build a one-off for a different client or need.

- We are getting pulled toward big... we like small, medium, and even maybe medium/big but not really big

- Our clients are pulling us - keep following that - we have both static clients and dynamic clients - the static clients take what they are given and run with it - the dynamic clients want changes and push for those pieces and features - straight up, the static clients are easier to manage - the dynamic clients are harder to manage, but they bring an element of life to the game - interesting

- Selling more dedicated servers - start on a shared environment and then moving to dedicated as needed

- Talks about the datasource project (aka World Building) - 100-150 hours still needed - able to scale both up and down - mix and blend code servers and database servers and able to move and load balance things better

- The best team that we have ever had - keep building and pushing

- Linking small building blocks together - nothing super crazy, just mixing small pieces together

- Moving more towards estimates vs bids

- Build in some training - not getting outdated or into the burnout zone

- Prices keep going up - we need to follow suite - passing on the cost increases

- Diminishing rates of return - trying to figure out new things - (in space - an ink pen won't work - will a pencil still work, let's use that)

Project management stuff with Cory. Detailing out the project for show/hide on the web settings. This has three levels deep for the setting. Corp or world level, part category or main group player level, and individual items or part level.

Working with Bryan on securing the shop folders and files (ecommerce pieces) using cfqueryparams and other security changes. We also got into some XML parsing and XML data.

There were a bunch of guys on the meeting this morning. All of them were checking in and what not. As they were talking with Steve, I was doing emails and listening in. Dustin popped in and showed us a new tool that he is working on. It helps to randomize certain numbers for one of the processes that he is working on. The randomization has a editable variation factor that you could plug into the mix. Pretty cool.

Helped Steve out with some email testing and what not.

Going over questions and projects. Lots of talk about normal barcodes (2D and older barcodes) vs QR codes and moving more into that direction. We are running into issues with traditional barcodes due to how much is being crammed into such a small space. Eventually, you are pushing up against limits and restrictions. We want to keep moving toward the next logical step(s). We want to virtually skate to where the puck is going to be (thinking hockey).

We also talked about sizes of corporations and how much they impact others on their servers. They may have started out as smaller entities but they have grown. They, some of our clients, are now starting to impact their neighbors (virtually on the different servers) due to their size and load that they add to the servers. We need to put our foot down, help them make the changes that are needed, and then let them know that this is what their bill will be. We have a few big dogs that are still in the shared environment, they really should be on their own or at least in a semi-dedicated environment.

There was some talks about moving data over to the deep freeze and what those costs would be. It doesn't cost much to put it over there, but it does cost to get it back out. We need to keep that in consideration.

We also talked about a current/future project called the datasource project (world building project - older code name). This would allow for multiple databases per code server. We could then mix and blend as needed on both code servers and database servers as to who services who and how many.

Our core costs have gone up, including the storage of our client's data. Costs seem to be going up across the board. We actually hurt ourselves by trying to stay the same. It's no longer the same thing. We need to adapt.

Multiple people on the meeting. I took a bunch of notes. They are on my local drive. They are called "emerald_fields_meeting.txt". Here are a few quick highlights:

- They are wanting to get into their own data warehousing - they will be mixing data from adilas and other vendors all under one roof for faster reports and analytics

- Everyone is heading into BI - Business Intelligence type levels - quick fast totals, counts, sums, and averages

- Lots of talk about outside 3rd parties and pros and cons of some of those services

- Emerald Fields does an awesome job and has some really tight business process - virtual poster child levels

- Steve was proposing some consultation from one of our adilas developers

- Push and pull type technologies

- Special discounts with limits and automating processes and custom discount engines

- Looking to the future and building new tools and features as needed

- Steve was pitching them some of the new things that are done and/or coming off the press - he's a good salesman and can pitch a vision

5.5 hours for Steve

3/8/21: Steve will add some logic that keeps patients from checking out without an MMR or customers checking out without a valid bday for 21 years.

Little BH- Medical only  Corp Id: 861

3/8/21: Per meeting today.

Spent an hour with Calvin on a demo/review of the web version of the adilas label builder. It is really coming along. Calvin built a fully functional Windows version of the adilas label builder a couple of years ago. We are now getting closer and closer to having a fully functional web version of that same (similar) tool. That is awesome. It's been fun to watch the progression. I wish it happened faster, but it is still super cool to see the progress.

After that, I was doing emails, paying bills, checking on funding options, and talking with Eric about some aggregation options for sales tax totals.

Working on some updates and changes to the shop stuff (ecommerce pages and files) with Bryan. We did a code review and pushed up a bunch of new pages dealing with the cfqueryparams and tightening up security stuff out in ecommerce land.

On the phone with Steve going over plans and touching base.

A few of the guys jumped on this morning. We were talking about building paths and providing such a good overview of where we are heading, that people want it right now (managing expectations and realistic timelines and budgets). Basically, we build a small foot path, let others start using it, and pretty soon they are expecting a fully built out highway with signs, guardrails, shoulders, etc.

As a funny side note, Danny gave the analogy of a small tractor being able to handle a small parcel of land. Then all of the sudden, the land area is increased and the same small tractor is still expected to run the bigger plot of land. We can all see that major upgrades are needed. In software and web ware, it seems to be a little bit more hidden and either clients think that it will still work just the same or we (adilas) think that it should work just the same, when in reality, there are major changes and major demands being placed on servers, pages, database, queries, logic, functions, tools, and other resources. We had some good talks along those lines.

Danny also showed all of the guys on the morning meeting some new "Adi" (adilas the dog or adilas dog images). Adi is the avatar's name. See attached for some of the new images. They, Danny and his team, are planning on using them as part of the new website that we are building.

Weekly server meeting with Cory, Wayne, John, and Brandon. We were only going to go for half and hour, but ended up going for 1.5 hours. Good stuff. See attached for some of the notes. Trying to get things figured out. Great meeting and we all went away with a more clear understanding and seeing where we are headed next. Making progress.

Shannon and I started going over the questionnaire summaries that we had done. We didn't get very far today. We also went over some other questions and just talking about other upcoming changes.

Emails, checking on funding, and general to do list stuff. Recording notes from the past few days. The good old transfer from scribbles on post-it notes to actually typing them into the developer's notebook, as an entry using elements of time.

Code review with Danny for a new corp-wide setting. He was commenting that he liked the project management stuff that Cory and I did for his project. It helped him stay on track and was deep enough to guide him through the process without someone to be there to hold his hand. We will keep trying!

After the meeting and pushing up the code, I went back through and was recording notes from other meetings.

Touching base with some of the guys on their projects. Small code review with Dustin. Pushed up some new changes. Quite a few of the guys had questions for Steve today. They were going over new features and asking questions about accounting. While they were doing that, I was recording notes and such.

Meeting with Chuck, going over his main website project. He showed me some of the new code and mock-ups. Looking good. We talked about custom animations, building templates, headers, and custom CSS stuff. We also talked about WordPress security stuff and doing training.

Emails and recording notes.

Sending out gift cards to our guys and gals.

Cory and I were jumping in and doing some project management on the timeclock project. Trying to prep things for the other developers. We also talked about what it would take to add new special line items and general data 0 server health stuff.

Merged in some code for Bryan. The new code was dealing with server security stuff. Also gave him some direction on where he is headed.

Writing letters and sending out gift cards to our guys and gals. That was kinda fun.

Went over to my dad's house and gave a guy a demo of adilas and what we do and can do. It was fun, we ended up talking quite a bit about potential and how this product could be used in so many instances and scenarios. Good meeting.

Wayne and Steve were on when I jumped on this morning. They were talking about settings and corp-wide settings. We started out with 6 and now we have hundreds of settings. Wayne was pitching some ideas for flagging the settings so that we could pull them in different ways. For example: say a single setting, a group of settings (like ecommerce), or a list of settings (comma delimited list or multiple). Great idea.

Follow up meeting with a client. Here are some of my notes:

- The current custom page that exists, they will leave it somewhat hidden and not connected. That way only certain people have access to the page.

- They would eventually like it to be fully automated and even hidden if possible. This deals with mapping custom sub attributes to certain phases and processes. Fully custom, just for this client. the automation deals with passing phase dates to sub attribute dates - this would require a small mapping to keep apples to apples.

- MVP solution (minimal viable product) - keep it small and tight. This is just for one client, we don't want to make this standard.

- Steve was pitching some other settings and status values for settings. Instead of just having active or inactive settings (use or don't use). He was proposing view only or admin only settings. Basically, pulling in a level of permissions on the settings themselves. That's nothing new, but sometimes as you build, you don't realize that you have to protect and/or figure out the levels when you first build it. Often, the idea is build it and then forget it. However, if the users have to keep going to the settings, you run the risk of someone who shouldn't be changing global or master settings and they switch something which causes problems. Basically, permissions and status levels within the settings. Interesting how everything eventually breaks into sub levels of control. Think of sub permissions.

- We did some light planning on the next phase of the automation process.

- There were some small look and feel requests. Once everything looks and feels good, they (our clients) are comfortable. If anything is off, even small ish, there is a small tension level. Very interesting.

John and I were supposed to be meeting on a different project, but when we joined the meeting, Eric and Wayne were having a great discussion on scheduling and stored procedures. They were talking about options inside of Adobe ColdFusion (server-side scripting) as well as options inside of MySQL (database stuff). Here are some of my other notes, while Steve, John, and I were listening to their conversation. Good stuff:

- Web stuff, client-side stuff, and server-side stuff. We have to mix and blend all of these technologies. Each one does specific things and shines in certain areas and aspects.

- Lots of great back and forth between both Wayne and Eric - they were talking about phases, threads, business flow, standards, etc. How to process big amounts of data in the most efficient ways.

- Pros and cons about database triggers - one of the best ways to use a trigger is to set a flag in a different table that business logic could then use.

- Along with triggers, they were talking about rolling back and using simple last date modified flags and last modified dates. Then you only have to go back and clean-up or alter what has changed. Lots of good discussions here. Eric had some good insight in this area.

- Most database tables (where needed), should have who created it (an id number), what date was it created, who modified it (if anyone), and what date was it last modified on? - This is not a comprehensive history, but it helps to keep track of general flow processes. The other advantage is that you should be able to tell a rough history (the basics) just by looking at one table. We could then build business logic based on those fields and values.

- Base some of the new logic off of the last modified dates and then prompt for action accordingly.

- Cost is speed

- Changing water into ice analogy - Think of water (liquid or new values) changing into ice (solid data and solid numbers) - water, snow, ice - it, things, become more firm and solid as they move along the process.

We started out and did some training on transition invoices and how those work to help book values that are somewhere between a quote and an invoice. Say something that has started but hasn't finished (don't want to claim it as revenue or a tax liability but it may have down payments or other inventory assigned to it). Nice little training session.

Back working on the internal questionnaire summaries. Proofreading and going through the summaries one by one. See attached for our progress. These summaries will end up being some of the basis that we use for our business and vision plan. Good stuff.

Random meetings and working on projects. John and I met up and did some review and planning on a project to select holidays (point and click holiday chooser page) for a payroll and timeclock project. After that, Steve joined us and we were talking about developers, projects, funding, and special skills of certain developers. Basically, how can we use and mix those skills and needs.

Cory and Danny joined the meeting. We were going over some custom labels and pushing them up to the servers.

After Danny left, Cory and I went in and did some research and fixed some paycheck stubs for a client. They had changed some stuff up mid stream and retitled (renamed) certain special fields without worrying about what was already stored in those same fields. The year to date values do simple math and add up whatever was in a certain column. So, it was showing numbers that were off because they changed multiple columns without thinking about past entries and other values that had been added to those same columns over the years. We made the fixes and let the client know.

Here is a more detailed version of what was going on. We allow for 5 special virtual buckets per person to store whatever values they need for payroll and paycheck stubs. For example: say an IRA, dental plan, meal plan, child support, insurance, or whatever. These values could be added to or taken away, before or after taxes (payroll stuff). They get to name the buckets as they see fit and apply any settings that are needed. It is totally up to the users or admin users as to what is used and/or needed. Well, image if you were putting in $200/month into an IRA account (pretend that was in bucket 1 of 5). Then you decided to switch the name of that bucket to Dental and it only had $30/month as its value. The math behind the scenes says - add up bucket 1 and show the year to date total. Basically, bucket 1 had a number of IRA amounts and some dental amounts - all mixed into bucket 1.

To fix it, we had to pull a bunch of data and then reset everything to the correct bucket with the correct name. Not super tough, but kinda a pain and took some time. That is a drawback if making things super dynamic and totally user defined (aka generic). On the up side of things, if you allow the users to only setup what is needed, you don't store extra data and you don't have to think up every possible special account in order to store the data. Instead of having 5 custom buckets to store values in, you would have to have 30-50 buckets with all kinds of hardcoded titles (allowing for all possible solutions - too many). We opted for the user-defined dynamic bucket vs every possible option and then not use even a fraction of them. Choices...

3/12/21: Sent a quote yesterday for 40 hours- could be as many as 50.

Does Adilas integrate with Azure Active Directory (i.e. SSO)?

We need to be able to automate provisioning the users.

Here is some high level info on SSO & SAML. Thanks!

https://azure.microsoft.com/en-us/services/active-directory/sso/#features

https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/what-is-single-sign-on

https://docs.microsoft.com/en-us/azure/active-directory/develop/single-sign-on-saml-protocol

Paying bills and recording notes from earlier in the week.

Checking and updating daylight savings value and timezone offsets for all servers.

Danny and Steve were talking about switching labels over to QR codes and even getting rid of our existing simple barcode stuff (on adilas standard labels). Barcodes work great until the barcode gets too big, then it breaks down because the barcode no longer is scannable (long barcode in a tiny space). QR codes have such a bigger range of characters and number of characters that they can show. That is where we want to head. We can already do that (QR codes), we just need to make more of an effort to make that the new default option.

Wayne presented next and we covered his changes that he will be implementing dealing with corp-wide settings. We currently have them all saved in a couple of corporation level tables. The tables are getting really big and are starting to cause problems due to how big they are (number of columns). The new solution will allow the settings to be held in data type specific tables based on the corporation id number, the setting name, and the setting value. Pretty simple. We will have new settings tables for strings, big strings, integers, decimals, and dates. That should cover most of the corp-wide settings.

Alan joined and Wayne was showing Alan and I some of the new code, objects, functions, and logic to deal with these new settings tables. We went over flow, validation, options, setting groups, global settings, etc. Lots of topics around the new changes and upcoming changes for the corp-wide settings. It is looking good (at least in concept).

We got into optimization strategy stuff. Taking the next logical steps and moving forward. We also talked about static vs dynamic and how static (set number of settings) placeholders actually take up more space than dynamic (only what you need) settings. We will provide defaults for each, but only store what is needed. We will end up using the dummy corporation as the default and then only store settings that are different per corp. Much more efficient on the storage side.

Going over quotes, talking about different developers, pros and cons, and current projects. We keep coming back to breaking things into smaller pieces. It does take more management, but we tend to get a better result. As a side note, we have had some epic fails on our part. Some of that is part of learning as well.

We had some good discussion on just in time (J.I.T.) project management. We are very good at that. We also talked about how agendas and plans can help keep things on track. We talked about some potential meetings with clients and helping with the communication needs. Small meetings with our developers, return and report, accountability for what they are working on. Good stuff.

Planning and progress meetings and presentations. Get our guys and gals used to presenting and showing what they are working on. It will help all parties involved. Think of how we could eventually get into doing pitches - bang, bang, here you go! That would be awesome.

We would like to get ahead of things vs always playing tag and catchup. We tend to get pulled in every possible direction, that makes it hard sometimes. The more we look into it, the deeper the management stack needs to be. We run pretty thin right now. We also talked about other stacks and levels. One of the big things is setting and reaching expectations. This includes tracking and billing for our time. This could be development, consulting, managing, communications, project management, design, etc. The whole stack.

Steve was talking about depth (the space or Z axis - think 3D levels) and how crazy things get with compliance issues, complexity of what is being done and tracked, and other needed factors. Easy and pretty doesn't always solve things. Sometimes you need that depth, layering, and/or spatial elements. As a reminder, according to us, the 3D levels are: X axis = time (horizontal or moving over time), Y axis = money and resources (vertical or going up and down), and the Z axis = space, depth, layering, and stacking. Here is a small help file that talks about some of those pieces.

After that, we started talking about possible tick list items that one of our clients would like to have and/or fund. We will be building a bigger tick list of sorts to share with them. Ideally, we would like to know what their goals, priorities, and expectations would be. We would love to do the work, it would really help us out if we could cover and get paid for our efforts. We've put a lot into this project. We would love some help.

At the end of the meeting, John had some questions for us on how to track credit card stuff and how to track a virtual expense account using adilas. Good little training session and we showed him what we do and what pieces are automated through the usage of the adilas system. Lots of talk about accounting, expense/receipts, expense types, on account payments, accounts payable, splits, etc.

Recording notes and working with Cory on a small corp-wide setting tweak that was needed.

Bryan and I were going over the query param project (security stuff). We then talked about another project called the default show on the web setting project - cascading settings dealing with ecommerce settings and showing things on the web.

Recording notes from past meetings.

Quick merge for Danny and some new custom labels for Highland Vineyard. Steve and I then rolled into some talks about sub inventory and trying to help to speed things up through queries, logic, and database storage values. We would love to rework the po/invoice line items table and the custom dates, custom text, and custom numerics tables. They all could use a few more values to help better connect them. Currently, they are connected, but only through a series of virtual bounces and upward threads. We would like to make it more clear and more easy to get the data back out again. Here is some info that may help with this project: https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4848

After that discussion, we got into other ways of speeding up the cultivation process. A lot of the ways we can speed things up is dealing with how much data we return and/or try to render out to the user, once they have completed a specific step. Eventually we will need to go clear back to the design and mock-up phase and/or stage. Simple drawings for what we want and then go build the dream. Right now, we just keep coding and fixing, coding and fixing. That helps to figure out the process, but it will definitely need a facelift at some time, in order to make it more efficient.

On a meeting with Cory, Steve, and John - dealing with servers. Our plan was to just talk about servers, but Wayne was out of town. So, we chatted and split up to work on projects. I started working on the PO/Invoice line items table and recording sub inventory transactions at the point of sale. We really want to speed up some of the downstream queries that deal with sub inventory. It gets pretty deep, pretty quickly.

Working with Shannon on the internal summaries for the questionnaire. We have already written them, we are just proofreading and making sure that everything reads well. See attached for progress. After working with Shannon, I merged in some code for Dustin and pushed up some files.

1-2 pm - Performance review with Mike and other developers. We met for an hour. We had a couple of the developers report on some of their projects. We had Eric, Bryan, Alan (Cory did it for Alan), and Steve all report on projects that are underway. Good meeting. We will be doing these follow-up and progress meetings every week. Schedule is yet to be determined. See attached for the meeting notes.

2-3:15 pm - Steve, Cory, and I got on a meeting with Calvin, going over the progress on the web version of the adilas label builder. He, Calvin, did a demo for us and we took some notes and asked some questions. We are getting closer and closer. There will be other versions and pushes on this project. It is amazing to see how much it takes to get something going. It then takes even more to keep it going. There are constantly new ideas and new perceived needs and wants.

After Calvin left, Steve, Cory, and I kept talking about other pieces of the puzzle. We see a need for frontend users (simple interface that is already setup and ready to go). We see an increased need for a middle-end or medium level developer/user (slightly more complex interface to setup the simple interface - settings, permissions, custom stuff). The last or other level would be the backend or behind the scenes level. There may be some other levels, but for sure front, middle, and backend users and developers. Very interesting.

We are going to be pitching some more ideas to certain clients - we are pretty good at going from project to project and building and lining things out. We would like to keep going with that and try to capitalize and monetize those ideas and values.

Working with Calvin on the label builder web interface code. We merged in 25 new files to help with the web version of the adilas label builder app. It isn't quite ready for full web use yet, but getting closer. The older adilas label builder app was a Windows only app. This new version will be available over the web for any and all users. We are excited to get it to the next level. This project has cost us a pretty penny but hopefully it will be well received and used by lots of users.

Steve and I were brainstorming on a list of needed projects that we want to get done. We made a list so that we could show Mike a smaller tick list. We have hundreds of projects, we just wanted to put down some simple one liners, on a spreadsheet.

Helping Marissa with some 1099's for her lawn care company. After that, Steve and I did some work on some clean-up logic and talking about the process that was needed. Shari O. popped in and was asking about helping to take care of the adilas family and their personal needs. She is very kind and considerate. The final thing that went on this morning was Shari O. doing some training to help Marissa with transitional invoices and how those work and help in certain scenarios, especially when we get deposits or pre-payment on invoices for work that has not been billed yet.

Chuck joined the meeting and we went over some updates for the new main adilas web site. We had a fun discussion about pitching and virtually selling "wet paint" (aka new products and features that haven't even had time to dry before they are in full use). Pretty common stuff to use non hardened projects and pieces (just in time).

We went over the new website and Chuck gave us a great overview. Lots of custom work, mixed with existing WordPress themes and options. It is looking good. We talked about training and getting a mega menu in place when we can. Chuck showed me a few examples of what a mega menu looks like (imagine a dropdown menu with icons, pictures, and special spacing within the drop-down menu).

I took a bunch of screenshots - see attached. We also talked about server configuration and plans for what pieces will go where and how it will all come together.

We started out with an update from Alan. Cory was joining me on the meeting as well. That way, both of us could get the updates from Alan. He has a number of projects that have been pulling for his attention. He is working on the Metrc API sockets and some new forced changes that they have made. We tend to spend a lot of time dealing with Metrc and their forced changes. He has also been talking with Eric on the aggregated sales tax totals.  We talked about his involvement with Wayne and some of the new settings that Wayne is working on. Alan has been somewhat of a consultant on that project.

He is also working on a big project called the aggregated vendors or vendor catalog project. We went over some options to  help lock vendors on the transactional corporation side of things (permissions and levels). We covered both sides - the enterprise side and transactional side. We need data to be able to go in both directions up and down (push and pull). When updating a vendor, make sure and prompt for other cascading to help save other steps or efforts.

We also briefly talked about some projects that are needed on the transition invoices (between a quote and an invoice - Q.T.I).

Update meeting with John and Cory. John reported on a number of projects that he is working on. Here are some brief notes:

- He is working on the payroll project to setup and select holidays for timecards and clock in/out section.

- Troubleshooting the HTML check printing in the classic skin

- Cultivation and phase dates project dealing with sub attributes

- Servers with Wayne

- Developer's notebook migration project - moving it to another server so that it doesn't effect the main data 0 box

After we got an overview, we ended up talking about other things that he would really like to do. He has an interest in doing more design work. Maybe mixing and blending between backend code, servers, and design work. Full stack mixing!

We went over some questions that he had on the payroll and holiday selection project. Small work session. He also wants to help out with our own setup processes and helping to refine those pages, steps, and processes.

Recording notes and trying to FTP stuff up to the content server. I can get small things to FTP just fine, having issues with big huge things.

Small work and training session with Bryan. We were working with JavaScript and ColdFusion and mixing the two technologies. Lots of conversions from one format to the other so that they could play together. We had a complex problem, so we built some small scratch files to play with the pieces and concepts instead of just trying to build it live. That is so much easier to handle and manage. Once you get the flow and concepts down, it makes it easier to transfer that knowledge to the live environment.

On a Zoom session with Calvin working on the web version of the adilas label builder app. We were trying to get some logging going and having a database issue on the content server. We also were having issues with the API sockets on the content server because it couldn't connect to the database.

Went into Smithfield to help my dad and Harry with adilas stuff. We got into inventory tracking, creating new users, and using the quick search features.

On a meeting with Wayne and John. We were looking at stuff on the content server. We were checking into FTP options, database stuff, server-side logging, and API socket connections. The content server mostly sits there and serves up files and media/content pieces. However, as we keep pushing things forward with Calvin and the web based adilas label builder, we are using the content server more to help with the processing of those pieces. Anyways, things are moving more in that direction.

Work session with Shannon to refine the internal questionnaire summaries. See attached for our progress.

Debugging the web version of the adilas label builder with Calvin. Recording notes form post-it notes to the developer's notebook - elements of time entries.

Cory and I jumped on a meeting to go over projects and progress. We talked about custom labels, server health for data 0, API socket tools, developer notebook, and other calculator type tools (web pages that don't require a login to use). We covered needs out in ecommerce land and helping to tighten up some of those pages. We still have some Flash clean-up to do as well. All of these are things that will help with the data 0 heath stuff. Cory and I were recording notes, details, and plans for each of these projects. Eventually, we'll get those pieces assigned out to a developer so that we can get them finished up and put to bed.

Great little meeting between Cory, Steve, and I to go over plans, projects, and priorities. Cory and I started out and then Steve joined us. He was traveling and so he was on the phone and Cory and I were on the GoToMeeting session. The goal was to create a small master list of projects that Mike with Herbo might be interested in. The benefit of that is that we, as the adilas team, get a chance to see what is still needed and what is coming down the pipeline. Progress is made daily, but sometimes it may seem slow if viewed from the outside.

I was writing and recording the notes (on a google doc spreadsheet) and Cory and Steve were commenting and adding their insight and input. We added some notes, moved things around, set priorities, etc. Good session.

As a small side note, progress doesn't always involve getting things all the way done... lots of progress happens along the way. We also spent some time talking about resources, developers, and who can do what. Just because you know what needs to be done, doesn't mean that you can just do it. You still have to balance the resources that are available. That gets tricky sometimes.

Checking in with Danny and Steve. Merged in some new code for Danny, dealing with some new custom labels. Steve had some questions and wanted to show me what he is working on with the mini units (serialized subs). John jumped on and we reviewed his payroll holiday chooser project. After that, Steve and I did a small session and looked over some clean-up logic for a project that he is working on.

Steve, Cory, and I going over projects. Steve and I did some manual data updates for a client using an older tool that we built years ago. It is always nice to use something that already exists.

After the small clean-up session for our client, we rolled into a brainstorming session to talk about priorities and projects that are either current or on the high to medium level. We are trying to get organized and get the projects that need the most attention, and/or get the best bang for our buck, out in front of us. We were organizing, sorting, and moving things around in order to set the order and priority levels.

Phone call with Calvin going over over some details about the web version of the adilas label builder. I merged in some code for him and pushed it up online. We are going to use some of the existing permissions for label building to tie the new web version in with the main adilas.biz system. We will also get Chuck involved to help with a small face lift for the new web version.

After talking with Calvin, I then called Cory and we did some planning and coordination on different projects.

Looking at XML code with Bryan. We were trying small things and experimenting with some scratch files. Hopefully we found a solution. We also talked about some other projects that are in the works.

Sean checked in. He has been on the road travelling but is circling back around. He was looking for Steve, but he was out as well. After that, John needed some help with a payroll project. We are building a new page for for of a payroll setting where they (each corporation) can select and set corporation level holidays, to help with holiday pay for payroll and timecards. Nice little work session as nobody else joined the meeting. It was just us.

Wayne, John, and I had a weekly server meeting. We went over a few things that we are either working on and/or that are still hanging. Nothing major to report. See attached for a few extra notes.

John and I spent some time going over the developer's notebook. It is currently on the data 0 box. We are planning to move that portion of the website over to a different server to help with spiders, crawlers, and persons who may be trying to use those pages as entry points (hackers). We were going over code and looking into page names and database tables. See attached for our progress. We still need at least one more session, if not more.

Shannon and I were going over and proofreading some of the questionnaire summaries from an internal questionnaire. We are making progress. See attached for our progress.

On a different note, we were reading over one of the sections and decided to add some more text and verbage to help explain things. As we started to add things, we could feel that we were losing some of the simplicity. We rolled things back and took out all of the extra stuff. We tried to further refine what we had as well. Sometimes it is hard to pull backwards. It often feels easier to add or keep adding to it vs removing and boiling things down to their simplest form.

Keep moving forward! Even if is is slow!

3/23/21: Dustin will make cultivation API changes for OR

Recording notes, doing emails, and small code merges for a developer.

Great meeting with Dustin and the gang. Dustin gave us a report on some of the cultivation projects that he is working on. He has three major projects that he is working on. They are: harvest packaging, bulk adjustments homepage, and a super cool one called accountability homepage. See attached for more details and notes. Great meeting.

John and I were working on the payroll holiday chooser pages and logic. Some of this was kinda new for John but we ended up going through cycles where we gathered up user form data (holiday date selections). We then took the dates, stripped off un-needed pieces, converted to variables, added to an array, add the array to a structure, and then converted the structure into a JSON object. We then saved the JSON object in the database. Some of that conversion processes was new for John, at least how we do it. Kinda fun and a good work session. Making progress.

A couple of the guys checked in. John showed me some progress that he is working on on the payroll holiday chooser pages. Looking good. I spent the rest of the time recording notes, uploading documents, uploading screenshots, and emails.

Chuck checked in and showed me some new progress on the main website. See attached for some screenshots. The new screenshots are dealing with the 12 main players and what they offer as solutions. See attached.

After that, I went back to recording notes and coordinating other pieces.

Weekly check-in meeting with Alan. I did record a small section. Alan is working on the aggregate vendor project and being able to push vendors to transactional corps. We talked about the backend code and some changes that are taking place in the code. Things like: duplicating structures, locking inside of the object instead of outside of the object, being able to reset things (transactions), etc.

I checked in with Alan and both Wayne and Eric are doing great on their projects. Alan was helping them out and being somewhat of a consultant on those projects.

Accountability of the developers

New database tables vendor catalog or vendor aggregate systems - enterprise_corporation, enterprise_mapping, enterprise_setting, enterprise_vendor_mapping

-----------------------

Checked in with John - general project update - not yet on the check write project - still needs to redo some certificates for Nagios stuff - server update - developer notebook and moving servers

John and I working on his payroll holiday selector project. Work session.

On a GoToMeeting with both Calvin and Chuck. Calvin has released some code to us for the web version of the adilas label builder. It works and is live, but we wanted to give it a little look-and-feel lovin before we released it (letting everyone know). Chuck will be do the re-skinning job on the adilas label builder. We met and recorded a small portion. Basically, we went over what we wanted and needed and some finer details of the label builder project. See attached for the recording.

After that, I jumped back on trying to catch-up and record meeting notes, emails, uploading videos, etc.

Merging in code with Bryan. We pushed up some code and then jumped into a high-end JavaScript file and made some tweaks. We did some testing and then merged in that file. It was dealing with parts and items and show on the web functionality. The new code will look at the part category (higher level) and then adjust the show/hide on the web setting for the item based on the default value for the category. Basically, connecting the dots a little bit deeper.

After that, we jumped on another project and changed up the logic just a little bit. We made some small tweaks and then pushed that project up as well.

Emails and recording notes to finish things up.

Touching base with Sean and John. We also looked into some scenarios with John's payroll holiday chooser project. He is making great progress on that.

Emails, recording notes, and general to do list items.

Great little work session - going over the questionnaire summaries and proofreading our responses. See attached for our progress. There was some mention of "Fracture" in the questions that we were working on today. We can't wait to get to that project.

Checking on funding, doing emails, and recording notes. Phone call with Steve to talk about plans and funding. Lots of good things in the works and circling around, we just need to land some of them.

Cory and I helped a client out by cleaning up some of their payroll and paycheck data for a single user. They had some things switched around and we used existing adilas tools to fix the data and get them setup correctly.

Next, we jumped in and did some project management and a deep dive on a project for an outside bank solution. The bank solution involves a data import tool, logic and matching (bank reconciliation), and then a nice printer friendly bank statement - all done through adilas and the outside banking solution. Most of our session was talking, drawing pictures, and putting notes and ideas on paper for a developer to get started with deeper planning and working on the project.

Recording notes and transferring info from handwritten pages to digital format. It takes extra work to do it that way, but it is way faster and doesn't disrupt the meetings and flow of things as they happen.

3/26/21: This is the beginning of a project that will allow for message marketing with a modal in e-commerce.

There were a bunch of the guys on the meeting. Mostly just checking in here and there and running small things pass Steve and I. Wayne had some database questions, Steve was working on sub inventory with mini units (serialized units within sub inventory), and Danny was working on some new notification settings. After Danny left, Steve and Sean  went over the power of using web based customer logs as direct ecommerce marketing tools to their clients. Steve has a lot of details and vision on that. He is going to have Danny start playing and building along those lines.

Cory, Steve, Sean, and I were all on the meeting. We were going over different projects, ideas, suggestions, etc. In the background, I was doing emails and small merges for some of the guys (just a couple of simple pages).

Meeting with Steve to go over some ideas and plans. Steve has been on fire today. He was pitching new ideas, lining out developers on small steps to bigger projects, and showing me new code that he has been working on. Fun to see. He has a lot of vision and loves to share it and push it along. That is awesome!

Here are some random notes:

- Steve's vision is great! He's been the primary visionary person throughout the years.

- Creative direct messaging options, using HTML compatible customer log notes, that populate out in ecommerce land. This could be controlled by settings, push notification to the user's or client's phone, simple one click login, possible bulk tools on the build and send side, ways of skipping or marking things as read on the user/client side. All kinds of fun ideas. As a side note, we already allow unlimited customer logs or customer log notes. You can already mark them as show on the web, and they will show up outside in the ecommerce area. All we would need to do is tweak that tech a little bit to turn it into a two-way messaging app. If we wanted to... just an idea at this point.

- Steve is working on the mini units project for a gun and firearm dealer. They can set a flag at the part or item category level. It says use or don't use mini units. A mini unit is a sub section under child or sub inventory. The sub, or package, could have multiple subs or serialized pieces under the sub inventory. The mini units project allows for something to be sold as a sub inventory item in bulk, and then as the invoice gets fulfilled, the different serialized pieces could be added in as details of the bulk entry. To explain, say you wanted to sell 10 of a certain item... The invoice would say sold 10 of XYZ item. Then, inside the system, you could tie in special serial numbers to all 10 of those mini unit items. This becomes a mix between a normal stock/unit (one-by-one serialized inventory) and parent/child inventory with granular control and ability to sell in bulk (simple line items on an invoice, but more details held in the background).

- Steve and Sean are going through different scenarios and figuring out processes and procedures. They are then making notes and coming up with solutions. The two of them have been able to work very well together. That is awesome.

- Steve sees one of our core values as being able to listen and hopefully understand what is needed. We are then able to make a plan to fill those needs. That is what adilas has been doing for the past 20 years. The market is talking and leading out with what they want and need, how can we build and capture that market?

- Sometimes the best thing is just taking the next little step. drop by drop, inch by inch, line by line.

- How can we capitalize on what we are building and basically inventing? We love doing R&D. We just need to help it start paying for itself.

- Steve really likes building contacts and doing social networking as a way of getting the information out and selling the product. He really likes, small, on the ground sales team that work and play well together. We pitch it, we sell it, we deploy and do setup, we help train and maintain the clients. We use small internal teams to do the whole process.

- I heard Steve pitching the dependable independent model to one of our guys today. They, our guys and gals, really love that model. Having said that, it does take a special person to fully bloom there. Sometimes it takes some getting used to and/or adaptation of sorts.

- My goal is to help Steve. The two of us together can make a lot of things happen. Good stuff. Both he and I can do whatever and be ok with it. Good Batman and Robin type team.

Emails, checking on funding, doing some follow-up on projects, and pushing up some new files.

Small meeting with Bryan. He was having audio issues on his computer. We merged in a branch of code and will let the auto deploy push everything in place later tonight. Mostly just some security updates on pages. Non mission critical but still needed.

Emails, texts, phone calls, and recording notes from other meetings today.

This morning was pretty busy. We had merged and pushed some code last night. One of the servers got the new code before the nightly auto deploy had happened. Cory contacted Alan and had him take a look at it. Alan ended up doing some emergency surgery to get things straight. We had done similar code prior, but this stuff had a few things that we overlooked and that were different. Anyways, Alan was on, and a number of other folks, letting us know what was fixed. I sure am grateful for his help and expertise.

Using ColdFusion query params (cfqueryparam tags) we didn't know that decimals had to have the number of decimals set per tag (called a scale or number of decimal points). We had also switched around some numbers and dates. We got it all figured out, but it did add some stress to the mix. Small scramble to get everything all good to go.

We were going to have a weekly server meeting, but Wayne was not available and we were still running around fixing code changes and tweaks. John was on and we had a small touch base meeting on some of the servers. Nothing major to report. We'll try again next week.

Sean, Steve, and I met with Dustin to go over some bulk move and bulk update options for his cultivation stuff. We are making plans to  use the counts to divert the clients to a bulk update process verses the traditional rendering of all information. We met with Dustin, pitched a couple of ideas, drew out some sample scenarios, and made a few plans. Everybody on the call was chiming in and all on the same page. Good meeting.

The general goal is to watch the counts, and do one of two things to help with the rendering of data. One, if the count is high, prompt and filter the records (even allowing multiple batch filters at a single time). The other option is to break the next step into slightly smaller pieces (counts per batch - within the returning record set). This would limit the amount of processing and still allow users and clients to view counts, quantities, batches, and be able to still drill-down to full details if needed. Kinda like an intermediate step where we show the groups within the data before we show the details. Both techniques will help a ton!

As a recap - group it, count it, break it down into smaller groups within the bigger group, and finally go to full details

Emails and follow-ups

Emails and recording notes.

Reviewing a 7 page document from Steve McNew - internal consultant and software process engineer. I have a copy of the document saved on my local computer. Some new and exciting things. Mostly a structured refinement of some of concepts, methods, and practices. Trying to become more structured and standardized in our approaches and philosophy.

I also had a half an hour phone call with Steve Berkenkotter. Part of it we were going over the document from the other Steve (software consultant), talking about funding, and what are the next steps for us as a company. We talked about scale, stepping up to the next level, allowing others to help handle small teams and sub projects, and concepts of the data assembly line.

We keep seeing a need for things to be open and flexible, then coming together and getting more rigid, and then expanding and contracting again, over and over. This same process will be needed as we go up the chain, clear into aggregated or master systems at the enterprise levels. These are the virtual flex bubbles or flex pods that we keep seeing. It all comes back to the data assembly line type concepts. Kinda fun to see it go full circle and even to keep expanding beyond the simple transactional corporations and worlds. "O|O|O" (pretend that those are little flex pods or flex bubbles - the O's are the flexible or open areas (based on phases and permissions), the | (pipe symbol) is the checkpoint or divider for the next level.

More info on the data assembly line concepts - help file

Working with Steve on the backorders homepage. This is taking a quote and slowly (depending on how quick things can be fulfilled) into an invoice or into multiple invoices (depending). We looked at some of his existing code and worked on a plan to improve some efficiency on how things were completed. Lots of fun logic mapping and simple text instructions that he can then translate into actual code (guides or directions).

Meeting with Chuck. We talked about some real estate investments and just general stuff. After that, we switched over and went through some new pages and pieces on the new adilas.biz website. He is working on some new banner images, mobile friendly headers, and looking into mega menus and what we can do there. See attached for some screenshots.

Chuck is also working on a dynamic way of showing different testimonials and being able to cycle through the different quotes and sayings. We also briefly talked about getting a deployment plan in place for next week. He is getting close to releasing things to production and going live with the new site.

Alan checked in and gave me a progress report. He is working on lots of error handling and unit tests (unit testing). We talked about how to use testing going forward. One thing that Alan likes about the tests is, as he goes forward, if he changes something, being able to go back and make sure that all of the prior tests still work (making sure that you are breaking things by changing or adding new code).

We talked a little bit about test driven design and test driven development. The more complicated the code, the more the testing is really needed to make sure that we didn't forget anything. Along those same lines, even if something is not super complicated, the sheer number of tests add up over time (testing for small things, not just the super complex). It gives the developer a level of confidence that things are still in order. We also talked about commenting code and prepping things for others.

I asked Alan about the learning curve for implementing the testing and unit testing stuff. He is getting better and better at it and would be willing to help teach others. So far, just Wayne and Alan have been doing the primary unit testing. All of the other developers test as they go and test up until code sign-off. When learning to do proper unit test, you have to learn about mocking things up, expecting certain results, and checking dependencies.

Other topics of our review were: DAO's (database access objects), services, and using script vs tags inside of ColdFusion. Alan likes script for logic and tags for output and mixed HTML and ColdFusion output. Lots of talk about re-usability of the code and being able to transfer and make things more modular and independent. Good update.

John and I met to go over the payroll and holiday chooser piece. We worked on some date manipulation stuff and keeping the future dates, even if the date range submitted did not include the other future dates - helping to keep things persisting along the path and throughout the process.

4/14: 2.74

4/8/21: 1.98

There have been some requests for us to check out the check printing in the classic mode. The user reported that the memo field was not showing up. This is part of the conversion from Flash printing to HTML and JavaScript printing for checks. The main project has already gone live. This is more of a clean-up and circle back around type project.

Shari O. joined the meeting and had a tech support question. We ended up modifying some code to help with the issue. Pushed up code to all servers. We also talked about adding in digital signatures and dates for our PDF documents that we populate and/or control through the system. We would love to keep taking things to the next level on the digital docs.

Eric called over lunch to talk about his aggregation project for daily sales tax totals per location per day. We talked about the po/invoice line item date and when that changes and how to virtually trigger events based on changes. We were talking about simple strategies as well as deeper update and logic checks for things when they change or get updated. He is making some great progress.

Meet with Steve McNew via GoToMeeting. Steve M. lives in Colorado and is a retired software engineer and project manager for US Air Force level project and contracts. He is going to be helping Steve Berkenkotter (normal Steve) and I out with taking things to the next level.

Brandon (myself) has a seven page document that goes over a bunch of questions and ideas that Steve M. was proposing and pitching. Much of the meeting today was going over that document. Here are some of my other notes:

- Pull in some nuggets from other places

- Base line assessment – top down and bottom up

- Finding the low-cost solutions and putting those pieces in to play

- We do have a place for the docs to land and be housed – docs, reports, standards, forms, checklists, letters, updates, etc.

- Steve M. has some possible samples – may need to be sanitized (from other projects and other clients)

- Capture some of the proof of concepts, prototyping, risks/approaching, telling the story, R&D – we already do tons of this... maybe bring it more into the forefront of what we are doing and even marketing

- Model based engineering

- Throw a few things around and see what fits

- Connecting the dots – lots of existing pieces, let's just start connecting the dots

- As we connect these dots – how can we turn this into marketing?

- Some migration stories – where are we headed, where were we, and where are we now?

- Layering the big picture

- Trade studies – why do you do what you do? Prove it and/or show the reasons

- Finding our own mix of methodologies

- Steve M. will throw things at us and we'll judge and respond

- Letting some of the things rise to the surface and even showcase things

The following are a few URL's (web pages) that we used while talking. Some fun things:

https://www.adilascontent.biz/top_secret/images/corp748_EA81FBBDE6/pdf/doc_144771_AF2CA12EDB.docx - starting of a plan for our company

https://data0.adilas.biz/top_secret/help.cfm?id=393&pwd=map - help file and diagram of the interactive map - inside look at adilas

https://data0.adilas.biz/top_secret/help.cfm?id=479&pwd=core - help file and diagram of the core interface and world building concepts

https://www.adilascontent.biz/top_secret/images/corp748_EA81FBBDE6/pdf/doc_81817_A099C1744F.xlsx - versions of adilas

Recording notes from earlier meetings.

Bryan jumped on and we went over a project that he is working on dealing with bank statements and what not. We went over what we had and made a plan from there. The current project he is on is a bank/payment solution that doesn't have their own PDF bank statements. We are going to help the other company out by providing details out of adilas for all deposits, expenses, and summaries for that bank. We already do that, we just don't make it look super fancy and turn it into a PDF for storage and/or printing. We'll just take what we already have to the next level.

As a side note, if we do add in the ability to save existing bank register or bulk reconcile pages as PDF's, that would be a nice enhancement for what we already have.

Recording notes for the day and cleaning up my list of little post-it notes from prior meetings today. Busy times.