Four of us on the morning meeting. Steve and Eric were talking about the transition between full independent (able to serve anybody at any time) and independent under the main adilas wing or being part of the internal team (still independent but getting specific jobs passed your way - no time to just server other clients at will). Eric was expressing how it sometimes is hard with older legacy clients that were used to just reaching out directly to the developer to get things done. Now they have to go through the process and filter through the queue (virtual line). That is good, but it does add some strain on some of the older looser independent relationships.

There were lots of talks about 3rd party solutions. They are good and bad. At different times, we have needed the influx of revenue and paying work. At the same time, we have also spent countless hours working on their stuff when we could have been working on our stuff. Somewhat a mixed blessing. As of right now, we are trying to avoid as much outside 3rd party work as possible. We have a tons of different pieces and projects that are needed internally.

Lots of good talks about customer care and serving those willing to invest in what we are doing. Even now, we are happy to help those who are helping us push the ball forward. Having said that, we are not so keen to help those who force their way or wills upon us. No one likes that. Along those same lines, we also talked about some of the pains of doing one-off development work and efforts. That then rolled into talks about feelings and how those play into the mix. We want to help people but we also need to balance being business appropriate and acting as business professionals. Lots of tough adjustments. Far from perfect, but we are trying to adjust where needed.

Steve brought up an interesting point, we are seeing, at this time, a massive movement to create and manage a conglomeration of systems and software trying to integrate and mix together. That is an interesting movement. It is almost like they are seeing the need to become a platform or a full blown system, all the pieces in one. 

We also talked about hidden costs and what it really costs to do that. Some of these 3rd party solutions don't go very deep. They seem to need deeper waters to swim in, basically, they need a comprehensive system and something that goes end to end. As the conversation went on, we got into putting up barriers and establishing rules in order to play well together. Lots of our talks were dealing with how we want to play the game and interact with others. Interesting topics.

After everybody else left, Steve and I stayed on and worked on some code together. He has some custom JavaScript that he is trying to do for one of his pages. We then talked about some older legacy code and older 3rd party solutions that may need to be cleaned up. Some of that code still exists on certain pages, even though no one is using those solutions. We may need to do some internal page clean-up.

Shannon and I spent another session doing summary work on the ideas and responses from the questionaire about the adilas trust business idea. Lots of thoughts and ideas about the adilas jellyfish (octopus) type model. See attached.

Funny topic of conversation - We work a lot with wet paint - Something can happen and then minutes later (wet paint), we are pushing on it, pitching it, and building on it. We virtually work a lot with wet paint (no time to dry before we start using it). I thought that was kinda funny.

Emails and recording notes.

Great little session working through projects and details. Cory, Steve, and I working on adding details to projects that are already in the project queue.

Going over a URL (web address) bug with Bryan. It was fixed by changing some URL encoding. We then worked on the Hypur project together for a bit.

Working on some custom code to help export the Bear 100 mile race finish standings via CSV (comma separated values) file. I could have done it by hand, but I figured we would need it again later, so I built a small export tool.

10/2/2020: Gram controls for e-comm:

1)38th Medical EPC- corp 1296
2)Galena-Medical EPC- corp 1323
3)Elati-Rec Corp 1199

Recording notes from yesterday into the developer's notebook.

When I got on this morning, there were six of us on the meeting. We cycled through some stuff and then everybody filed off to work on their own projects. Steve and I were left alone and we worked on some custom JavaScript code together. Light training and chatting as we worked.

We talked about charging for high end or specialty tech support. We talked about calling it specialty services or something like that. This is when we have to get a developer or designer involved vs just a quick question or phone call. Basically, do we need one of the specialty workers or people? If yes, we need to charge for those meetings in order to cover their time.

We went through a number of projects, asking questions, taking notes, and filling in gaps. We talked about new settings and next steps for certain projects. The more we plan and do our prep work, the smoother the projects should go. We also setup some new plans and added milestones and checkpoints along the way. All of this is us getting better and better at project management. We are so grateful for Cory and her efforts. Steve, Cory, and I make a pretty good team on the project management side. Steve can sell it, dream it up, and pitch it. Cory helps things to keep going and doing follow-up, and I help with technical questions and ask questions about different pieces of the puzzle. It is working out great.

Looking at and talking about code that we added for auto generating customer loyalty points. It was good, but we had our first client who was asking questions about some of the auto adjustments to ACV (actual cash value in dollars) and points per transaction. Basically, a company had issued and redeemed numerous transactions at higher values and then switched point values. The new code, which is correct, auto adjusts things to make the ACV dollar amount match the points. Because of some of the older water under the bridge, we had a client who was questioning some of the math. We went through it and were very happy with the outcome. Basically, there was one auto adjusting entry and then everything else was perfectly in line and on target. Good stuff.

Talking with Steve about receivables and payables inside of adilas. Basic business stuff. Constant state of flux. After that, Steve and I were working on some more custom code together. We then got into some budget talks, possible options for selling percentages and even doing an internal family round for funding options. We talked about the adilas trust and ideas there.

As of 2/3/21: $4984

10/5/2020: Created for Charles billing for templates

See sub notes for more details.

10/5/2020: These most likely will have to wait until the new year but wanted to get them in the queue.

2/15/2021: dustin spent 50 hours on the OK test.

10/5/2020: Will need this by Feb 2021 (waiting on info to be posted on METRC website)

Had to do some money movement and pulled from our line of credit to help fund some of the payables and such. Emails and other small to do list stuff.

Meeting with some of the guys to go over new needs for the gun company and what they are calling templates. Basically, paperwork and processes that they need. Here is a link from Chuck with a couple quick concepts and ideas.

https://xd.adobe.com/view/254b3d41-db95-4c9b-be8a-72db1c717c72-7018/?fullscreen - couple of pages for concepting flow

Other notes may be found by looking here - look at the sub notes on this other entry.

Working with the Euflora team. They sent an email with a small tick list of items. We then got on a GoToMeeting session and spent a good half an hour going over things. Some of what they wanted was things like... missing sub attributes (it ended up just being a setting), problem with API sockets (ended up being a subdomain thing - small fix), and and extended data dump (extension of the printable inventory list plus a bunch of new columns from other tables). This half an hour needs to be billed out.

After the meeting, Steve and I got back on the meeting to talk about options. We talked about adilas as a companion software package for any business and how we could be the whole thing (full business system and platform) or just a great sidekick. We talked about the options of being that flexible sidekick type package. Kinda fun. We also talked about if we sell some percentages, we need to pass on the taxes to the buyers. Taxes are at 20% (15% federal and 5% state). That is a pretty hefty fee.

On a meeting with Molly and Bryan. They were going over options, bug fixes, and trouble shooting client needs. We talked about getting our internal tech support system and workers to be more responsive and quick. We also talked about passing some of those upgrades on to our clients for a price. It just takes more money to play at the higher and higher levels. Light talks about other possible up sales.

After the meeting. I got an email and had to setup a new adilas meeting room on GoToMeeting. One of our guys accidently deleted our reoccurring meeting for GoToMeeting. No harm, we just had to setup another room with a new id.

The meeting started off with Steve, Danny, and Sean talking about custom gram trackers for the shopping cart. After that died down, Steve and I worked on some custom code together for a project that Steve is working on. Small chats about this and that as we were building the new logic for transfer invoices, new PO's, and passing data to Metrc (state compliance system).

Danny had a couple of gun range users on a call. We had a number of guys on the call. We had Steve, Brandon, Chuck, Danny, and Sean. These are some of the notes from the meeting. Danny had the couple on speaker phone and the rest of use were on the GoToMeeting session.

- They bought the gun range from a client who had 5 years of data.

- The whole adilas system is built on a web or web page type format.

- Some things that they would like is: sell a gun, add a member, schedule a lesson.

- They do use payroll - but they need a split rate for their employees

- They are looking for industry specific forms

- They need reoccurring invoicing - we have this - and they have multiple merchant accounts

- Text and form fields vs a simplified work flow

- They used to use adilas to help with waivers but it seemed to be a bottle neck

- Lots of typing. They want to use a driver license scan.

- In the sales process, it asks for the driver license and that should already be in the customer record

- They can tell that adilas has a powerful database backend, but they are looking for a simple work flow - aka a big button to do a task

- It would be nice if things were tracked from the manufacture

- On there inventory, they are running full vendor specific stuff where they could be using a more generic inventory

- They have a lot of paperwork that need to be online.

- They need lane use and scheduling.

- They feel like they have a number of different businesses running all under one roof. Retail sales, gun range, lessons, plus normal business stuff.

- They do like having all of the reports and data, but feel that most of it too complicated.

- They would like to have different modules that would be easy to turn on/off and hide/show those pieces as needed.

- They may be missing some training - a bunch of the pieces that they need are there but they may be missing some training.

- On payroll - they really need some split rates. They have to setup different departments and then they don't pull together to calculate overtime correctly due to the different rates.

- Training, training, training. They are making complaints that totally exist but they don't know how to use them.

- On the bottom of the calendar... they like the next month, last month buttons but they only go to the physical next or previous month. They want it to be fully go as far as needed.

- Pricing - They have seen big prices like $14K or $500/month.

- Lots of the ranges have tried tons of different software systems. Nobody seems super happy with their full products.

- There were some complaints about having to do things one way and then add that info into adilas after the fact. They would love to see things more streamlined.

- Go to the Las Vegas trade show in June - they saw 6+ vendors pitching their products. The show is huge.

- They would like built in online scheduling, directly from their website, with full merchant processing. All doable, but not out of the box currently.

- There are only about 20 main distributors in the gun market. They, the distributor, seem to want to share their product catalogs and inventory lists.

- They would love to get info from the distributor vs having to enter their own info for every gun. Lots of different makes, models, and small tweaks to what each gun has.

- They have 8 lanes. They had to close 3 due to Covid-19. That creates a huge wait and higher pressure. They really want online booking for their lanes.

- Each business needs stuff catered to their specific business model and industry. We are very general and it works, but they are really looking for an industry specific solution.

- We keep hearing this... training and training - they were talking about problems between splitting an invoice between a credit card and cash. That is built-in, but they don't know how to use it. As a side note, some of that training and lack of training deals with a breakdown on the communication channels.

- Steve jumped in and said that we are committed to making it easier and more user friendly. We would like to service specific industries and thus being willing to work directly with end users and persons who are in the know for their industry.

- Things keep changing - things that they want, keep being developed but not being communicated back to them.

- On the reoccurring billing, they want the full thing. The invoice, the payment, the full processing, the whole nine yards. They kept talking about similar to a guy membership where it auto charges, auto bills, auto everything. Once again, the full cycle. We have all of the pieces, but there is a small part of that process that is still manual.

- They do like the membership end date functionality that shows up in red if they are expired.

- They have membership cards and want to be able to scan those and make sure that it pulls up the correct customer. They said that it used to work, but now it doesn't work. We would have to see what it scans and then make sure that it coded into the system.

- They had major pain one day when adilas was down... they had to handwrite 250 tickets. That was terrible. They really need good up time.

- They have a new range software package. It took the other company about 2 months to get it all installed and configured.

- The amount of time is limited that they have to instruct and help their customers. They want it almost so intuitive that no instruction is needed.

- Trade-ins, verbage, and making things simpler. The naming convention doesn't tell them what it will do. Some examples are: system maintenance, system assets, elements of time, etc. They want it to say, sell a gun, add a member, schedule a lesson.

- Less typing - more scanning - more clicking (within reason). Minimal on the typing. Just for fun... they have to type in crazy names with screens, masks on, and other crazy Covid-19 type stuff. It just makes it tough.

- On memberships... They love that all of the carts are tied to customers and we track all of that data. However, if they sell a membership, they want it to auto add and update the correct fields and values.

- They seem to skip the news and updates - they are on a mission doing the task at hand.

- They like the high-tech toys.

- Getting the developers to get some immersion into the real business model and the style of what is going on. Aka - what is really going on and how should it flow in real life? Getting the developers out in the field more (exposure to the end user side of the puzzle). They called it immersion. Finding and solving the pain points.

- We may come out and visit their shop and their range. That would really help all parties involved. Steve, Danny, Chuck are all volunteering.

- Some of the other software platforms aren't deep enough or don't do enough. They can see how if we change the frontend of adilas, it could really handle most of the needs.

- Guns are a fear-based business. News, elections, crazy times, all of those things drive sales. Their industry is really pyrenoid on giving out personal info - the government may come after them.

- Being able to scale... sure we can do it once or a couple of times, but can we do this for hundreds and hundreds per day.

- Quick fixes like being able to scan the driver license or enter a phone number from a 10-key, etc. Things that already exist but need to be surfaced better. Steve was mentioning a new gun range homepage and/or interface.

- Let's keep the communication lines open. Reach out to Danny. danny@adilas.biz

- Steve was talking about both form and function. Let's get it going. He was talking about even some quick changes like a new custom homepage for gun ranges. Task based buttons and quick access to underlying functionality. Add some quick options that they will use.

Shannon and I were doing some research and summaries on the adilas jellyfish model. We also explored some options about using an octopus vs a jellyfish. This was a suggestion from Danny Shuford in some of his comments that we were summarizing. Here are some of our findings:

Defining an octopus - multiple legs, it can squeeze, run, hide, change shape - expand, it can be very rigid, it is classically a predator. Normally when you think of an octopus you think of something much bigger - or potentially something that has much bigger parts and pieces. Some thoughts and images are potentially frightening and scary, especially when thinking of large octopuses (movie-level characteristics). They are also nimble and quick, not always the aggressors, flexible, able to camouflage, blend in, be hidden or subtle, or can be right out in front. We kept coming back to some preconceived notions and/or expectations. It has a central head or body and has arms or other appendages (options) - We could potentially explain those other options if needed. Maybe people hear jellyfish and feel like that is too passive but maybe they hear octopus and think too aggressive or potentially dangerous. Octopus may be harder to draw if trying to explain a business model or architecture or structure. 

Overall as we discussed it further, we determined that the jellyfish model seems to be a better fit. It conveys the idea we are trying to share. It isn’t as intense or intimidating. It is really just a teaching tool to help convey a concept.

Steve and I got on a GoToMeeting session to talk about options. We spent some time going over ideas and drawings for the adilas trust and how we could set that up. I have another Word document with a bunch of notes. Steve and I met for a good hour, talking and going over ideas and options.

Calvin called and we chatted for a bit. Calvin was pitching a proposal to work on the adilas label builder and getting that whole product web ready and transferred over to adilas vs being custom Windows based software that he developed. We talked about budgets, timelines, expectations, and other options. One of the things that Calvin was pitching was outsourcing a JavaScript grid layout engine. If we got that built, we could use that same layout engine to configure custom labels, custom invoices, customer receipts, check printing, PDF forms, and other layout type projects. Good stuff.

Here are a couple of other quick side notes from the conversation with Calvin. We talked about doing focused sprints vs big long drawn out projects. One, the developer's lose momentum and two, sometimes funding runs out. Time and resources, those are major pieces to the puzzle. Plus, this is the major killer, transitions... you lose so much in the start/stop, start/stop process. We gain some advantages as we do small pushes to minimize the length of the project and the number of transitions that will happen. We already knew this, but sometimes it is a good reminder on efficiencies and flow.

After the other meeting and phone calls, I merged in some code for Steve on branch that he was working on.

Meeting with Spencer and Steve going over Spencer's short and sweet custom shopping cart. He has it broken down into 3 sections right now. They are: 1. Customer stuff, 2. Select a product, and 3. Confirm and process. The whole project is web and mobile responsive using Spencer's custom framework. We went over a JSON nav configuration option and some of the other cool accordion (sections that expand and contract like an accordion) features of the new custom cart. We haven't deployed it yet, but it is getting close.

We also talked about a second or third round where we would look at adding payment and full checkout options to his current AJAX/JQuery one-pager cart. that would be really cool. As a funny side note, once you leave Spencer's more modern cart, you currently have to step back in time to use the full checkout, credit card payment page, and review cart page. Major contrast when switching between the new short and sweet cart and the older finalize and checkout process. Kinda funny. Nothing that can't be fixed, it just takes time and resources. We will definitely circle back around once it is launched and do more tweaks and other rounds on this new cart.

After the meeting with Spencer, Steve and I stayed on the meeting and kept chatting and talking about business options.

Test and merge new update for the flex attributes from Bryan. Great job. That project is live and being tested by a select group of clients and users. We know it has a lot more that is needed, but it is coming around.

Phone call with Shari O. to go over servers, users, and accounts receivable stuff.

Working on some custom code for Euflora. They needed an expanded data export or data dump. The export included parent items (parts or general inventory), quantities, parent attributes, photo/image paths, and web long descriptions. Each one of those things is from different tables and we needed the whole things wrapped up in one data dump or data export. Interesting. This time was billable and hours were sent to Cory for billing.

Emails, catch-up, and small to do list stuff. Pretty quite morning.

We got together and chatted about projects. Chuck was on an earlier meeting today with a client. He reported on that and needs of the client. They have lots of paperwork and need to track certain processes. We talked about two other projects that Chuck is working on. We are almost finished with the adilas docs project that shows coding conventions, style guides, and common processes and procedures that we do inside of adilas. The other project that he is working on right now is the update on the news and updates and WordPress stuff. He, Wayne, and I will be getting things pushed up and scheduled here in the next couple of days to finish up that project.

The last thing we talked about was Chuck helping Steve, Sean, and Danny with the sales and marketing stuff. Lots of options there and we are making progress. Good stuff.

After our meeting, I went back to recording notes from earlier in the week. Kinda behind on recording the other meeting notes.

Recording notes, emails, and paying bills.

Recording notes from the past couple of days.

Met with Bryan to go over ideas and options for getting a latitude and longitude for some 3rd party API socket calls. We did some light research and checked some of the files that we have. We added that feature at one point back in 2016 and then removed it about a week later. I remember we had people complain. Looking up google API stuff and older references in our code bank.

Emails and checking out code on servers. We had a report of an error, but it looks like some of the code was rolled back to a prior date. The real code should have fixed the problem, but it looks like the auto sync code with master was disabled and/or altered somehow.

Paying bills and recording expenses.

Steve and Sean going over sales stuff. They were talking about the Apple Model and how someone greats you when you come in and then you could be helped by someone else by going through some sort of simple queue type process. Danny checked in. After that, we helped Steve with his local environment. Both Dustin and John Maestas checked in. Some small intros were made and what not. John is Dustin's friend. John is just getting going with us on some development projects.

They then started to talk about different versions and generations, for example: generation 3 or generation 4, etc. Dustin has been responsible for some of the new versions out in cultivation land and what not. It is fun to see the progress and the changes over time.

After these guys left, we went into a sub meeting of sorts and worked through some things. Sometimes, our clients, want industry specific processes that are fully built out and completely industry specific (super narrow focus and/or paths to choose). As we were talking, we ended up talking about drawing out the processes, pretending to do simulations and different use cases. We also talked about being proactive vs reactive  and/or passive. We really want to help our users out and then let them help us refine it vs waiting completely on the client's input. Sometimes they don't know what is possible, they tend to stick with what is set in front of them.

Often, our clients don't realize that we can customize it (tweak or refine the processes). That seems really trivial to us, but thinking in custom code (what is possible) is a skill. The deeper we go, the more we are seeing that all of our layouts need to be fully customized or customizable and based on settings. That sounds awesome, but that adds a whole other level of complexity. Small and skinny yet totally data driven.

We need to get back to the limited flex grid pages. Make it slick and skinny. We are already using it for Beaver Mountain, but want to make it good to go for all of our clients. This would be so cool, but it will take some more work. Having said that, we really really want to get back to this. The limited flex grid is a way of setting up custom fields and dynamically populating a really small add/edit form that only shows what they want or need vs all of the possible fields.

As a side note, the flex grid table has over 40+ different fields that we can and do use for different things. Imagine is you could setup a simple form that only had 5-6 of those custom values. It then becomes really simple vs too big or too overwhelming. The goal is user defined simplicity, yet still being fully connected and powerful. If needed, we could always flip over to a full or more extended mode if some other field or value is needed. It is almost like layering the interface and the data. Super simple on the surface, but deeper or more rich as needed (layering).

We got off into communications and dealing with outbound messages, communication options, and getting people connected to the correct sub or special pages (combo of communication and navigation options).

Next, we got talking about building out custom skins (wrappers of the logic and data) and how that plays into the mix. We did some light pitching and talking about different packaging and marketing options. Some of the subjects that we chatted about were things like ski area, gun shooting lanes, classes, and then working with people in those industries to build and test out products and services. Basically, have or get a dream, build it, and then use people who are in that industry to test and give feedback on interface, navigation, user experience, flow, and functionality requirements.

On the marketing and sales side, if we have someone who is using our product in a specific industry, that testimonial does tons for helping others in that industry to be willing to jump on board. We have also found that if we find someone who is in an industry and they are willing to help, provide feedback, beta test, and give ideas... that is like gold and helps the process get smoother and smoother. It is amazing how a little bit of icing makes the cake look that much better.

Expanding into other horizons, we really want to do this. Our conversation circled back around to the dream it up, push on it, and we'll help you wire that up type model. You dream it up, we'll wire it up. Making things simple, powerful, and easy. Awesome words/phrases, harder to do, but possible. We also talked about opening our eyes and minds to what is possible. Being able to see and/or imagine is sometimes harder than you think. Once we can see it, the next phase is letting our users and clients catch that vision. Once you can transfer the vision, others start helping to beat that drum and making it happen. Share the vision!

As we look at the MVP (minimal viable product or minimal viable plan) type approach, we get pulled out of the dream land and back into - what are the next step or steps that need to happen. You can't lose sight of the goal, but you also have to make it work (along the way) vs just the dream at the end of the tunnel. Having said that... one thing that has been very successful for us is... get them hooked on one aspect and then letting them go and start dreaming. They'll start putting the pieces together. You just have to get that process started. Sometimes with an MVP type approach and then let it grow from there.

Here are a couple of other topics that were discussed: saved reports and connecting to them, other future projects (fracture), reviewing topics listed above, automated and predictive logic, aggregates and quick starts, templates, build your own processes (data assembly line and flex bubbles or flex pods), and other topics. Good meeting. Lots of new ideas and also firming up some of the older ones that keep circling around.

Working with Shannon and summarizing data from a questionnaire dealing with company structure and where to focus. See attached for our work and how things are shaping up.

As I was giving a demo to some of the internal guys (small sales pitch on vision and options), I was showing what we did for Beaver Mountain and their horizontal time view (time across the top and their ski lesson instructors down the left side with their time periods marked out for when they are booked). I thought that it would be cool to let the users setup those (or similar) horizontal templates using settings. They could name the template, create new, assign filter or search criteria, able to edit or delete, search, view, and even get their own URL or address (similar to how we do saved reports). I thought that would be super cool. Allow for time blocks to be set across the top - start/end times, block size (10 mins, 15 mins, 30 mins, hours, etc.), and what to show down the left side. This could be people, users, customers, vendors, locations, items, etc.

Imagine a template that you could setup what it looked like (settings), what it pulled (settings), and how it displays that data (layout based on settings for persons, places, or things). That would be so cool. Basically, what we created for Beaver Mountain Ski School, but configurable.

Here are some small ideas (just scratching the surface): Instructors and lessons that are booked per instructor, classes being taught per room, shooting ranges and lane assignments and booked slots, employee work schedules, light rentals, appointments, multiple person schedules (each with a different URL to access a person at a time or a different URL to see all together, if needed), daily task lists, etc., etc.

Filters could be time templates, colors, phases, action statuses (started, stopped, pending, completed, etc.), assigned to (person, place or things), or whatever.

The Beaver Mountain horizontal view deals with conflicts, drill-downs to the underlying events (elements of time), and also allows for quick adding based on values within the horizontal view. For example: Say you have an instructor and they have an opening from 2-4 pm. If you click on the "+" sign in that section, it would already know the date, the person, the time block, and other criteria. You then take that info and auto fill out the form so it becomes super easy to add to the horizontal grid based on quick steps. All kinds of stuff could be passed through to the next (create new) page. Anyways, just wanted to record this idea and jot down some notes.

- New note added on 7/19/21

What about vertical time views (visual blocking out the time slots). We already have a time slot report which shows things going down, and it's pretty cool. It could be built out even better and show things in blocks. Currently, it just shows the span but not a visual block yet. If we could just take it to the next level, it would be pretty cool. Just ideas here, what about anything that could fit in the same vertical block, great. If there is a conflict or double booking, we add another vertical column. The horizontal time view adds extra rows. The vertical time view could add extra columns (very similar).

Great meeting with Steve. We were talking about the adilas structure, company, percentages, and options for the adilas trust. Brandon has a Word document on his laptop with some notes that were recorded.

Cory and I spent 2 hours working on the Flash to HTML5 project. We went through each of the main Flash widgets and uploaded authoring files, extracted the ActionScript code for each file, and recorded other notes for each of the 3 main projects. They are: the adilas check write app, the barcode generator app, and the my cart favorite buttons (mini flash buttons for point of sale systems). Great progress, trying to prep things for a developer to help us out with the conversion process and transforming the older Flash apps into more modern HTML5 type apps.

Emails and merging in some code for Danny.

Checking in with the guys. When I got in, Steve was chatting with a couple of them already. Both Dustin and Danny had some small questions for me and then Steve and Sean were working on some stuff. I did some emails and then after that, Steve and I chatted a bit about shares, percentages, ideas, and options. We also talked about increasing our prices for services that are needed.

Going over projects. The first one is a project to help secure customer photo uploads. Currently, things are protected by valid login, permission checks, and all kinds of internal code. We have a client that is trying to pull some of that secure data outside via ecommerce and different API sockets. We went over a new project and talked about adding some security to those customer photo uploads. We also went over a bunch of other projects including some new and old 3rd party solutions, API sockets, and API documentation.

We also chatted about charging for 3rd party services, custom error messages, cultivation, realms and worlds (where are things happening - internal, external, certain sections within sections, etc.), who fixes buds, and how can we speed things up and automate our own internal error handling. We may need to gather more information from our users or automate that flow of information. We could then setup our own ticketing solution where we respond and acknowledge a support request, setup the new ticket, and get it assigned out to the correct department and/or person.

There were also some conversations about some of the 3rd parties virtually selling vaporware and how that affects us. We want to keep improving our internal and native offerings. However, sometimes we need the options that an outside 3rd party brings. We also briefly talked about internal communication channels and how can we let our users know what exists and is available natively (already built in and part of the monthly service fee for the platform). That has been a big challenge for us.

Danny and I were going to talk about a new project, but he was still working on some custom labels for a company. Small discussion and then he bailed out. We will hit the new project later on. After that, Eric popped in and had some quick questions. Small open forum type session. When I wasn't helping, I was recording notes.

Paying bills and emails.

Cory and I got on a GoToMeeting session and did some planning, outlining, and then recording a video for a Flash project. We have three Flash projects that we are trying to convert to HTML5 (newer format) by the end of the year. We did some outlining and videos for two of them. We ran out of time and the developer who is going to be working on the projects joined us. We scheduled more time to get back to this process.

Spencer joined us (Cory and I) and we went over a high level overview of the Flash to HTML5 projects. We briefly showed Spencer some of the current Flash apps or widgets and what they do. We also got a little bit techy and talked code, options, and direction. Towards the end of the call, we setup a number of other meetings to keep this project on track.

Paying bills and scanning invoices and receipts.

Steve and I were on, working and talking. We got a bug report that took over and hour to find. It was a random cart problem, but it wasn't introduced from the cart itself. We found that if someone had a cart going, and they just used the cart, no problem. However, if they had a cart going and then updated their personal settings and didn't have a default cart type, it could flip the cart type back to unknown or undefined. It only happened if you did a certain sequence, so we added some code to not flip it to unknown if no default cart types are specified. It sounds weird, but it took a while to figure out what was going on. One of those sequence things.

As a side note, this setting described above, is used on hundreds of other pages to control the checkout process for gram controls and invoicing. That made it a bit more challenging.

Danny joined and even hung out for a bit, but we were busy tracking down that bug. So we rescheduled.

Shannon and I got going on our meeting talking about the bug fix that we figured out this morning. I was explaining to Shannon what was going on. While we were talking about processes, Shannon then had a question about the bulk verify for expense/receipts and payments (checks and other bank stuff). We spent the hour looking into her questions and making some small changes to help her out. This mornings meetings felt like a small debugging session vs new work being done. Kinda funny. Keep moving forward.

Emails and code review for Eric.

Working on new logic to back out balance sheet entries if voiding out expense/receipts or deposits that have a reference to a balance sheet item. This is project #1725 in adilas: When you void an E/R or a deposit that is allocated as BS, it should remove it from the balance sheet (just the sub or details of that transaction - not the whole thing).

John and I met up and went over his data table project. We did some code review and got it all pushed up live. This was his first live project. Good stuff.

Working on the custom data import for Euflora. It was a multi column CSV file with ties out to parent attributes and web long descriptions for ecommerce. These are not normal fields that we do bulk updates on. Building the CSV upload page with the custom logic. Most of this session was spent on the parent attributes and matching things up. As we parsed through the data, we had to dynamically do either new inserts or updates on existing data. This needs to be billed out to the client.

Early start this morning. We are going to be doing some maintenance on the news and updates pages. Chuck is installing some new WordPress themes and changes. Wayne and I are helping with different pieces. I spent the first little bit today working on a news and updates bypass so that Chuck wouldn't have too much traffic as he is making updates and changes.

After that, I spent a good couple of hours working on a custom data upload for a company. The upload was for their parts and item inventory. The upload did a special loop and check for certain parent attributes and web long descriptions. All of these pieces are used outside in ecommerce. The company is using an outside 3rd party to show their inventory and then using adilas API sockets to pass data back and forth. Kinda of a custom wire job. Anyways, about 2.25 hours working on the new CSV data upload options and logic. Very custom with lots of error handling and clean-up built in.

Chuck and I jumped on a GoToMeeting session. I was having audio issues with my computer. We ended up on a phone call and using GoToMeeting to show screens. Chuck is working on some news and update WordPress updates today. He also reported on some custom registration stuff for a client. We will try to wire those new pages up tomorrow. Somewhat of a quick touch base and report.

After that, I spent the rest of the time working on my audio connections for GoToMeeting.

Working on laptop, windows updates, recording notes, small bug fix, and emails.

10/14/20: Eric is doing this

Danny and I worked on his local development environment. We had to re-enable some sub inventory attributes. After that, we went over a basic outline for the new projects that he will be working on. We did some small drawings and a general overview. I think that helped get us on the same page together.

Emails, news and updates stuff, and recording notes. On the phone with Chuck going over next steps on the WordPress news and update changes.

Danny, Sean, and Steve were on the meeting when I joined this morning. They were talking and touching base on things. I was doing emails and trying to get caught up with small to do list stuff. Here are a few notes that I gleaned just from listening.

- Keep building and connecting the pieces - take the next logical step.

- The deeper we go, the more we are seeing elements of time being an underlying foundation or under weaving of almost everything we are doing. Maybe keep exposing that and building towards that. We've always know it was there (foundation of events and objects over time) but maybe keep pushing that connection and foundation piece.

- Have the attitude, let's figure it out. We keep getting hit with more and more questions, what if's, wouldn't it be cool if's... etc. Well, let's figure it out!

- If you find the pain, then look at the tools that you have, and build a solution to fit.

After that, we changed course and started to talk about a project with a gun manufacture. They need to track gun registrations and RMA (return merchandise authorization) stuff. We invited Chuck on to the meeting and took a bunch of great notes. See attached.

- In this meeting, there was a lot of talk about the data assembly line concepts and how it would be super cool if we could do the limited flex grid type approach for flex grid as well as elements of time. Imagine a small and simple form with only a couple of key values, you submit it, and the next time you need to do something (say another phase or process), the small and simple form could keep track of where you are at and only show you the new limited fields that you needed. That would be so cool. Almost a generic process or phase builder. You pick what you need at what phase and then as you walk through the phase, you only get presented what you really need at that time. That concept may be worth exploring more. Think data assembly line for data, based on settings, templates, phases, and underlying processes (tasks to do and/or record). Simple, step-by-step processes with a powerful and dynamic backend so that the frontend looks super simple (trained monkey could do it - in theory). That would be pretty cool.

Shannon and I had a good work session. We are still working on summarizing all of the responses from a questionnaire that we put out a couple of months ago. Pretty common for us (things take time). Anyways, the topics today were products and services that we want to focus on and should we seek outside funding or try to stay with internal funding? Great questions. See attached for our progress.

10/15/2020: This is a custom report that Bryan did for Elevele. They need it to be updated to map to sub expiration date instead of some parent date. it is in the custom folder, inventory 

10/15/2020: Another api.

Emails and recording notes from paper and post-it notes.

Danny has two new projects. They are slightly different, but close enough to count as one bigger project. We went over some of the notes we had for the project and lined things out a bit. We made some new plans, took some notes, and started to get into the coding side of things. These projects are dealing with four new corp-wide settings dealing with age verification.

Working through the project queue with Steve and Cory. We went over a number of projects. We added notes, and lots of filling in details. We still aren't over the top on documentation, but we are getting better. We are catching the documentation, but it is currently in a brainstorming type format vs a logical read or easy to follow presentation. Good work session.

John and I got on a meeting. We have a new corp-wide setting that is needed. This corp-wide setting is dealing with sub barcodes and what values are added as a prefix or frontend value to the barcodes. The main meat of the barcode is an auto id that matches the primary key id number for the record. The precursor or prefix is a string of characters that help us look for the correct barcodes. We did some planning and then right into code when we were ready. We started with the new database script that was needed to get the project started.

Spencer joined the meeting and passed me a couple of existing JavaScript libraries for JS grids (canvas layout matrix) and for JS barcodes. See below for the links. This is dealing with our Flash to HTML5 projects.

https://lindell.me/JsBarcode/ - JavaScript barcode options

https://projects.calebevans.me/jcanvas/ - JS Canvas or grid layout options

After we finished up, Cory and I jumped on and looked at a small bug that needed fixing.

Steve and I spent an hour talking about ideas, key reps, key consultants, what they are doing that we like, what we could work together on and where things are headed. I was taking some notes on a separate Word document. Good stuff.

From Steve - "flex bubble" or "flex bubbles" - concepts of mini steps (bubbles or pods) to make a whole (aka processes) - parts of the data assembly line concepts - dynamic settings and user (data) driven settings. Help them build their own phases and processes - super simple. Think of a process where you are able to say... by the time we are done, I want this, and this, and that... Then setup the steps or phases to get that done. All through settings and basically a simple point and click build process to format and formulate the correct steps in the process. That would be so cool.

Keep finding people who want to play! Lots of great talks about who we are looking for and what piece they bring to the puzzle. Fun conversation.

1/25/24: We are thinking it may be best to do csv files, as Biotrak is impossible to work with.

10/16/2020: Created project to keep this on our radar.

1/26/24: Latest is we may just go with csv updloads

12/7/22 added New York to Biotrack dropdown. ******** Need to add New York API endpoint to BioTrackAPI.cfc. It is currently pointed to Arkansas *****

11/9/22 got variable info from Alan and checked, fixed bugs and pushed with Brandon.  Edits on the following pages:

BioTrackApi.cfc, biotrack_api_settings.cfm, and biotrack_api_settings_action.cfm

10/16/2020: Added this to the queue to keep on our radar.

New API Documentation - https://api.licensee.fl.biotr.ac/documentation/index.html

Emails, recording notes, and getting updates from the guys who checked in on the meeting.

Cory was going through her list with Steve and I. We went over a number of projects and light updates on certain things. One thing of notice, we are seeing that we need to route emails and communications through the right/correct channels. We will get an email and 4 or more of us get it. We all read it and then don't know who is going to be responding/working on whatever is needed. Not very efficient. We are getting better, but it still needs some work.

Due to a backlog for ordering things... we have a new request to help with an on order project for serialized stock/units (big ticket items). Problems in the normal supply chain for some of our trailer dealers and firearm dealers. Interesting.

John and I are cruising through his project. We went over our database update for a new corp-wide setting and then started into building out the add/edit process for the new sub barcode prefix project. Small work session.

Bryan and I jumped on and talked about his eXPO payment solution project that he is working on. Most of our projects dealing with 3rd party payment solutions have been done on the invoice and shopping cart side of things. This particular payment solution already has the invoice side of things. The new project is on the expense/receipt or outbound money side of things (paying for things). We went over some code and looked into Alan's new objects, scripts, and DAO's and services. Alan is revamping tons of the existing models with newer code sets. We also did some checking on some JSON formatting coming back from a 3rd party API socket response from a vendor. They were sending back non compliant JSON responses. We'll have to get with them to get that resolved.

After Bryan left, I spent the rest of the time doing bills and other odds and ends.

Chuck and I got on a meeting and worked on first round wire-up stuff for the SAR USA firearms registration page. He had already prepped the main form page. We are passing it on to a ColdFusion page (logic and validation) and then into the database. Working with Chuck on the process.

Eric and I jumped on and were looking at some random entries on the Euflora server for customer loyalty points. Everything that we could see was pointing to good code and it doing what we wanted it to do (change over to ACV on loyalty points - actual cash value). We finally figured out that there was about a one week period where the servers were using the older code vs the newer code. We ran an update, that already existed, and it fixed the problem. It took us awhile to figure things out. Imagine a current model that works but a known window (say a week, a couple weeks in the past) where things were not correct. Hard to find that kind of stuff. Eventually, we recognized the pattern of the older code and that is what tipped us off to the possible problem. All should be good to go, we only had this problem on one server. That makes it tough to debug and figure things out. We were both pretty stoked once we figured it out and got it back on track.

Phone calls and emails. Clean-up from the day.

Bryan, Kelly, and a client got on a Zoom session to launch and test some code for the client after hours. We pushed up a couple of files and Kelly and Bryan will work on the other changes that are needed tomorrow.

Tech support, emails, and recording notes.

On the morning meeting. Steve and the others were talking about sales and such. I got put on to a small bug fix with duplicate customers out in ecommerce land. Working through a small fix on the add new customer stuff.

Cory and I were going over some notes on a project. Our goal was to create a short video to give to the developer who will be assigned to the project. We ended up spending the whole time jotting down notes, drawing, and figuring things out. By the time we were done, we had a small plan with both new corp-wide settings and new individual record settings for show/hiding things out on the web in ecommerce. Some of the settings were dealing with show/hide values, required yes/no, and allow edits yes/no. Good stuff.

If you look deep enough, you will see that the entire foundation of adilas is built on a foundation of permissions and settings. That seems to be at the very root of almost everything that we are doing.

Shannon and I were summarizing input and talking about funding and funding options. See attached for where we are on the adilas trust questionnaire summaries. We also got into some good discussions on where we are, what we've been doing, and even some plans for future funding opportunities.

Working through his new project on the a new sub barcode prefix setting. We finished up the add/edit form today. Tomorrow, we'll be on to the action page to help the user submit and make the changes stick in the database. Small training session.

Danny and I scripted a database update page. This was Danny's first database update script. We then did some light prep for what will be needed on the ecommerce settings page for his new settings.

As a fun side note, Danny and I talked about being willing to help push and code the WanderWays (camp adilas) project along. Lots of good and great potential there. Worth pushing forward on. That is awesome.

Fairly quite morning. Sean checked in and so did Cory. Sean showed me a bug with some custom ecommerce stuff. Cory wanted me to merge in some code for Steve as it is Steve's day off today. Merged and pushed up new code. Started looking into the bug that Sean let me know about.

Chuck and I did a two hour wire-up session on the gun/firearm stuff for Bill (a client). The main part of the session was training on database interactions and using ColdFusion cfc's and methods. Making progress.

Alan checked in part way through and showed me some new code for some sub invoice and sub quote functionality. It is crazy to see how everything keeps going deeper and deeper into subs. We also briefly talked about servers and security stuff.

Alan joined while Chuck and I were working. Quick check in and chatting about current and upcoming projects.

Emails and recording notes.

2:00 pm to 3:00 pm - Meeting with John M to work on his project. We have not launched it and pushed it live, the development of the project is completed. This is a new corp-wide setting to help control the prefix for the auto sub barcode values within sub inventory. The project included a new database update script, add/edit forms, validation, passing the data to the database, and then using the new setting when the keyword "auto" is used on sub inventory barcodes. Pretty cool. Also, John is doing great and really catching on. Good stuff.

Work session with Danny and I. We have 4 new ecommerce settings that are coming along. Today we were in adding the form controls to help with the adding and editing of the new settings. We also had to do some documentation and new help verbage stuff.

Recording notes and getting caught up. Also fixed a small bug out in ecommerce dealing with adding a new customer from the ecommerce land section and/or pages. Cory had me scheduled to work on the remove BSI item from voided deposits and expense/receipts, but I wasn't able to get to that during this time period.

Just Steve and I on the morning meeting this morning. The first part of it was just some catch-up and random to do list stuff. Towards the end, Steve and I were talking about shares, percentages, ideas, and options. We would like to setup the adilas trust and help give back to our guys and gals who have helped us build up to this point. Good stuff. Great conversations and making progress. Brandon has some notes on his local computer.

Work session with Chuck. We were working on the gun registration wire-up job for a client. This is where their customers go in and fill out an online form and we then suck that info into the database through a custom wire-up job. Most of the session today was error handling, and making decisions on what to do in certain scenarios and/or use cases. Lots of training while doing the project.

Danny and I were working on his project for four new ecommerce settings dealing with age verification and age prompts. We finished up the add/edit section today. Going through it bit by bit.

Recording notes and emails.

Part way through the session, we were notified that there was a bug and/or problem with stock/units. It ended up being that the stock/units were fine, the problem was the API socket call after the fact that was the problem. We had just put a version of a filtering software called cloud flare on the data 0 box. We were doing some super simple API socket calls and not using https (SSL - secure socket layer). No big deal, it was just a quick update. However, the cloud flare filtering software was blocking anything that was normal http (non secured traffic) and thus the problem. It took us awhile to figure it out and then to make all of the changes. I was on, Cory was on, Shari O. was involved, Wayne was involved, etc. It got pretty deep. We finally got it all figured out and okayed in the end but some rough waters for a bit.

Cory joined the GoToMeeting but we were deep in the middle of a server level fix. This meeting did not happen, but Cory was there listening and working in the background.

Spencer popped in and we did a quick recap. He is working but doesn't have anything to show right now on the Flash to HTML5 projects. Small report.

The rest of the time was spent cleaning up and getting things all sorted out.

A bunch of the guys and gals were on the meeting when I joined. Marisa, Sean, John M., Steve, and I were on there. Sean and Steve were talking about needs for the gun dealership. They need a cross between a stock/unit (serialized inventory) and a part or general inventory item (bulk or widget inventory). As they were talking, I jumped in and mentioned that we had a similar request back when we were working with Barry at GPS Autotrackers. He, Barry, wanted to be able to sell things in bulk, but still track things with specific data (say a serial number for each GPS unit). He wanted the invoice to be something simple like: Sold 400 GPS units for a certain amount. Then, somewhat hidden and/or off to the side, here are the 400 serial numbers that go along with that (extra details or extra information or data).

As we talked, we ended up pitching a couple of different ideas of how we could figure that out. Option one was just use normal stock/units (existing serialized inventory stuff). Option two was parent/child inventory with a single parent and tons of subs (existing). The third option was a parent item, a sub item with a certain number (quantity), and then hold any extra info in a special table that is setup to hold the extra details. In technical terms... a one-to-many-to-many or in basic terms a parent item, one or more sub item(s), with one or more extra detail(s) per sub. We did a number of drawings and ran through some verbal use cases and options. The option three stuff seemed to have the most potential.

We talked about an extra sub table that could hold things like: auto id, corp id, part id (parent), sub id (subs), special tracking number (serial number, vin, batch, rfid tag number, etc.). It would also have columns that we could connect it to things like a PO, an outbound invoice or quote, and maybe even a separate tie-in to a customer if needed. As a small side note, we were thinking somewhat of a mini flex grid type table (similar concept but smaller in scope).

We don't know what to call it, but there is already some prior entries and ideas called a mini unit (see other entries).  This is a cross between a stock/unit and an item or a part number.

Wayne joined the meeting and we switched gears into servers, hackers, and how to help protect ourselves. We've had some hackers circling around us this past weekend. All part of the game. Wayne is doing a great job and showed us what he is seeing using some of his tools, logs, and outside monitoring services. Good stuff and we are so grateful for his skills and help. Wayne was showing us things and Steve and I were asking questions. Some of the other guys were just listening in.

Danny had some time scheduled, but he was having Internet problems. No meeting took place, but he did text me to let me know.

Chuck joined at 11 and waited until around 11:30 am until we finished our other meeting and server security talks.

Once we got going, Chuck and I worked on a custom wire-up job that deals with adding a message page and custom validation to a simple form for doing a gun registration. We ended up getting rid of all of our prior validation and substituted it for our new custom tags and deeper validation routines. Good stuff and all part of the learning curve.

Emails, recording notes, and other odds ad ends.

Bryan and I got together and did a work session on a couple different projects. One of them was a recap on some menu boards, changing up the JSON storage, and making things smoother. We also spent some time and worked on complicated loops and sub loops on a sub inventory report that he was working on. Good work session.

Cory, Steve, and I were going over projects, settings, reports, exports, different developer strengths and needs, and ended up doing some small code tweaks and pushing up the changes. Somewhat of a working, planning, and implementing some changes - type of meeting.

Bryan coordinated a late night, after hours, code push for 2 corporations on the data 3 server. Kelly, Anita, Bryan, and I were on the call. We got things up and got the thumbs up from the client.

Met up with Shawn Curtis to setup some times to meet to do payroll stuff and update all of the new withholding settings for 2021.

Steve asked me to run some of the mini units ideas and options by Danny, as he missed out on our conversation the other day. We did lots of drawing, scenarios, and even some typing of what we were hoping to accomplish. Nice little brainstorming and planning session. This is kinda funny, but I was pitching the ideas on mini units like it was my current project. I kept defending certain ideas and concepts, yet nobody was defending an alternate point of view. I don't know why, but I felt like I was trying to pitch something that was being opposed and/or had a conflict. It turned out fine, just not sure why I was so motivated to get the ideas and concepts across. Kinda funny.

We ended up going into options for the mini units and how they could be tied into packages of packages (cases, boxes, crates, etc.), media/content options (specific paperwork per mini unit), and tons of options on flow for how those mini units would flow through the processes (data assembly line and flex bubble stuff). This ended up sending us on a tangent to talk about the order, invoice, fulfillment, and shipping processes. Lots of ideas about bringing things in, tracking and recording inventory, selling items internally, and also selling items externally or through ecommerce. Certain places have subs, sub processes, data entry, uploading documentation, gathering other info, etc. Each side of that story (receiving, stocking, selling, shipping, etc.) all have different needs dealing with the same mini unit or serialized items. Very interesting.

We got into what some of the reports may look like, how to find and filter the records, we also talked about bulk ways to look and match-up those extra details (serial numbers per mini unit). We got into 1-to-many-to-many-to-many relationships. It got kinda deep in places. Build what is needed to track it all the way through. Very interesting.

Steve and Sean were also talking about tracking backorders and using quotes (orders), invoices, and monitoring the fulfillment of those orders. We got into concepts of joiner tables out in database land. A joiner table is a table that creates relationships between different objects. The subject for this meeting was quotes, quote line items (aka the order), and how those were fulfilled on one or more invoices, and invoice line items. We talked about ways of using a joiner table to monitor those relationships and fulfillment needs.

Good meeting, lots of concepts, pitching, planning, and drawing.

Emails, text messages, and transitioning into working on the void deposits and expense/receipts project where we back out associated balance sheet item entries. Worked on the back out BSI item entry project. Spent time working on the expense/receipt side of the fence today. Getting close on that project.

Phone call with Russell. We talked about a wage increase as of November 1st of this year (in a couple of days). He is working and was telling me about his school load and what he hopes to do over the next semester and other classes that are coming down the pipeline. Russell has done a great job and we would love to get his help on a more permanent basis as a key dependable.

After that, phone call with Russell, I did some review of some notes that Steve and I have been making for the adilas trust entity.

Steve and I met for almost an hour going over ideas, sales, company background, rules of the adilas trust, talking about selling percentages to help cover things, and other topics. Good conversation. I took a bunch of new notes and have them on my local computer (laptop). We are planning to make an initial internal offering for adilas percentages from November 1st to December 31st. We are changing up some of the internal ownership structure and want to let our guys and gals know what we are doing. All good stuff, we hope, just something new that we haven't done before. The story is unfolding and we are getting a more clear view of what we want to do and what we have to do. Steve and I were brainstorming and roughing out things that we wanted to put into the official memo and notice. Exciting times.

Brandon has almost 4 pages of notes on his local computer with ideas and things that we are planning and going to be doing.

Work session with Danny and I on his four new ecommerce settings. We were at the part where those pieces need to be implemented into the ecommerce side of the puzzle. We spent the whole session going over how ecommerce works and what pages to what. Somewhat of a tour/exploratory view of the ecommerce pages and flow. I thought that it was fun and hopefully Danny is feeling more comfortable with where things are headed and where things are going (for this project).

Chuck did some light training for Danny and I on popup modals and what is already available through our current CSS and project themes (bootstrap libraries and themes). After that, Danny left and it was just Chuck and I. We turned over to flex grid tie-in training and talked about how we were going to be using flex grid in our gun registration project. We then prepped his local environment and then coded or did a wire-up job from his custom gun registration page into full on customer records with associated flex grid tie-ins for his customer fields that were needed. It's not super tight yet, but he is getting the concepts and I hope that he is enjoying the custom wire-up training that we are doing. I'm hoping that it will help him later on when he is doing more frontend stuff and having at least, a knowledge of how we do the wire-ups after the facts. I think that it is going pretty well.

Here is a small help file that helps talk about concepts of what the flex grid is able to do (click here).

Helping Shawn get his local environment setup and back up to speed. Sometimes, Shawn takes big breaks between times of working with us and what not. We re-cloned some code and repository stuff for him to give him a new start.

Sean and Danny were talking about simplicity and ease of use. Each industry is so different. They were talking about simple buttons, wizard type hand holding (step by step processes), and easy completion of the remaining steps. They, both of them, were focusing on gun dealers and gun shooting ranges, but the concepts are very general. We have to be deep enough to get the job done, but nobody wants to wade through the whole lake to get to the beach. Keep is short and simple, where possible.

Emails and recording notes from post-its to digital. Checking on a small bug for Cory. Couldn't find anything. Eric joined and had some questions. Pointed him in a good direction.

Working with Chuck on the flex grid wire-up job for the gun registration pages. We also did some light review on some of the other code that we were working on. Work/training session.

Alan didn't check in, so I just spent the time cleaning up and recording notes from the past couple of days.

Working on some new documents dealing with the structure of Adilas, LLC as a company and options for moving into the Adilas Trust entity. Some of this work was looking through older notes and writing up an offering (percentages) document for the main Adilas, LLC entity.

Bryan and I met up and worked through a custom inventory report. We ended up getting pretty deep into the logic and underlying form values that were passed in. It was good to work on it together, as we kept each other in check and on task. Good little work session. At the end, we pushed up some new code to the servers. Bryan is going to tweak on of the exports and get back with me.

Working on the percentage offering document for the Adilas Trust. We are planning on gifting between 10% and 20% to the Adilas Trust. That is where we will help all of the adilas dependables track their dividends, investments, etc. Good stuff.

More work on the percentage offering documents for the Adilas Trust. The current document has 4 pages. The first is the offering (what percentages are available and how that will work). The second page is some sales and revenue history and company valuation stuff. Pages three and four are quick Q&A's (question/answers). Sent a copy off to Steve for his review.

Sean was the only one on this morning. We were talking and chatting about quotes, orders, and expanding that part of the system. He has a client with a need to virtually sell all kinds of stuff without actually having things in your inventory. That would be perfect for an order (using a quote but calling it an order). We also talked about how a single quote/order could then populate one or more invoices to eventually solve or resolve the requested amounts. That quote to invoice (possible multi) relation would need to endure and be accessible over time as the products get pushed out to the customer or client. Fun discussion.

After Sean checked out, I went back to making modifications to the Adilas Trust and adilas.biz offerings document.

Wayne and Cory joined the meeting. Steve was unable to join. We went over a number of ideas and details on the project to take the corp-wide settings and ecommerce settings and break those huge tables (tons of settings) into smaller pieces. We talked about a new session held server object and asking for settings via a setting service that Wayne and Alan are working on (less database calls). Currently, all corp-wide settings are held in the database and pulled over and over, based on the pages and the needs of the user. See attached for some of our other notes.

Wayne was mostly leading the discussion, I was taking notes, and Cory was following along. For this project, Wayne will end up working with some other developers and he will be the lead on this project. The goal is to be able to get our servers ready to cluster or operate in a cluster environment (more power).

Research on modals and JavaScript. Danny and I spent the hour doing research and trying some things. We need to load in some dynamic modals (virtual popup windows) for an age prompt out in ecommerce. Most of the session toady was research and playing with scratch files.

Chuck and I were working on the custom wire job to help with the gun registration page for a new client. We worked on some error messages, updating comments and notes in the database, and general overview of what we've got done so far. Good wire up training project. The project involves a custom form, validation, checking for existing records, and adding and editing registration results (including flex grid tie-in stuff). We should only have about an hour left to finish up this first round. Getting close.

Meeting with Cory to go over projects. We were talking about developers, schedules, updates, and projects. We detailed out a couple of projects dealing with ecommerce. One was for a new setting to show/hide a customer photo gallery in ecommerce. Allowing customers to upload their own documents and pictures. The other one was dealing with flex attributes and being able show and use those new customer flex attributes out in ecommerce (in-line database extensions). It is fun to see how each section gets built, and then a little bit later on, it gets refined and added to. It just keeps going. Constant refinements and progress.

Recording notes from the day. Trying to keep up.

Writing up a personal letter to Kelly, talking about server department stuff. Steve and I had some ideas we wanted to put in writing and present them to her. We wanted to pitch her some ideas on joining forces to make an internal adilas service department. Kelly has been one of the top rep/consultants for the past 10 years.