Working on the custom data export tool for Trailer Solutions. Added a number of new checkboxes and if statements. Trying to make the page and export tool more dynamic.

Working on the custom data export tool for a client. Worked on making the form fully dynamic and then adding in custom pagination (next page options). The pagination took a bit of time as I haven't done that in a while. Light testing and page review.

Small sales meeting and morning meeting. Some of the guys were talking about linking things together and how that takes time but really helps with the flow of both data and logic. The ability to link things together is huge and rests on the web technology called hyperlinks. It's been around for some time, but the power of what it can do is not fully realized. That's pretty cool!

We got into talking about how we have tons of features but some of them are hidden, or no one knows how to use them. It's our job to keep pulling thing together like a zipper be zipped up. Organization, links, navigation, settings, and permissions will be needed to continue to keep pulling things together. Those are huge parts of the system.

Shari O. was talking about some new hardware that we are going to be buying. The sales guys are going to be able to give some of the hardware away to help with the setup process and to sweeten the deal for our clients and customers. That's pretty cool. We have never really done that before. Basically, taking away the barriers to entry. For example, including a free credit card mag stripe reader or whatever.

After that, the guys were talking about 3rd party integrations and the problems and disconnects that we run into with those solutions. They are both good and bad. Sometimes, they put up good money and help push the ball along. Other times, something goes wrong with either us or them (usually them) and it gives us a black eye. Meaning to our clients, they have gotten a bad taste in their mouth due to problems or promises being made (either side of the fence). We've talked about it before, but if we put as much effort and energy into our own product as we have given to outside 3rd parties, we would have a ton of stuff. Like I said, it's a bittersweet subject. It has helped by filling a role but has come at a higher cost.

Steve was talking about going back to finding and setting up smaller companies. It's so much easier to set them up and get them going (how much red tape). We then switched over and were talking about some of the sales staff and what they are doing and/or trying to do. Currently, our goal is to just get them going and help them learn step by step. It's a process.

While they were talking about stuff, I was pushing up code for Trailer Solutions for their custom data export tool.

John was reporting on some new updates on the department homepage. Eric, Cory, and I were looking at gift cards and scenarios with different settings. We had an internal email bug reported to us and we started looking into it. John was the lead and doing most of the debugging today. Bryan joined us as we were checking things out. Sort of a grouped effort. We spent quite a bit of time looking at the email stuff. We pushed up some new code and John will get with Wayne later today to finish things up. We did what we could for current time. It will need more attention later.

More work on the custom data export tool. It is getting really close, and I pushed up new code. Writing out some documentation and getting some screenshots. I had to install Photoshop to edit the screenshots (my hard drive crashed, and I didn't have that installed yet). Recording notes while waiting for the program to download and install. Sent an email out with the screenshots and the web link to the export tool. The export tool has a series of checkboxes to show/hide data or sub data relationships. You can filter it and it shows JSON data for customer info. It also includes customer additional contacts, flex grid tie-ins, customer log notes, media/content files and data uploads, etc. Pretty deep customer-based export tool.

Scheduling time, doing research, and planning for some custom code that is needed for Beaver Mountain. Went in and made a whole to do list inside of my digital scratch file. I'll be working through the list. I spent some time reading over my notebook notes from meetings with the client. Transferring hand scribbled notes into digital to do lists.

Logged into their new system and spent some time going through corp-wide settings, locations, snow owl look and feel, and ecommerce settings. Feeling better about the project and making good progress.

Met with Bryan briefly to talk about projects. He had some family over and we had to cut it short. We'll hit it again tomorrow.

Checking emails before the server meeting. Once the meeting started, we went over some of the changes that we have been working on with internal emails, output formatting, and changes. Wayne is working on things and going through a process of elimination to figure out what else is still needed. Cory and Wayne were talking about scheduling and plans for new feature releases. We also went over some other projects and gave small reports to make sure that everyone was on the same page.

Cory and I looking into an inventory disconnect. She was calling it a ghost cost out in inventory. It had a similar feeling to a project that we would like to call internal cost corrections (ICC). Anyways, the error ended up being that the company had duplicate vendors and the code was grouping things based on the vendor's name, thus creating a missing vendor and its data.

The fix is to make sure that the vendors don't have duplicates or redo the code and make it loop over vendor id's vs vendor names. The id's would always be unique. Anyways, we talked about work arounds and ways to fix the data and get the vendors and items fixed and merged together. There already exists a tool for that, we just have to talk the client into to using it.

Work session between Eric, Cory, and I. We were testing and going over gift cards and trying to see if we could push some things up to data 0 for live testing. We looked over code, made some back-ups, and then did some code review. We ended up pulling the code branch onto my local machine and did some testing instead. We found a few problems.

After Cory left, Eric and I made some plans for moving the project forward in smaller pieces. Currently, there are too many system level dependencies and things that deal with the entire application scope variables and values. We are going to push it up in smaller pieces or waves so that the dependencies become less of an issue. It may take a few days (vs a single quick push) but it will make it smoother. Good plan.

I got behind. Recording notes from the past couple of days.

Danny, Sean, Steve, and Michael were talking about sales and sales leads. They were also talking about other sales related topics like Ag (cows and farming), CPA's (accountants and do they have or see a need), state compliance centers, fees for merchant processing, etc. They were also talking about other point of sale systems and pros and cons of those systems. The conversation went out to Uber Eats and other delivery services.

As it kept going, Steve was encouraging the guys to keep looking for the pain points and then being able to solve and help out to relieve those pain points. Sometimes the users or possible clients see a system and start thinking about the future workload to get a system up and running. That can scare people away. We are looking for solution minded people who are looking for a system.

The guys were talking about asking for other leads and trying to keep it simple. Helping them to basically fill in the gaps where possible.

Phone call with Steve. We were talking about ownership and year end 1099's. Emails and text messages. Random to do list stuff.

Work session with Bryan going over projects. We talked about date-picker stuff and then moved onto scheduling. I was pitching a small proposal to add in a temp roster for the horizontal time view. This would be a JSON formatted setting that would allow you to pre-load in certain people to your horizontal time view. It's not real availability, but it was a step in the right direction. I did a bunch of drawing and brainstorming with Byran. Most of it was on the fly. He recorded a few notes.

We then switched and got into deeper availability and the layered calendar options that we are planning on building. This flow would allow us to prep or overlay a schedule or virtual availability schedule over the main calendar (elements of time). We went over ideas for flow, logic, and what it might look like. We determined that there were 3 main steps. For a single assignment, we would need who it was that was being assigned? The who could also be the what. For example: are we setting the availability for a person, place, or thing? That's step one. Step two would deal with a date or a date/time range. These first two steps would always be required. The third step would ask if we need to reoccur or duplicate those new availability settings. We would need to select that option, only if needed. If used, we would copy or duplicate the existing settings in bulk.

We got into tons of details and ideas. Lots of drawing and brainstorming. Bryan and I were even playing in Microsoft Excel and doing some fake table layout and data input stuff for the new layer tables. We would like to think of the new overlay functionality for the calendar as layers or availability layers. This will end up being part of our "any" scheduler. Behind the scenes, we will have the real elements of time (that already exists). The front or overlay layers will be for things like employee scheduling, non availability, holidays, web availability (options for online booking), etc. Fun stuff.

Phone call with Eric. Making a plan for deploying the gift card project. We have already rolled it out a few times but had to pull it back due to some random errors. Our next deployment will be staged or done in waves to get rid of the system dependencies that exist at the application level and the session level.

Recording notes and digitizing post-it note entries.

New code with Eric for gift cards. We also decided that we would add the adilas quick search to the classic homepage in the top header as well as all other pages. That was the only page that has/had a built-in quick search, so we didn't think that we needed it in the header as well. We have had requests to put it on all pages, even if it is already there. Some users use the quick search as a primary navigation tool.

Cory joined us and we went through some scenarios and did more testing.

Quick sales standup meeting. Everybody was reporting in and what they were doing. The focus was on continuing to gather information. Maybe looking into multiple sales channels. Most of our clients could benefit if we could provide services or help them sell their stuff through multiple channels.

For us, we will continue to make calls, doing email campaigns, and online research. The guys were also talking about different angles and circling back around on different companies. Danny was saying that sometimes the easiest person to sell is a salesperson. Lots of groundwork. We even talked about teaming up with others to bring a bigger team or group effort.

They spent a bunch of time talking about SG&A (selling, general, and administrative expenses) for internal production. We will be looking deeper into production and manufacturing companies. More gathering info and solving pain points. That's where we shine. Lots of talk about selling support, training, no contracts, and price points. Ideally, we want to help people do well and succeed.

John was reporting in on some new look and feel changes. We will be pushing up some news and updates that talk about a blanket number of changes. It would be too much to cover every change that is coming down the pipeline. The main goal is to help standardize the look and feel. Some of this will be done with page level settings per page - what to show/hide, verbiage, aliases, rules, etc. There is a progression of things! It just keep going!

Planning with Bryan. The topic of the day was brainstorming on the "any" scheduler or any scheduling stuff. We talked about a number of different steps and what we could save and where.

1. We will use JSON page level settings for simple and advanced (shifts) rostering. Thinking about a number of different tabs going across the page for the new settings. Tab 1 would be simple full day rostering, tab 2 would be advanced shift level rostering, tab 3 would be shift settings, and tab 4 would be the web availability stuff listed below (in number 2).
2. The more advanced stuff will be saved in the layers or availability layers. We have already come up with 3 sub steps of that process. Click here for more info about the web availability layers. As a note, the web availability layers would be saved in a database as individual records vs JSON object storage. It will help us look things up and map usage/availability levels better.
3. We will offer a number of different, user defined, saved favorites. These are custom reports with saved search criteria. Some of these may be calendar views, horizontal time views, vertical time views, and other custom reports. Here are a few links with some ideas. See element of time #'s 8004 and 6967 in the shop.

Good brainstorming session and going over ideas. We got pretty technical and did a lot of drawings. It's fun to see how things progress and the progression of things.

Building out the unique and special events for Beaver Mountain. Going through the checklists from my notebook from an in-person client meeting with Beaver. Small time and flex grid code changes. Pushed up some files.

Meeting with Aspen on her world building research and visual timelines project. Light training and history of adilas. Printed her out a check. Pitched an option for co-ownership for part of adilas, llc - MMLLC - multi member LLC stuff.

Emails and merging in some code for Dustin.

Working on Beaver Mountain special events. Small bug fix on the classic add/edit parts categories page. Adding in new vendors, part categories, and items for Beaver. Setting up ecommerce images and ecommerce settings. Tons of new product images.

Working on Beaver Mountain stuff. Merged in some changes. Small tweaks to internal elements of time pages. Working on code.

New user accounts for Kristy and Amie for Beaver Mountain. Working on formatting on ecommerce pages and micro tweaks to code.

New custom data collection page that submits data to the paperwork or registration form. Custom code for Beaver Mountain special events.

Shari O. joined the meeting and let us know about a new state withholding tax called "FAMLI" - pronounced family. Each of us on the meeting was giving an update on what we are doing. More need for mobile and doing ecommerce type transactions. We are also seeing more of need and want for online ecommerce appointments, scheduling, and online signup for special events. We spent some time talking about our current sales staff.

Some of the guys were talking about going to other peoples sites and checking out what they have for ecommerce and how their checkout and transactions take place. Kind of some research, in a way.

John was reporting on some new CSS and layout changes that he is working on. We are making progress there. Things are heading more and more towards mobile ready and mobile responsive development.

Emails and working on adilas ownership percentages for Wayne and Marisa. Built a small spreadsheet with percentages of ownership to show who has was percentage. Steve and I are helping to spread the load and also the ownership. We are excited about that.

Merging in code for Bryan. Looking at date-picker stuff for 20 different files and pages. We then switched over and he as the first round of the simple rostering for scheduling done. We merged in that code. We had to fix a couple of merge conflicts. Pushed up new files to data 0 for testing.

Two different sessions, working on custom code for Beaver Mountain. The first one was from 1:30-4:00 pm and the second was from 4:30-6:30 pm. Spent time looking into custom data collection and waivers and paperwork. Tying the pages into a time id and invoice number. Worked on hidden flex grid fields to pass along for the forms to work correctly. Started building the new waiver/paperwork file.

Working on some custom code for Beaver Mountain and their special events. Spent time working on waivers, paperwork, and prep work. Pushed up files and prepared for live demo. Getting vendors, items, PO's, web settings, elements of time, and photos all ready.

Went into to the Beaver Mountain office and worked with Amie and Kristy. Showed them a live demo of the special events and how things work and flow. Good demo and making progress. They gave me a small list of other things that are needed and wanted. Great meeting.

Bryan and I looking at the advanced rostering and scheduling options and settings. We are getting into things like days, swing, and graveyard shifts. More work and planning on the "any" scheduler. Talking about next steps and going over plans. Bryan is doing great and we are adding in more settings to help things be data driven vs just code driven. That allows us to cater to more people and clients without super detailed custom code. If we base things off of the settings, it becomes data driven and even if it does something special, it is based off a setting, so other can use or do the same thing. Good stuff!

Checking on a list of parked domain names. I reported back to the guys about how my Docker server install was going. No problems on my local development environment. We talked about other server level projects such as: inventory snapshots, email formatting, gift cards, dependencies, and sales tax aggregates. We keep making small little tweaks. We also checked on a number of other small projects.

Eric popped in and he and Wayne were talking about triggers and stored procedures. They were looking at the database entries and what not. As part of the meeting, they (Wayne and Eric) were physically looking deep in the database. Eric is going to circle back around and do some more checking on his side of things. They were reviewing the stored procedures.

It was kind of fun to watch them view and refresh some of the aggregate data on the fly. Cory was acting as the user (actually doing something inside of adilas), Eric was orchestrating what to do and look for, and Wayne was doing the backend calls and database SQL statements. It was fun to watch, as a fly on the wall.

Eric is going to run some debugging scripts on the data. They are looking for a cause and effect scenario. They were also looking at servers, monitoring processes, and running pages. From what it looks like, they will need to do some further data research and analysis. They are trying to get to the bottom of the data differences between the transactional records and the aggregated data.

As a note, if we can't get with Wayne, John is the backup database admin person. He has access to all of the different servers.

Eric and I were pushing up files for wave one of the gift card project. John and Cory are going over the discount engine and talking about ways to do live testing with good data, without hurting anyone's live data. As a wish list, the developers would really like a way to get good clean data (basically a new database or new data) at will. Some of the data that they end up with gets muddy, due to testing, demos, and bug fixes. Sometimes they only complete a part of the process. It sure would be nice to be able to clean that data or database up with a click of a button. Basically, a restore to point x or y (whatever or even an ongoing good and clean data point).

After John and Cory got finished, Eric and pushed up some more code for wave one. The goal was to get some of the dependencies out of the way without leaning on them (using them). That way, when we push up the next wave, those other dependencies will allready be there in place.

Fun show and tell with the guys and gals. I showed off the Beaver Mountain special events, how we are building in paperwork and release forms, subs of time, history and usage, and customer logs. Danny, Sean, Michael, Shari O., John, etc. were on the meeting and I was just explaining things and showing the guys where we are headed, drawing, asking questions, good back and forth, and just having fun. I'm not sure if they knew it or not, but they were my audience today.

Meeting with Shari O. and John. Going over payroll and new requirements. Whether or not we like it, on payroll and other things in the system, we have to virtually keep up with the Jones (stay up to date). We talked about some new settings for other withholdings 1-5 and helping to standardize those names and values. They are very flexible, but maybe too flexible.

If the company isn't careful, they could mix numbers for different things. These custom withholdings fields are for things like 401K, insurance, dental plans, meal plans, child support, Aflac, IRA's, etc. The problem is, if one person has child support and they put that value in flex withholding field 1, then they have to do child support always in field one, for other people in the same company. If not, image how crazy it would get if Betty (fake person) has field 1 for her 401K and the Tom (other fake person) has field 1 for child support. Individually, they would be totally fine, but any combined numbers get muddy and mixed.

We talked about the need for some other payroll settings (show/hide, aliases, global naming, etc.). We will create these new settings and then help our clients configure things so that they run how they want them to run. Basically, we'll help hold their hands through the setup process.

Cory and I were working on projects and project management stuff. Shari O. was reporting on the new payroll rules for the state of Colorado. We spent some time talking about the new payroll settings and how to help them handle things. We talked about both fixed values and dynamic values. These new payroll settings will end up being a new project for Bryan and John.

Next, we checked on some custom data for a client. We figured out a few things and sent them an email asking which way that wanted us to fix the data. After that, Shari O. and I got on and did a small session on graphics and editing PDF's. She may need some Adobe Creative Cloud tools to help her out. She it trying to modify existing welcome packets and what not.

Work session with John. We were fixing some CSS and making changes out in the shop. We fixed the ecommerce view for what are called icon boxes (a view out in ecommerce - layout). The display needed more space and we had to move the price and add to cart buttons around. It got a little deep, due to the settings of what was going on. After that, we started into the Beaver Horizontal time view and trying to add tool tips to the layout and view. Because this page is custom and somewhat old, we had to go back to older styles of code. The new pages have that stuff built in, but the older pages couldn't pull it in, there were conflicts - libraries and other crisscrossing dependencies.

Merging in code with Bryan to help with some date format stuff. This was going from a 2-digit year to a 4-digit year, in order to work better with our date-picker plug-in. We then switched over to the advanced rostering settings for elements of time. We got into the shift settings and what is needed for the next steps. We just keep walking it forward. Talking through things and making plans.

Emails and some data clean-up for a client. They had us remove some duplicate parent attribute assignments that got added in somehow.

Got an email request from the client to add a few new fields into the custom export tool. Tweaked the form to show the address 2 (mailing address) and the customer status fields. Also added in a new report filter to help show/hide active/inactive customers. Pushed new file up to the server and emailed the client with the update.

Quick sales meeting. We are finding gaps in older systems and seeing needs. We are going to try to fill in those gaps. We can do so much more, but there is a need there and we could get our foot in the door. We are looking for pain points and then help them improve and keep going. We can mix and blend and mix and match between our 12 main system players and 12 main business functions.

Steve and I spent some time looking into a complex data structure that he is trying to build out. This is for a 3rd party menu system. We also spent some time talking about being able to build out a small custom website for our clients. Some of them don't have anything and need some small contact us pages, about us, and sort of a homepage of sorts. We could just add those pieces to the ecommerce site and be good to go. Just some ideas and thoughts.

Steve is going to be playing with parent attributes and tiered pricing. He already has a small, hardcoded solution but wants to build it out a bit more and make it more dynamic for ecommerce transactions. Internally, we use a thing called a smart group that has rules and assignments but in ecommerce, we need to make it a little bit simpler because the users/customers don't have as much control or power.

John had some questions about some of the pages that he is reworking. He is working on look and feel and adding in responsive design and page layouts. After John left, Steve and I had a small chat about elements of time and where we are heading. Working on more time, event, and calendar based settings along with options for online customer facing booking and scheduling. Good stuff.

Bryan and I working on some of his projects. He has quite a few right now. We went over some of his rostering and new tool tips for the horizontal time view. We then flipped over and talked about new global payroll settings. We spent most of our time going over the show/hide settings and the custom naming for the 5 flex fields for doing payroll calculations. We went over commission fields, page flow, requests, etc. He took a bunch of notes.

This is a side note for me. I have a notebook that I use at church and what not. I had it opened on my desk and was reviewing a talk by Bishop Gerald Causse (french name). He is the presiding bishop. Anyways, his talk (10/1/22) was dealing with stewardship and caring for something. Sometimes I get overwhelmed by how much there is to do with adilas and building this whole system. I've been working on this project since 2001.

After reviewing my notes, I was trying to look at my role differently and how I help and take care of the adilas system. I can't do it all, there is no way. But I can help, take care of, and add my efforts to the mix. That is huge and my cumulative efforts add up. I am trying to be a good steward. Some of my stewardship deals with code, concepts, and vision. I can do that. Also, if you are a steward, it lessens the pressure (in some ways) and that will help. My personality tends to hold on to things way too long and sometimes that is not healthy. Anyways, learning and growing as we go. Yee haw!

Working on three different projects. First, quick tweak to help with High Valley Bike Shuttle and setting up reports and shuttles for the next season. Second, sending files over to Beaver Mountain. These included some instructions, template files, and blank registration forms. I also sent an email to the client with information. Third, I worked on some new tool tips for the Beaver Mountain on their horizontal time view. The folks at the ski school have requested a few things. Playing around with ideas and options. Light research.

Going back to the idea of setting up custom verbiage and SOP's (standard operating procedures) for clients, we have a ton of great options in the top header and footer for the snow owl theme. Each person has 8 of their own custom navigation links and buttons. There are also over 40+ custom navigation links and buttons that may be setup per corporation. If used correctly, it would make access to simple SOP's and other custom training, education, or tips available to all users, right from the site, using the custom headers and footer links. That is pretty cool. We need to remember this when we are building out fracture and our next theme and framework. These custom links and buttons are huge. What do you need? Where do you want to go? What is important to you and your company? Let us help you out... Good stuff!

Working with Russell on a Saturday. We talked about all kinds of subjects and topics. Here are some of my notes:

- Self-help and continued education and learning. One little bite at a time.

- Using Microsoft Paint for quick drawings when I don't have the drawing tools from Zoom or GoToMeeting. It works pretty slick and can be pulled up quickly.

- On CSS templates and themes - spending time to get to know the templates and CSS themes. Get to know the components and what is already done and what can be modified and tweaked as needed. Well worth the time to get to know the templates.

- Priorities and getting the correct talent and teams together.

- CSS theme forest - some great pre-built themes - Making things flow and look pretty.

- Splitting up backend code, database logic and access, and frontend views and code. Once you get them all split up, it makes changes, on either front or side, easier to make.

- Back to templates and components, he explores around, looks for elements and asks, can I use that theme for something that I (or my client) wants? Don't get tied in to just what you see - look for potential.

- We can't do everything by ourselves - if needed, hire someone who has vision and can spend the time to make it happen. Make it a priority.

- Looks, performance, functionality, ease of use, and support - what clients are looking for.

- How easy is it to do a certain task? Learning from the user's habits and expectations. If needed, get a good UX/UI developer. Ideally, have a nice frontend that hides the whole backend. This can make it more feel more industry specific.

- Paving a path for our users.

- Full API socket backend. That is true power if it can be harnessed.

- Russell's goals - powerful, looks good, and easy to use.

- Using Adobe XD to mock things up.

- Making little building blocks. Then you can move them around and put them anywhere.

- Full mock-ups for the whole course or phase(s). Getting approval, then breaking things into smaller tasks to assign out. Figuring out routes, templates, flow, etc. Russell uses his team to help prep it for the developers.

- Someone has to manage it or coordinate the rollout.

- Using greenies (newbies) vs a senior developer. There are pros and cons to this approach. You have to almost look at each scenario and then decide what your course of action will be.

- Building things more modular for reuse.

- Everything comes down to choices. Including... whatever we don't change, we are choosing to let it be. It all comes down to choices.

- Leaving things better than you found it. Just like going camping.

- Grow from where you are at!

- Teach me (whatever) and then I'll choose.

- Russell's underlying concepts - pray hard, work hard, and use the talents of others around you. Russell likes to use the Big Guy upstairs (prayer and inspiration).

- What's our budget? What can we do to get more budget? Don't just see the budget and then stop there. If it's not enough, look at other angles and see what you can do (within reason).

- We talked a lot about life's pace. The keyword is "pace".

- Pondering the path of your feet - where are you heading? Mixing and blending what's in front of you.

- Smart goals - S.M.A.R.T. goals - Specific, Measurable, Attainable, Realistic, and Time bound.

- The drip affect - that is awesome - the accumulation of tons of drops over days, weeks, months, and years. The compounding effect over time. Leaning for transfer, means leaning one thing and it helps you with another thing. Learning starts compounding and multiplying. That is really cool!

- Going back to measuring growth - what does a little bit of (____ - fill in the blank) do for us?

- Virtually filling our lamps, small changes, seeking and putting ourselves in good habits.

- It's ok to need help.

- Plans for our next meeting time. Russell and I talked about building out a small, baby component, from research, to mock-up, to code, in order to go through and do the whole process. Sounds fun!

Morning meeting with all of the guys. Everyone was reporting in and giving updates. I gave an update about using the snow owl theme headers and close to 40 custom navigation links that are available to the whole user base, per corporation. We talked about an update on gift cards. Eric and I are working on that project and trying to roll things out in waves.

We switched over to talking about ecommerce and gaining more control via settings and options. Steve was commenting to Danny about tiered pricing out in ecommerce land. There are some new options coming and we'll take the existing pieces and just keep making them better. As the discussion progresses, we were talking about our general approach and how diverse our user base is. Because of that, we have a ton of tools that some clients may never want or use. In that same breath, we can also offer things to our clients that they never would have gotten if they had a specific software package that only did one specific thing.

The guys were talking about problem solving and how we excel at that. Steve was talking about a shed analogy and how you can have a ton of different tools in the shed, but you only pull out what you need for a specific project and/or task. That's adilas, in a nutshell. Just for fun, Danny was talking about the TV show MacGyver or MacGyvering - making it work with what I have. We love the challenge of trying to make the glove fit. We have tons of tools and features that we can mix and blend to make it happen. Good stuff.

Helping Steve with some image paths for a 3rd party solution menu system. After that, John was showing us some new pages that he is working on and changing the look and feel. We looked at some custom Expo/Herbo code and layout stuff. At times, we are not sure what certain older pieces of code do and accomplish. Sometimes, just like in life, we have to fake it.

Steve chimed in with some accounting history to help John with some of our terminology. He was talking about the term "Posted" and what that used to mean. In a way, this older term was a way of locking things down and moving data along a virtual data assembly line - old school style. As a side note, it is amazing how much training and education it takes to help our users know what to do and how to do it. That seems to be a never-ending process.

The last topic of the meeting was looking at some of John's new mobile responsive code and page layouts. It is looking good. We are excited to see where it goes.

Working with Bryan on the date-picker changes. He had a few files that we merged in and pushed up to all servers. Cory has been letting us know about pages with date-picker issues and Bryan has been fixing them. The main problem is switching from a 2-digit year, like 23 vs a 4-digit year, like 2023. The new date-picker likes the 4-digit years and defaults to that format, if you don't provide enough information. Anyways, we are reformatting code so that it starts with the 4-digit year. That seems to help it out.

Next, we switched over and started looking into some of Bryan's shift-based rostering (who will work days, swing, and grave for certain days) for the horizontal time view project. He is making progress there.

After Bryan left, Steve and I jumped back on and worked more on some 3rd party menus and image paths. Steve is working on a new API menu system for a company.

Paying bills and recording expenses. Going over emails.

Eric and I working on the gift card project. We had it all ready back around Thanksgiving time but we've had a hard time getting it fully integrated. Lots of variables and things (application level changes) keep happening all around us. We are making progress.

Today, we ended up having to roll back some commits and try to get his code branch back up to date. Somehow it got all mixed up. While Eric was rebooting his computer, John and I talked about an error message and tracking down a bug in the bank transfer code. After Eric's machine was back up, we spent a bunch of time trying to reset his branch. Sort of a salvage type mission and session. Thank goodness for Bit Bucket and the code repository. We had to go through a number of sub commits and try to reconstruct the main gift card branch.

Emails and recording notes for the day. I'm a little bit behind. You should see how many post-it notes I have on my side table. Stacks.

Emails and recording notes from yesterday and part of last week.

Danny was reporting on a sales demo from yesterday. The company that he is talking with has some complex shipping and fulfillment requirements. We talked about, if we can catch the data, we can then calculate things and help them out with quotes and shipping costs. The guys were talking about using complex parent attributes and possible tie-ins for outside shipping API sockets and connections.

The guys had some questions about inventory planning pieces. We decided to get Alan to give us a demo of what he is working on for a client. No one really knows what it is other than Cory who is helping to quote things out and point Alan in the right direction. Anyways, he will be giving us a demo on Thursday morning for the morning sales meeting. It should include stuff on scheduling builds, reserving inventory, planning, and doing the actual builds.

Steve was reporting on some of his sales conversations and leads. He has been meeting with a number of different folks and just reporting on each of those contacts. One thing that he kept saying was that some of the potential clients feel like they are growing out of their current solutions. That is great for us.

The last two subject for the morning meeting were talking about 3rd party delivery services and options as well as internal look and feel changes for pages. John is doing a great job and he's been pushing up new files here in the past few days.

John and I were looking into a possible bank transfer bug with Cory. We found it, but we are not sure that it is a bug. It may be that the user is using it to do something that it wasn't designed to do. That happens more than we know. We then did a critique and review of some of John's new look and feel pages. All in all, I'd say that it is looking good. We talked about how much scrolling is needed and maybe adding in a quick summary section to help get people to the meat of the page as quick as possible.

John is going to be pushing up a number of branches of code here later today. All of them are dealing with deposits, banks, and expense/receipts. After that, we rolled over and started talking about levels of mobile responsive design stuff. We want to get what we can this round, but we also know that we may have to circle back around and pick up that piece at a later date.

Brandon is going to be checking out the parked or other domain names that need to point to adilas.biz. We have like 30+ different domains that point to the main adilas.biz site. Wayne was on the meeting but feeling kinda sick. He will keep working on his tasks that are already assigned. At the end of the meeting, John and I were talking about controlling the printing to make that look good. Sometimes you think that you can just design something and it will work awesome for desktop, mobile, and print. Sadly, not always true. Depending, sometimes you have to design and have code in place for all three versions (desktop, mobile, and print).

A couple of different sessions. Small review session with Bryan on cross-corp invoice to PO processes. He is working on a sub barcode project. I spent some time checking out some of the adilas domains that we have pointed to the main adilas.biz website. I was supposed to get a list out to Wayne on my findings. I made an Excel spreadsheet and saved it in the Wayne folder on my local drive. I also met with John after lunch to go over some more quick layout discussions. We looked at things and made a decision. He is going to keep pushing it forward. We should have new pages (redo's and new look and feel facelifts coming online weekly). That is awesome!

Recording notes. One of the entries that I was recording notes on was a fun meeting with Russell last Saturday. See elements of time # 9765 for full details. Lots of stuff for adilas (business stuff) and lots of just life lessons and concepts. Good stuff!

Eric and I doing some gift card project planning and testing. We were splitting up a code branch to do a second merge and release wave. Testing on my local branch. Lots of back and forth with Eric. Merged in the second branch and then talked about group dynamics and lessons learned. Making progress. Hoping for one more branch tomorrow, and then it will be fully up and deployed on the master branch.

Emails and recording notes from today. Light clean-up stuff.

Pretty quite morning. Michael and Eric jumped on briefly to check in. After we chatted for a bit, they bailed out to work on their own stuff. I went back to trying to catch up with recording notes and doing emails.

Page layout stuff with John and Cory. Getting good feedback from our clients. The hard part is listening and then implementing changes. Cory and I then went over a number of projects. We have a request for a custom (bigger) image for printable invoices. New payroll settings with show/hide options and new custom alias names and other settings. We also talked about charging for training. We fail at that sometimes.

We got into default corp-wide settings and wishes for the future. It is amazing how quick our clients want things, but at the same time, and in the same breath, they want sub settings, micro control, and sub level permissions. It's a very interesting mix.Cory had a list and we went down the list and chatted about projects, updates, and other things that are coming down the pipeline. Cory had to leave and John and I flipped back over to look and feel and layout stuff.

John is reworking the bank pages, deposits, and other financial documents and pages. We talked about responsive web stuff and also flipping it over to printer friendly. We haven't had to worry about printing much, we just made web pages and people printed them if they wanted to. Things change with certain responsive websites. You have to almost treat pages as three separate layouts and designs. You have desktop (full web but on a bigger screen), mobile (phones or tablets), and then print. You have to address all three. That adds a challenge, especially with thousands of pages.

Towards the end of the meeting, John and I were talking about graphical homepages and some of our ideas and goals there. I told John that we had been dreaming about graphical homepages for years. We would love to add in a consistent look and feel, graphs, charts, and other eye candy stuff. Just really make it fun and pop. It feels like the time is coming. As a funny or silly side note, John and I were talking about how we have been virtually hiding for years, building, beefing things up, and doing tons of prep work. It's time to flip the switch and start showing what we can do. Hopefully all the prep will pay off and we can stay ahead of the curve (demand and scaling efforts).

Cory and Shari O. jumped on and we went over some payroll questions and strategy. Touching base on where we are heading. Certain clients require a lot of our time and absorb whatever we will give them. We have a client that has latched onto Cory and Shari O. and literally contacts them almost daily. It's way beyond tech support. It's full-on training. The two ladies were talking about plans and how to break that cycle and/or have them pay for training.

Working on the Beaver Mountain custom horizontal time view (the original one). They requested a rollover/hover type tool tip to show more info without taking up any space on the horizontal time view page. I started into it and adding title/captions, student counts, and instructor counts. Created a new code branch to track the new changes.

Eric and I working on wave 3 of the gift cards project. We broke a huge project down into 3 smaller waves to help relieve the dependencies that were built into the project. Lot of application-level stuff, session stuff, and cached server objects and views. Testing and reviewing code. We had to fix some merge conflicts. This branch (the new code) was started months and months ago. That sometimes makes for a number of merge conflicts. We also spent some time picking up missed files and rebuilding the needed assets. We had had some code repository issues with this branch. Good work session.

Back on the Beaver Mountain horizontal time view and adding in custom tool tips with captions and lesson counts. Finished up the top part for unassigned lessons.

Alan joined and was asking about parts and item photos. He may make some tweaks to that part of the system. He is working on the global item catalog and being able to flip default thumbnails and images. We were going to watch a demo from Alan on some of his production and manufacturing stuff. Eric popped in and we got pulled away and had to work on some small errors. All of the other guys bailed out over to Zoom and Alan gave his demo there.

Eric and I spent a couple of hours and tried to make some fixes. Small tweaks to the payment structure fix. Learning and figuring things out. As we keep going, we will end up circling back around and making it more efficient. We will keep refactoring things as we go. As part of this process, we kept finding small one-off's and custom code. Also, some of that stuff (custom code) is hard to test. One of our goals is to push as much as possible to data driven vs code driven changes. It takes the whole village to make it happen.

Shari O. and I doing some scheduling. We recorded it and will give it to a client for review. Most of the time was spent going over new setup of reoccurring online booking and scheduling. Small code changes. Testing and then we switched over to talking about yearend reports and 1099's. Small work session.

Beaver Mountain custom tool tips for their horizontal time view page. Lots of prep work and reading over older code.

Bryan and I were talking about helping to create default websites for our clients. Some of them don't have anything, as far as a website or web presence. After our discussion on building out simple websites, I was pitching a full package with special events, merchant processing (credit card stuff), online booking, registration, paperwork, the whole nine yards. I would really like to help pitch and sell our services, possibly even as a plug-in of sorts. Say somebody did a WordPress site or a Weebly site, it would be so cool if they could tie into some of the adilas functionality as a plug-in of sorts. Just an idea, but I think that it has some potential.

We pushed up some code for some of the changes that Bryan is making for date formatting and the date-picker code.

This is the Element of Time for 

global_parent_attribute_updates.cfm

Going over post-it notes and recording entries into the developer's notebook.