Emails and getting ready for the day.

Zoom meeting with Russell. See my notes below.

After meeting with Russell, I was on a phone call with John for about 30 minutes. Talking about what is going on with Adilas and Adilas Lite. Going over possible work options. He is going to reach out to Steve and Cory and we'll go from there.

Some of my notes from meeting with Russell:

- Working with Russell on his tool and homemade framework project. He has learned a lot by building it. He can then take that information and know how and apply it to his other projects. Interesting learning method.

- We talked about project bloat - and how using outside libraries and themes are faster, but it tends to bloat the project (you get more than you want or need - code wise).

- Instruction heavy vs automated

- A framework sets a standard. You can then start expecting certain things. Almost like a miniature set of rules and expectations.

- Starter kits vs the end all, be all - You have to start somewhere. Things will keep morphing over time.

- Tools tend to be built as a box (sort of rigid). Often, people and companies want to add on to the box (customize or add custom code or custom work flow). You then have to ask yourself, does your (my) code fit in the box? Yes/No - then trying to match up tools with company structure and needs. Russell was drawing a standard code set and then a non-standard code set. Imagine one being like a box and the other looking like a blob or a flower with different peddles. We were talking about what fits in the box and what has to be custom. We had some good conversations about that. What is the core? What are the plugins? What is custom? What is allowed? What tools or tooling is being used? Etc.

- API's and API sockets - Allowing outside parties to virtually play at the wall - The backend code could be whatever. The frontend is more structured, meaning the API interface needs to be open to outside traffic (permissioned and approved) and a standard that could be used over and over again. Basically, how it is presented back to the user or developer, needs to be well documented and as standard as possible. The true backend has more flexibility. The backend creates the content that is given back. It also interprets the inbound requests.

- The system and it's architecture and code are all based on trade-offs. You then have to accept those trade-offs. Speed, flexibility, rigidity, rules, scale, custom, standard, hardcoded, dynamic, etc. You have to look and balance the trade-offs.

- If you are doing the full API socket thing, you could actually do a headless CMS (content management system). Basically, if you are going the API route for quick and dirty stuff, it (the new application) doesn't have to look like or follow the same rules (thus becoming headless). You separate the content from the layout or view of that content. Imagine a WordPress type app that is built better and interacts with our internal pieces. We talked about the flexibility of the API. It would be so cool if you could mix and match API calls (quickness) and the whole power of the adilas backend. Inbound and outbound requests could return simple JSON. Lots of potential here. For fracture and adilas lite, we want to run the whole thing off of API socket calls. Our own internal headless CMS, in a way.

- Doing everything on your own (one man show or lone wolf) requires you to know too many topics and subjects. Jack of many trades, master of none. You can gain a lot by allowing for specialists and teams. Correctly done, they can make some amazing things happen.

- Setting up rules and then enforcing those rules. Firm, fair, consistent.

- When pushing API content back, sometimes it is helpful if you can add in helpful stuff to help out the users - For example: Pagination values and page links. Ideally, it is all done through settings, requests, and options. Only return what they want, but make it available if needed. Try to think - what would help the user and/or developer on the other side of the API request?

- Building out basic functions that could be plug and play (self-documenting, self-validating, etc.)

- Russell is trying to build an auto generating REST API for his stuff. The auto generating portion is based on the database (data dictionary). Virtually a set of interpreted rules, assignments, and instruction.

- There is a database level and a service level. Each needs to be built separately. In our terms, we are trying to do DAO's (data or database access objects) and services (things that do something including connecting to the DAO's).

- Build the super complex stuff once, and then use it many.

- We talked about the analogy of a set of railroad tracks. If you build out the known railroad tracks and have proven the methods, you can use it over and over again. Railroad tracks are great for that. If you have to keep building out new ones, and you don't get to use them over and over again, why make railroad tracks, make a simple road instead.

- Figuring out your own testing strategy

- Helping the users use things correctly based on validation and/or information or feedback to the users. Basically, force them down the path and don't give them too much wiggle room (helps the devs manage things). Sometimes too many choices cause more problems.

- Usability and error handling and error messages (good communication back to the client or end-user or even back to the developers).

- From Russell - When your code structure or architecture is bad, your testing will scream at you. If you have a good structure or architecture, your tests should be easy or easier.

- The value of training

- If the servers are down, you don't build tests, you just fix. If you have the time, you build the tests and get the whole thing done.

- Having a good system helps you go faster.

- Dealing with testing, you are going to test anyways, may as well write it in a test. This enables you to be able to go back and rerun those tests. If you have good tests, it should help you in finding those error and bugs faster. Progress moves at the speed of trust. If it's your mess (code), you know how to clean it up and fix it, you also know what it affects (touches or reaches out to - dependencies). What about the other guy (someone who comes in and works on your code)? How do you pass on the notes and instructions? You really have to think about looking out for the other guys/gals that will be coming along later.

Recording notes from earlier meetings. Spent some time reading over a document with a general outline of the adilas lite and fracture projects. Got the outline document from Hamid last night. I made a few small changes. Making progress. See attached for both the original from Hamid and few of my changes. We are going to bat it around a bit and figure out what else is needed. Nice little work session.

Emails with Steve and then working on Bear 100 mile race pages. Simplified the aid station titles on the DNF pages. Had to do some light gymnastics to take a cryptic message and make it read in plain English (easier to read). Added in a sort order on the aid station results. Pushed up new code.

Recording time and recording notes. Doing some planning on mileage stuff. Printed out some notes and making plans. Small paper and pen session writing down some notes. Sometimes it really helps me to step away from the computer. See attached.

45 minute phone call with Steve, going over possible new bigger client that has multiple locations. Light talks about a new shopping cart that is needed. Other look and feel stuff.

Phone call with Steve. Heather, my wife, joined us for most of it. We were going to talk about a new internal shopping cart but Cory wasn't able to join us on the call. Today was Labor Day and she was off.

We ended up talking shop and talking about adilas in general. We covered the gamut and talked about all kinds of topics. I took a bunch of notes and was even writing Heather some notes as Steve was talking (interpreting and filling in gaps). Here are a few of the topics that we spent some time on.

- Defining the company structure and what does that look like or what will it look like? We all wear lots of hats and do all kinds of stuff. Who controls what, who manages what, and who reports to who? That all (company structure) needs to be defined. We've been able to skate along and skip some of this, but we really, really, need it now. We are getting too big not to have it. This lack of structure is starting to affect other parts of the puzzle. It is amazing what we have done, up to this point, but we also see that some changes are needed. We both agree on that, we just aren't sure how that needs to be done. We need a plan for this.

- Communication lines and who knows what and when do they know it? Some of our communication lines have been struggling.

- Steve and I were both able to vent a little bit. We are coming from different angles, but both wanting similar things. Heather chimed in a few times as well. I think that it was good for all of us on the call.

- The terms "plan" and "projects" are not the same thing. If we have a project, then we have to make a plan for it, meaning the project. The project is not the plan itself. We also talked about short term, long term, etc. The plan that we are talking about is a long term plan (small mock-up outline - not the finished product). Not just the next project. There is a huge difference.

- We have been really good at bootstrapping (working with minimal funds or funding and making things happen on a shoestring budget). We are super good at just in time project management. We are really good at seeing a need and coming up with a solution. We are not very good at long term planning. We also struggle with communication and expressing ourselves.

- Steve is very good at sales. He is good at watching out for people and helping them achieve their dreams. He hates being in debt. He hates owing people money and not being able to pay people for work that has been done. Especially, in a timely manner. That just adds stress. He is one of our best doers - he just goes for it. Super hard worker. He has sold more adilas systems than any other person. He has trained countless companies, employees, and consultants. Originally, he was the mastermind and brains behind the whole concept of adilas. It's been an amazing journey. One of his strong points was explaining what he wanted and then letting us figure out what steps needed to be taken to get there. He has done this over and over again.

- Due to lack of funds or any outside funding, we have had to run super thin and lean. In some ways, that has been really good and we've advanced the ball further than anybody else could have (us and our team). That same lack of funds has a downside as well. That doesn't give any flexibility for creativity, experimentation, testing, documentation, and even marketing. We are missing some key pieces.

- We spent some time talking about selling part of our company to raise some money. That has pros and cons as well.

- ROI (return on investment) and budgets

- We tend to follow the dollar - if a client wants something and is willing to pay, even if it not quite or even close to enough, we tend to go that way. Steve was talking about an old saying - "A bird in the hand is better than two in the bush." Meaning, you just keep getting what is available and real vs chasing something that may or may not come to pass.

- Building up a company, any kind, especially a SaaS (software as a service) company takes time and money. No way around that.

- All of us have been running at max for a long time. That takes a toll.

- The end goal is a reoccurring revenue stream or model. We are getting there, it just takes a lot of everything to keep that up and running.

- After the meeting with Steve, I was talking with my wife Heather and my daughter Amber. We chatted about a few things. Amber was saying, maybe downsize and then rebuild. If it's hard to manage right now, how will you manage it if it's bigger? We also talked about a possible board, council, or someone to help manage things. We may need more than one leader. We need to define and fill the correct roles. It's way too big for a single person. We'll have to plan that out and then make it happen. Good phone call.

Emails and recording notes. Small sort order change on the Bear 100 DNF pages. Ended up recording notes for 9/1/23, 9/2/23, and 9/4/23. It just keeps going. I guess that is both good and bad... :)

Sent an email to Steve with some ideas for a high-level plan (word doc and a couple of web links). Looking at possible changes for the adilas lite mini website. Reading over an outline and thinking about what needs to be updated to make the outline and mini website match.

On a Zoom meeting with Steve, Cory, and Shari O. We covered a number of topics. One new one was a little mini cart overview. They want one that is super simple and just does a limited scan cart for barcodes. No major look-ups (showing search results). We went over a few project specs. We talked about a future need for multi cash drawers or multiple registers. This could include a possible way to flag and tag an invoice and an invoice payment based on who is using what.

We went over a number of other small projects. Nothing really pressing. I took a few notes. Mostly just light maintenance stuff and/or allowing payees (users or salespersons) to be flipped on invoice payments or payees (users) to be flipped on subs of time. Most of those places, we just grab the payee (user id) from who is doing the transaction or payment. We may need a way to go in after the fact and flip that, in certain scenarios. Should be pretty simple.

Doing a few different things for ship A (main adilas). Light research on CSS, bootstrap, and what cart options we have available to us.

Spent a good 1.5 hours helping out Bryan with code and flow on his new Authorize.net integration. We ended up talking about invoice types. Bryan had added in a whole new invoice type for refunds. We talked about how even though that doesn't seem too big, it cascades into reports, financials, and other cause and effect things.

We got into the differences between refunds and voids and even partial refunds. That got a little bit deep. We ended up having Bryan write some stuff down and he will looking into some of the possible scenarios. We also went over some reflexive flex grid tie-ins and how to code those so that we get links and relationships between the original invoices and the refunds. Overall, a good session.

After Bryan left, I jumped back into doing some more CSS research for a new mini cart. Recording some notes.

Part way through some CSS research, I got a phone call from Eric. He wanted to go over some options for recording tips - credit card stuff, merchant processing, and how all of that flows through accounting. We talked about a number of options, including using special accounts to show the liability and the asset, until cleared out (tips paid out to employees). After I got done with Eric, I jumped back into some CSS and bootstrap research. See attached for some notes. I was playing with things on the w3schools website.

Recording notes for the day.

Spent an hour and a half going over what I learned yesterday from the Bootstrap tutorials from w3schools. Making my own page with all kinds of elements, containers, row, columns, tags, classes, spans, and fun stuff. Basically, a practice session.

Great little session with Eric, going over accounting for tips and gratuities. See attached for some of our brainstorming ideas and notes. We also did a bunch of drawings, scenarios, and even used the financial flow calculator to run some scenarios. Good stuff.

Prep stuff for a new cart. Reviewing basic HTML, CSS, and Bootstrap tags, attributes, and classes. Spent most of today going back over links, images, and tables. Quickly bouncing through pages at w3schools. Trying to make sure I good with the basics before jumping into a whole new realm (huge pre-built theme with HTML, CSS, Bootstrap, and JavaScript).

Zoom session with Russell. We spent an hour going over Ajax and jQuery training. I told him that I had to build a small mini cart and he jumped in and was helping me learn some basics. He sent me over the files that we were working on.

We covered topics of: Looking up options for fake api's (get quick data from an outside source just for testing), samples Ajax calls, samples for jQuery, fetch, CSS spinners, we rand some quick tests, pull things in quickly, configured them, and tested them without any special calls (quick and raw). etc.

My other big takeaway from the morning meeting was the value of the continuing education that Russell has been doing, adding it up over time. He was able to jump in and start playing vs having to look everything up or not knowing where to go or start. He already had the basics and was able to build from there. That was super cool and fun to watch. He told me that was from years and years of doing continuing education, a little here, a little there, etc. Super cool!

Eric and I jumped on for a second session going over tips and gratuities, accounting, flow, and exploring that project. Good stuff. Eric was taking the notes today. I scribbled down a few things, not in any order, but here were a few things that we talked about.

This may not make much sense - just quick notes:
Tip flow - deposits, invoice payments, later flow when dealing with paying it out, main invoice amount plus the tip amount and comparing that to the sum of the invoice payments, aggregate data and adding the tips up for history reports and totals and counts. Talking about new expense types and paying those tips out. Reports to show tips earned or tips per person. We also talked about tips on a group level (splitting tips or tips not specific per person). Possible tip payout invoice - or they could just do a negative line on the deposit. Low impact changes.

Meeting with Shannon over the GoToMeeting session. It has been a while since we last met. We spent the first little bit chatting and catching up. That was fun. We then went through some history and where things are at on the adilas frontier. Back stories, front stories, current roll outs, etc. We talked about the pains and it being painful sometimes for things to come together. Sometimes it feels like it takes forever, and it progresses really slow. Just for fun, we called it survival living.

She was a really good listener and I enjoyed sharing some stories and some tales (basically more stories). I gave her two small assignments and she will be working on that over the next few weeks. After that, we will be getting back together to meet twice a week. She has one of my sisters coming over for the next few weeks, so she will be unavailable for a while.

Recording notes from 9/6 and 9/7. Watching a Camtasia video on a guy doing some cool editing. His name is Oz Du Soleil and his video was on making an Excel spreadsheet tutorial. Pretty cool. The fun one was how he made it. Here's the link. Hamid and I are planning on doing some video tutorials for adilas. Maybe not quite that cool!

Hamid works at Walmart and he had to go down and help out another store do some inventory counts. He was telling me how they deal with shrinkage (people stealing) and what not. Pretty crazy. Almost this balance between labor costs (what it costs to have x number of people) and what it costs to write off the shrinkage (stealing). Anyways, we talked about this little balance between the two costs. Interesting.

We went over some Camtasia stuff, video editing, and then onto some Bootstrap stuff. Hamid was checking out a resource for some Bootstrap themes and free web hosting. We are way to big for that, but it was pretty cool (mdbgo.com).

We spent some time talking about the adilas lite outline that Hamid helped me put together. I told him that I used that, just the other day, to send to Steve. That was a big help. I also sent him the Bootstrap theme that we are using for the adilas snow owl theme. Good session.

Recording notes for the day, light clean-up, and checking some emails.

Great two-day conference. Took tons and tons of notes. See attached.

So, Sharik Peck, owner and founder of Rezzimax allowed me to come watch he and his team put the conference on. I brought my mother, who loves that kind of learning and content. Those people (the participants) were her kind of people. That was fun to watch all of them interact. I ended up loving it as well. I learned a ton, tried out the products, and even contributed a bit to the conference (questions and comments). My main goal was watching what they were doing, how they interacted with the conference participants, and observe little tips and tricks that I could pick up and use when I do some training events and conferences. Good stuff!

Here are some of my notes. Once again, this was more of me observing and picking out tiny tidbits of information vs taking notes on what they were really doing and talking about. I hope that makes sense.

- The Dream - telling a small story. Dreaming and then trying to put the dream into reality. Just the motion of following a dream led to a whole other set of ideas, situations, experiments, and achievements. Basically, the whole journey that ensued and is still going. All from following or attempting to follow a dream.

- One of the main goals was sharing knowledge and getting manuals and resources out to their users. One of their biggest problems was - How can we replicate "Sharik" (fill in the name of whomever is a major key player or awesome influencer)? Sometimes, to start with, lots of the main knowledge and/or know how resides in a few key players. We have to get that information out, virtually duplicate that person, and let others help run with it.

- They spent some time, right at the first, trying to get the conference attendees to help pass the word along. They did a whole section on the affiliate program that they are using. This could be done through referral links, commission structures, affiliate program website, training, certification, and specific tracking of coupons.

- They used some guest speakers to help spread the word. They also have done some research, written articles, and gotten things published, in order to get the word out. Some of that takes times and networking. Along with that, it is always good to bounce ideas off others in your field. Collaboration and idea farming.

- "Form follows function" - they kept saying that

- Small pieces of world building - I saw interconnected system, relationships, finding and fixing problems, addressing pain and disfunction, and seeing how those interrelated pieces worked together to almost create a world. This is an older entry dealing with some world building concepts.

- The smallest change in a system can play through and create new problems and new solutions. Trying to get a good balance - along the way.

- Straightening out disharmonies

- Helping people help themselves - teaching them coping and learning skills

- Deprogramming - things that run in natural or normal habits that may be unwanted or causing problems and issues. Deprogramming, in a way, means undoing or rerouting paths and avenues.

- Lots of experimenting and being okay with that - nothing happens by magic.

- Practice and hands on training - they were giving additional instruction during the practice session. The instructors were miced (had microphones attached to them) as they were walking around and helping others with the practice session. Everybody was able to gain from the instruction and feedback given to individuals.

- Durning the presentation, they would bounce out to a well formatted video to help encourage the participants to go to their YouTube channel for more information.

- Talking about alignment and getting things in-tune or aligned - This was tied into a foundation and going back to the basics. This included basic knowledge and basic techniques. The alignment seemed to be a key factor.

- Focus your mind on what you are grateful for... One of the best sources of change.

- Over the years, Sharik has gone onsite and helped out many people - where they are (to their place, their home, or their business). That seemed to be a reoccurring theme.

- Look where you want to go - If you do, you'll have a better change of getting there.

- Victim or Advocate - Question - I make things happen or things happen to me?

- Thinking about thinking - an active approach

- They used their tagline over and over again. It was - "Tune out pain and tune into life!"

- He, Sharik, tries to surround himself with people who have lots of skills, knowledge, and talents.

- They had products and samples that they gave out and let people use, try, and experiment with.

- Their packaging was very professional looking. Nice glossy info sheets, nice visuals, everything looked very professional.

- Matching frequencies - we don't want to stay out of sync very long. We tend to want to match what we are hearing and/or feeling.

- Great interactions between the instructors and the conference attendees.

- Consistency and creating good habits.

- Don't be afraid to try something new. Learning over time and recognizing patterns.

- There were a few different times that Sharik would talk about the process of inventing - He would wake up, write things down, react to things as they keep coming (from any source), and keep moving forward based on where he was and where he wanted to go. I loved the stories.

- Quite a few user stories (from the participants) and testimonials. You could tell that everybody liked the products and the procedures (protocols).

- Lots and lots of great hands-on practice sessions. He even had a number of people (assistants) who could help him out, there at the conference.

- They kept referring back to their website for videos, information, manuals, products, etc.

- They had a new product that got introduced at the conference. You could tell that a lot of time, energy, money, planning, and excitement were part of the new product release. They introduced their mini's or mini version of their calibrated vibration tuner. It was pretty cool! Everyone there got one to play with and experiment with it. Lots of ideas and scenarios started to play out. The participants were expressing ideas and possible solutions, almost imediately. That was really fun to watch.

- Feedback was requested and very welcome.

- Sharik has been doing some public speaking at different events for quite some time. Great way to get the message out there.

- Loved the light flexibility in their agenda. They switched things up on the training as needed. If you were a person who fully expected perfect clockwork, you would have been disappointed. If you were ok with some flexibility, they you were spot on. They still kept it moving but there were definitely some custom alterations on the fly. I really enjoyed it.

- Recipes - basic steps to get a certain outcome or output. They called them "rezzipes" for Rezzimax but they were virtually recipes - simple steps to get certain results.

- Harvesting ideas from others - giving credit where due.

- Lots of personal stories, details, knowledge, hints, tips, and experiences. That made it fun.

- They kept showing success stories - it almost made you want to be one of the success stories. Almost a level of marketing without actually marketing. That was cool!

- They ended the first day pretty casually and soft - they didn't teach clear to the end. Sort of a soft ending on day one. Light interactions, hands-on experimenting, networking, etc. Quite a few people hung out and chatted, asked questions, and had some great interactions.

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

Day 2

- Small suggestion from my mom - A bag with your logo on it. We got lots of goodies and new toys. My mom recommended that a bag would be nice. It would be reusable, helpful, and people could see your logo and name as the people carry their stuff.

- Sharik started the day off by asking for feedback.

- He had a few people that could only be there part of the day. He was willing to change his agenda to help accommodate some of the people who needed to leave early. Those people wanted to cover a specific topic. That showed great flexibility and a personal touch.

- He, Sharik, made some fun and great introductions to those who were helping him out. His fun introduction added credibility to the presenters and/or helpers. Whatever their role was.

- They showed a new mobile app to go along with their new minis (calibrated vibration tuners). Super small demo. Talking about upcoming changes. The users wanted to be able to read/write new hardware names (be able to name the devices - in English vs multi-digit serial numbers). They wanted ways to name the device, assign them to a room, or attach a type to the device. Basically, ways to flag and tag things so that they could organize their environments. It was all about organizing their flow.

- They (the users) wanted to be able to turn things on and off remotely. Using technology to help their clients and patients sleep better.

- They also wanted full control to program multi devices with plans, modes, times, timers, and custom options.

- The end users wanted to know timelines, they were really excited to get using it.

- Currently, they are using Bluetooth to connect. They want to be able to do all functions, remotely, including ways to control all of the micro functions, timers, wake-up, go to sleep, modes, cycles, etc. Ideally, they would love it if they could program something remotely and then the device could go pick up that information from a central server or central location. Basically, a web app of sorts. Going beyond Bluetooth.

- Users wanted to know about updates, notifications, communications, and how to provide feedback.

- Not only feedback but also recommendations and feature requests.

- Sharik was asked a question and jumped back into a small history of where they came from. The electric toothbrush story. That was part of the start of the whole dream. In his dream, he was told, "Vibration will heal the human nervous system. Go figure it out!". Through experimentation, they went through over 800+ electric toothbrushes. This is a side note, but I've known Sharik for years. At one point, he was experimenting with handheld sanders (from a hardware store). The toothbrushes were too little and small and the handheld sanders were too big or too powerful. They ended up with their own tuners that allow for calibrated vibration (speed, intensity, and frequencies) and even waves and patterns. All part of the invention process. Kinda fun.

- It was fun to see journeys come full circle

- Back to the minis and the new app - the users wanted to know protocols - who to talk to, what to send in, how to communicate, etc.

- Sharik invited the developer to show the new app. All of this feedback was being thrown at him while he was presenting. They were recording it and others were taking notes. There was no way for the developer to actually take all of the notes for the requests, ideas, and suggestions as he was presenting. It really helped to have other helping to either record or jot down the notes.

- Just for fun - Sharik said about the programmer - "A programmer on a mission!"

- Note about the media guys who were helping - they had two guys recording the conference. One was the primary tech guy. The other was more promotional and marketing. They were capturing testimonials along the way. They miced (used microphones) all of the speakers. If someone else made a comment, they tried to resay it or recap over the microphone. Sharik was also recommending that the attendees get with the media guys to get their stories and/or testimonials. Pretty cool setup.

- Jumping back into the conference and some of the topics. Lots of time spent on "Trauma" - aka problems, issues, and pain. Without pain or needs, no solution is needed. Once trouble or a problem exists, a solution or answer is needed or wanted.

- Pornography, drugs, alcohol, PTSD, life events, etc. All forms of trauma or issues. Some of these things are taken in by the eyes, ears, hands, mouth, touch, feel, or other ways. Eventually, they get into us and/or affect us in some way or another.

- Teaching the law of opposites - joy and misery, happiness and sadness, inhale and exhale, push and pull, etc. Being ok with being uncomfortable. Pairing these opposites and finding patterns. Back to trauma - front door and back door approach. There is always a way in, look around and be creative.

- Let it go! Exposing yourself and being vulnerable. "IT" will come later. It meaning, what you are looking for. Sometimes you just need a catalyst for change. Replacing negative with positive (thought).

- Standing next to the event, not in it (trauma and events). Can you remove yourself from it and virtually watch it play out, what can you learn, do, observe, as you look at it from a different angle. If you only look at things from a single vantage point, you may be limited as to what options are available.

- Going almost empty and then rebuilding and replenishing.

- Trauma has attachments - it could be other traumas or connections with other events or situations. Usually, it is not just a single thing... there are relationships and multiple interconnected pieces.

- Forgiveness and understanding. Forgiveness doesn't make it right. It does have power to help you. At some point, you may need to ask, how is this all done? Where does that lead you?

- Having a safe place to recover and seek healing.

- The ability to connect to the music within you.

- Saying prayers - for self and for others - looking beyond yourself.

- Sharik was sharing his story and tons and tons of other experiences. It makes it real.

- Triggers

- Learning lessons and then passing on those lessons learned. Experiences just happen!

- At one point, they went over a number of FAQ's (frequently asked questions). They had a preset list and it made it easy to just jump through them and/or skip around as needed.

- Different people do things in different ways - that's ok and even encouraged...

- Great discussions and awesome feedback and ideas from the participants. There was enough flexibility in the presentation to allow for that.

- Inspiration and being open to new ideas. Sometimes it takes time to come to an understanding.

- Freely give, freely share - keep it open.

- Each participant comes from a completely different place. Acknowledging the pioneers in the room. Go explore. Learn from your experiences. If you are experimenting, try it on yourself first - controlled experimenting. Fun discussion.

- Mixing and combining techniques and skills.

- Finding out what nature does and either using it (nature or natural ways) or trying to simulate it. Helping to integrate those type of techniques and processes.

- There are tons of other things that can be added into the mix. Take what we have and what we offer and then add to it and even enhance it. Build off of a stable base.

- Back to a topic in the main presentation - deep questions and sequences - Am I safe? Once you feel safe or relatively safe, you can open up and/or work from there. Interesting.

- Making time to care for ourselves.

- Stick to the basics - back to recipes.

- This is from my mom - She can hear the main presenters but can't hear anybody else (other people who asked questions or chimed in). That bothered her a bit. She knew that I was taking notes on my observations and leaned over and asked me to write that down. That can be hard to fix and tends to fall on the presenter to restate the questions and comments. Just noting that was requested (restate what is being said by others).

- Pathways - things that are used over and over. What works for you? Use that and then build and go from there. Along those same lines - think about strategies and figuring out how to duplicate or predict certain outcomes and behaviors.

- Light humor lubes the discussion and/or topics being taught or discussed.

- Gathering information - connecting the dots - even over time. Be patient! Along the way, seek for opportunities and find alternate paths or pathways.

- Sove a problem, then move on to the next... the deeper you look, it will become a map of the environment. That's pretty cool!

- Going back to basics - the goal is the big picture.

- Repetitive processes - that's how we learn.

- More videos and referring the participants to subscribe to the YouTube channels (plural).

- Lots of techniques, tips, and tricks.

- They were talking about self-healing... at times more advanced help is needed - meaning surgery or other advanced help. That is okay! Start with self-healing and go from there. There is a point that we need other people and their skills and knowledge.

- Talking about pain - if you take it all away, sometimes you do something stupid - keep it real - without any pain, you can push things too hard. Pain can be a great teacher. Knowing your limits.

- In their videos... there was a lot of consistency - well done. Some of them felt repetitive but yet different.

- Sharik's wife kept helping them, whoever was presenting, with reminders and helping them if they forgot something.

- Giving service - helping and doing good

- Public speaking and facing fears

- They were talking about sharing energy and sharing energies (plural)

- The feet are great messengers to the brain

- Simple steps - set timing - set steps - make it repeatable

- Watching friendships and relationships being made from the conference attendees - fun to watch

- People cheerleading each other and supporting each other

- Good laughter and fun times

- Emotions tied to injury - making new paths to the brain

- Putting all of the pieces together - creating a system and using other systems that already exist

- This was big for me... what have we found... letting people know... passing on that knowledge

- Just noticing - some of the attendees were standing, going up, getting closer, taking pictures of slides, videoing, recording, and taking notes - internal thinking

- People want to learn - some great questions and follow-ups

- Telling the brain "the map"

- Being developed on the fly... people testing things on the fly. They were putting ideas into play on the fly (meaning the attendees and the presenters). This was especially true as they were playing with tuners and techniques.

- Alignments - keep coming back to simple alignment concepts

- Improvements and seeking improvements

- Major participation - he called someone up to the front, let them do it, and he was commenting and lightly direction what was being done. Very hands on.

- Watching for reactions - seeing through their behavior

- Things working together

- Talking about sensitivity and visiting or building up those areas over time.

- Following protocols - set steps to follow to get certain results

- Translating ideas and concepts to different applications

- Personal stories and tying them into parts of the bigger or main story

- Helping to solve problems - daily

- Constant message of gratitude - being grateful

- Good resources - that helps to bring back that knowledge quickly

- Sensitive individuals - start where or wherever they are at - helping them quickly get back to recovery

- If it takes time - take that time

- When they are ready... there is always a timing that goes along with healing

- Question - Are you trying to solve things or just make things better or easier? There is a difference.

- Thanking others

- Explaining why we do the same things over and over again - finding those patterns and reasons

- For me, I loved the stories and how much Sharik and others had helped others, all around the world, making a difference.

- If you do some pain... Make sure you put a smile on their face before they leave.

- Some of the participants want a way to share and pass on advanced tips and techniques. They talked about a Facebook group(s) and making them public or private, depending.

- Wanting to stay connected

- Mindfulness and being focused - going there on purpose

- Self regulating

- A tool to help - not the end all solution

- Primitive reflexes - a return to a pattern - there are both good and bad primitive reflexes - ways to help overcome ones that are unwanted

- Light it up (an area of the body or a pathway to the brain) - the brain loves information - food for the brain

- Asking others to help us get the word out - work of mouth

- Technique - cross grain or crossing - going across the midline and then back again.

- Transforming and transferring energy

- Test it as you treat

- Work on the weak side

- Working through barriers

- Accelerating processes

- Isn't that cool (both ! and ?) - statement and question

- Combos

- Tests

- X is tied to Y, is tied into Z, is tied into... Everything is interconnected.

- Reviewing, even at the risk of sounding like a broken record.

- Spent some time going through scenarios (different changes or alterations based on the circumstances)

- Integrating both sides - of the body or of your environment

- Keep working on things that need help - wake it up - then integrate it

- Mirror therapy

- Don't put limits on what people can do - the mind and body are amazing

On the phone with Steve going over a new possible shopping cart. We talked tech stuff, look and feel stuff, as well as logic stuff. Steve has a client that really wants a scan only cart (just barcodes, nothing else). We talked about the pro and cons and challenges of different possibilities and paths. We decided to mix and blend some of the tech.

We also talked about how some of our competition shoots for a best-in-class status but only does one a small portion of the puzzle. The end user or companies are then required to use multiple pieces of software, and then try to marry them together in some sort of mash-up or combined solution (conglomerate) of sorts. That creates other pains and problems. Our systemized approach has some great value.

Steve and I also talked about how some of the new fracture (adilas lite) code is actually project # 6 on the to do list. We can really help push on ship A (current adilas model) before we jump right into fracture. That's a good plan, for now.

Zoom meeting with Cory. We went over projects, updates, and needs. Light project management. I'm supposed to focus on the new shopping cart and help the other guys as needed.

After the meeting with Cory, I jumped on a GoToMeeting session with Bryan. We were trying to figure out some alignment and spacing for a client that has a custom login page. Bryan and I also spent some time working on some files and Git code repository stuff on Bryan's local code branches. Getting branches sorted out and everything in its own place.

Emails and recording some notes from this morning. Light prep for getting into the new shopping cart stuff.

Adding some small tweaks to the main adilas lite website (view page). Added a crumb trail, new sub navigation to bounce to each subpage, a more standard header, and a link to the fracture - PDF outline. Pushed up new code.

Bryan and I jumped on a quick meeting to go over some refund flow and logic.

Prep work for a new shopping cart inside of adilas. Started on the project. Reviewed some video, sketched out some ideas on paper, and light research. It should end up being super simple. Recording some notes to finish up the day.

Emails, recording notes, paying bills, and on the phone with Shari O. Mostly random to do list stuff.

Web & Mobile Development Occupational Advisory Committee Meeting at Bridgerland. Sat in on the meeting and participated. This was my first time going to the advisory committee meeting. It was pretty fun. We ate lunch, went through an agenda, small slide show, and then talked about ideas and options. It sounds like they might want me to come back and talk to their students about SaaS (software as a service) and remote working from home. That sounds fun.

After the meeting I talked briefly with a guy who helps write grants. Random side note, the Bridgerland Web & Mobile Development Certificate requires 30 credits and about 900 hours. They require a competency level of at least a B+ for each class taken. I thought that was pretty cool.

I also visited with Sterling over in the main campus. We chatted for about half an hour. I'd like to start rescheduling some training events there at Bridgerland. It's been a great venue. Anyways, I told him that I would be interested in teaching some classes come spring time.

Recording notes and mileage for the conference last weekend and the committee advisory meeting today. Scanning in notes from the Rezzimax Conference last weekend (see pdf).

Recording notes from the Rezzimax Conference. See element of time 10257 in the shop for more information.

Recording notes, phone call with Bryan, and then back on the mini scan cart project.

Meeting with Bryan. He is working on the authorize.net project and doing invoices with multiple payments, voids, and refunds. Going over payment flow and questions.

Making progress on the mini scan cart project. Adding in some navigation, buttons, and starting to look into settings and dynamics.

Working on a section of the mini scan cart called preset searches. It's almost like mini custom links and buttons that are available as part of the new shopping cart settings. There will be up to 10 customer buttons, searches, and links. Trying to make the whole thing dynamic. After that, started into the customer info section.

Looking over code and pay flow with Bryan. He is getting close on his Authorize.net project for refunds and voids. We will hit it again tomorrow.

Recording notes from the day (9/13/23). Lots of ship A stuff today.

Recording notes from the Rezzimax conference. See element of time # 10257 for the actual notes.

Emails, recording a few notes, and then back on the mini scan cart. Working on formatting, layout stuff, and settings. Spent time starting to plan out and build the starting of the settings page. This should be pretty cool when it is finished.

Working with Bryan on code for refunds. Code review, tightening things up a bit, and trying to smooth out the process. It's still a little bit bumpy. We got into a place where we needed code for both single and multiple payments. For now, we ended up putting in some temporary error messages and blocking certain functions. More code review and fixing some merge conflicts.

Did some prep work for storing the new mini scan cart settings. Zoom meeting with Cory to show her some progress. Spent time building out a new method to pull the custom JSON objects out of the database.

Meeting with Hamid. He is working on some bootstrap tutorials and doing some practice pages. I showed him what I was doing on the new shopping cart.

Jumped on with Steve before meeting with Russell. We went over the new mini scan cart and some of the settings. Trying to show him where we are going.

Met with Russell for about an hour. We spent the whole time working scrolling layouts. We also did some research and built a small table that we will be using in the mini scan cart to show a line items table and the top row (headings) are sticky, meaning they stay at the top and the rest of the table scrolls. Great little work session.

Jumped on the GoToMeeting with Chuck. He needs to get his local environment all setup again. He wiped a hard drive and lost his older local box and coding environment. We talked about options of the older classic way or getting with Wayne to try the Docker container way. I got him enough info that he can do it either way. We then talked about the new shopping cart that I'm working on. He was watching and providing some light feedback.

Recording notes from 9/14/23 and 9/15/23.

Meeting with Cory. We talked about discounts on special line items and unlimited special parts. We briefly discussed the new discount engine and plans for getting that fully up and running. The other three things that are coming down the pipeline are helping Bryan with some reports, the mini scan cart, and the Bear 100 is coming up at the end of the week. We also looked on data 20 at some possible duplicate invoices. We talked about some possible solutions to prevent that. You have to work pretty hard to make that happen. It happens in real life, but we can duplicate it while doing any testing. Almost like an Internet glitch that happens every once in a while.

After the meeting, emails and touching base with Bryan on pushing code. Recording some quick notes.

Started into some bootstrap training and got a text from Bryan. We jumped on a GoToMeeting session and looked at a date/time issue. We made some fixes and merged in some code. After that, doing some emails with Wayne on being able to reconnect via our VPN (virtual private network) to push up code.

Working on the mini scan cart. Adding some new options for layouts, settings, and working with forms and placeholders. Small work session. Pushed up code to repository. Making progress.

Bryan and I merged in some code last night that we were working on. It was working great on all of our tests. We weren't able to push it live for testing before it got auto deployed. When it went live, we found that if you didn't have a certain setting turned on, it was throwing an error. I was out hiking and got a call and text message from Cory. I joined the Zoom meeting once I got home.

Wayne and Bryan were on the Zoom meeting with Cory and Shari O. We got the error fixed and made some adjustments to the code. While Wayne was re-deploying code on all of the servers. I was able to get my VPN stuff setup so that I could push code directly to the servers. That ability and connection was down for a couple of days (on my side - just not being able to connect directly to the servers). Anyways, we got it all resolved.

Once things calmed down (servers were getting fixed), I was able to talk to Wayne and do some catching up. We haven't spoken for a few months due to who is on what meeting. That was good and he was explaining his wants and needs (as a system administrator). Some of what he does we don't fully understand and/or know. Our conversation ended up flowing into the start of the server meeting. I think that he needed to talk. That was good.

Meeting with Bryan. Looking over some new merchant processing code and logic. We made a few changes to the add cart payment page and merged and pushed up code on data 0 for some testing, after we had tested locally. After that, we spent some time going over data, steps, and processes for looking at quantities on sub inventory pages and reports. Small work session.

Meeting with Alan over the GoToMeeting session. We did some catch-up and then started talking about plans and priorities. Alan was saying that we could potentially break things down into smaller and smaller pieces. We totally will and need to do that. Just for fun, he said, we could start fracturing fracture (project codename). We looked at the 7-8 projects for adilas lite and talked about priorities and how each one plays into the others. We are planning on focusing more on the value add-on core model project next. We need to lay some things out, define it, and then (even now) start building some of those pieces.

Anything that can be reusable, including concepts and code, we want to build out those pieces. Be able to reuse as much as possible. That way they can help both ship A and ship B out. Good catch-up meeting.

We decided that for the next couple of weeks, we would both focus on some ship A stuff to help out the main adilas system. We have a small deadline to try to hit by October 1st.

Great phone call with Steve. We were talking about options for white labeling and even doing some kind of franchising options for certain companies. We talked about the concept of being like Intel (chip sets). We don't have to be Dell, Sony, HP, etc. We could just be the software (virtual chip set) that run the other programs and products. We don't care what it is called (the selling company). We just want people to use our products, even if they don't know that they are running adilas or a part of adilas in the background.

Anyways, Steve has had a few different people somewhat approach him lately with similar type requests. They virtually want to own their own software but don't want to pay millions of dollars for it. Steve and I were talking about options on how that could play out and how it would work. Great phone call. I enjoyed the conversation.

As part of the conversation, I was lightly pitching the concept of white labeling and how that could tie into layer 2 of the value add-on core model - Industry specific skins - aka - white labeling. We would like to move in that direction.

Working on the mini scan cart. Spent most of the day working on the settings form. Decided to try an accordion (show/hide/collapse certain sections). The form is pretty big, so I was hoping to make it look more approachable. Light debugging on the mix between the accordion and the form stuff.

Bryan gave me a call and we chatted about asynchronous (Ajax) calls and options to help with big reports. I also jumped on a call with Eric talking about EMV chip options and how tips and gratuities play into that. He's making great progress there. We talked about keeping things super generic and then customizing the solution, either through settings, or different payment integrations.

Recording notes from today - busy day (9/19/23).

Email and then back on the mini scan cart project. Spent the morning setting up defaults, submitting the settings form, and inserting or updating the settings records in the database. Light testing on the new functionality.

Doing permissions and security stuff for the mini scan cart and being able to change settings. Working on logic to switch between corp level settings, user level settings, or no settings (new or unset settings). Quick phone call with Cory to go over repushing code up to the master branch after a roll back.

Spent some time going through the classic internal shopping cart and listing all of the main pieces and features. See attached for a list. I had forgotten about a bunch of those things... kinda fun but also puts a bigger load on remaking everything for the mini scan cart. We should be able skip quite a few of the things for this round. That will help.

Jumped on the GoToMeeting with Steve, Cory, and Wayne. We were going over bit bucket (code repository) and how to get certain files updated. We had to roll some code back and then things kinda got out of wack. We got it resolved and everything should be good to go. Wayne was showing us some high level code repository stuff. It was way over our heads, but he knew how to do it. I'm super glad that we don't have to figure out everything by ourselves. That's what a team is for.

More work on the mini scan cart. Going over replaceable dynamics, popup modals, and success messages. Working through my to do list. Small work session.

Working on cart line items for the new mini scan cart. I was able to harvest some good code from other internal shopping carts. That really helped.

Zoom session with Cory and Steve. Showing them the progress on the mini scan cart. We did some demoing, playing, and even some drawing of where things are headed. Good meeting. They want me to get it pushed up as a beta cart, even if it is not fully finished. They basically want to play with it and even start showing it before it is fully finished. I'm going to make a few more tweaks and then push up an MVP type beta product. Good stuff.

Jumped on the GoToMeeting with Hamid. He's been playing around with some basic bootstrap stuff. He showed me a page that he is working on. He is having fun altering the CSS and harvesting things out of tutorials and prebuilt themes. That is great practice and can really take you far. We spent a little bit of time going over some harvesting tips and tricks. I think that he enjoyed that. I've been harvesting things lately to work on my mini scan cart project. Just for fun, I showed him what I was working on and how a mix of both frontend and backend together make some cool stuff. Light intro into working with Bootstrap and ColdFusion.

Recording notes from yesterday (9/21/23). Most of it was ship A stuff. Jumping back into the mini scan cart project. I've actually been having fun. I hate to say it, but for the past few years I've only been able to work on small little baby projects. This one is actually a legit project that is taking more that 5-10 hours. I don't know how much it will actually take but I've already put in more that 40+ hours on this project. That's been kinda fun. One, to learn new things and two, to really see things come together. I've enjoyed that.

Not really part of my time but wanted to record this. Steve sent me a long text message with some ideas for approaching our first white label joint venture opportunity. He's been talking with some guys for quite some time. We've had other text, email, and phone conversations. He has spent countless hours already talking with these guys. He has a meeting with them today and was going to be pitching them on the joint venture white label solution. It looked pretty good. We texted back and forth, and I left a voicemail message for him. We'll see what happens.

Spent some time working on the line items, flow, layout, and links. Made a few other tweaks to the scrollbars, links, buttons, and permissions. Merged in code and pushed a beta version of the mini scan cart up to data 0 and let both Steve and Cory know about it.

As another fun note and message, I got a call from Steve just after lunch. He was reporting in on some of his conversations and meetings that he has had today. We spoke for half an hour on some of the possibilities. He is really turning some things over. Fun stuff and making progress.

Sending an email to a buddy to get him started using adilas. Sent him a bunch of links, instructions, and links to videos.

Recording notes from a couple of weeks ago, at the Rezzimax conference. See element of time # 10257 for more details and the actual notes. Wasn't quite able to finish but made some progress. As I was rereading some of those notes, there is some good stuff there. All of us need healing (in one way or another). I enjoyed going back over some of those notes. I was even getting some ideas on things that I could do to help others and myself. Good stuff!

Zoom meeting with Cory. My main two projects this week are the new shopping cart and the Bear 100. We also talked about the public API and 3rd party solutions using either the public API or a special 3rd party API socket channel. We spent some time talking about the discount engine and figuring out a plan to launch the new code while still leaving the old code somewhat in place. We may have to go backwards and retrofit the old code to handle the new custom date ranges. We'll get it all figured out.

We looked at some sub inventory reports and sub reports based off of sub id numbers and other sub reports based off of the RFID tag number. Shari O. had a few questions at the end of the meeting. She was mostly just listening in to say on top of what is going on and happening. Cory got to show her a little bit of the new shopping cart. It seems like we are mostly on top of things right now. No huge out of control fires. I left the meeting and Cory and Shari O. were still talking about emails and clients. Good stuff.

Working on the mini scan cart page and project. Started working on submitting the form via JavaScript and passing the correct mode to the update cart page. Just starting to work on the existing update cart page. Small work session.

Working with Bryan on sub inventory reports. We took an existing report and worked backwards to figure out a better join and better query. We needed some grouped data, but it had to come from a specific table with specific criteria. We ended up changing out the SQL and the left join options. Deep database query stuff. By the time we were done, I think it looked pretty good.

After meeting with Bryan, I got an email from the Bear 100 data team. They would like to meet before the race this weekend. I sent them off an invite to an after-hours meeting on Wednesday. They have a request for me to help build a test page for their CSV files. They have some new CSV formats and they want a place to try them out before they go live or do any real database interactions. Sounds fun.

Filling out job reference stuff for John for zip Recruiters. He sent me a couple of emails with links. I just clicked on the links and filled out the forms. After that, just checking elements of time and doing other emails.

Jumped back on the new cart project. Working on stripping out form fields from the classic view cart body page. These form fields will need to go into the mini scan cart in order for the update cart page to work correctly. Created a temp file to carve things out. Recording notes for the day and light clean-up.

Meeting with Bryan. We did some code review on some advanced sub inventory searches. Merged and pushed up code to data 8 for testing. We had to force a cap on the number of records that we would allow to be returned. It was timing out, if we left it too open.

Working on the update cart page for the mini scan cart. Went through the classic cart and figured out which form fields were needed. Spent some time putting those values back into play. Light testing on the new cart.

Meeting with Bryan to look at a query. Light research and refinements. Ended up being the main po/invoice line status. The query was including removed or inactive line items. We only wanted the active line items. We also had to add in a web availability filter that we missed.

Recording notes from yesterday and checking emails. Getting started for the day. Spent the morning working on button functionality. Made sure that it tied into the update cart page. Added in some subtotal and tax info. Lots of testing and micro tweaking things. Pushed up to data 0 for some live testing. It will roll into master tomorrow morning. Sent a quick text to Cory and Steve to have them go in and do some testing.

Working on refining the mini scan cart settings. Spent some time working on modal popups, links, and started on a link builder form. Good little work session. Pushed code up to the repository in a small side branch.

Multiple different sessions working on Bear 100 stuff. Built them a new page to test the CSV uploads. It uploads the page and then runs through the logic without actually inserting or updating the database. Kinda like a mini dry run. It shows errors and good data. Basically, you can run the test over and over again until everything passes. That should be a cool feature for them.

Met with the Bear 100 data team over GoToMeeting. They wanted to see all of the new features that we had added. New features, both to the public runner portal and new features to the backend radio admin app. Small dog and pony show (showing them around and doing a light review). They, the radio folks (Bear 100 data team) only use the system for a couple of days each year. They need a small review.

We played with the new test CSV file page and they gave me some feedback. We changed some code, while they were on the meeting and pushed it up.

After the meeting, I got a list of runners from the race director. Uploaded all of the runners into the system for the 2023 race.

Helping Steve with his VPN connections for accessing the servers. Lots of Bear 100 stuff. That race goes off tomorrow morning. here is link to the news and updates about the race. The actual public runner portal page is located here: https://data0.adilas.biz/bear100

Did some work for High Valley Bike Shuttles and adding some special code to browse right to a specific page with a sub tab (sub section) opened up. Normally, the sub sections have been harder to control. We added in some options to virtually control the pages and the sub tabs within the main pages. That was kinda fun.

Meeting with Bryan. I showed him some of the changes to the online scheduling stuff. He helped build the original functionality for reoccurring and special events. We then switched gears and did some planning on dealing with huge record sets and bigger reports and big data exports. Basically, we have the data in the database, but it takes too long to show the whole thing (all of the records) in the browser. Imagine asking for 20,000 records at once. The database servers that up like a snack. However, the browsers struggle because that is a big bite to chew and virtually it is like putting an elephant through a straw. It's painful.

We did lots of drawing, looking at code, samples, existing pages that do mini versions of this, etc. Good planning session. Bryan has already been playing with some code and doing some research. That is awesome. We will continue to keep playing until we feel like we have a good plan and a good mini version of what we are wanting before trying to tie it into live reports.

The discussion turned towards two major options. One is AJAX or asynchronous downloading of the data. We have to respond quickly and then show progress while pulling in the other (thousands) records. The other major option is to offload it, meaning the search and building the export, by using a queue of sorts. Basically, we push the search criteria to the queue, get a total record count, and then start building that behind the scenes. If the user wants to check, we can show progress of how many records have been added as compared with the total record count. We then notify the user when it is done. That way they don't have to wait, and they can be doing something else instead of just waiting and hoping that it will not timeout.

Bryan and I made a plan for doing some local testing on a report with 70,000 ish records and then moving it over to live once we've knocked it around a bit. We went over a few other details, but Bryan is going to start playing with some scratch files. Making progress.

Phone call with Eric going over what it would take to import customer loyalty points from an outside system or source. We went over some details and ideas. Eric is pretty busy, so I will have to build this out. He is going to send me over a file, and we'll go from there. Most likely, we will need to run this import over and over again for the same client. Reason - they are still using their existing system but as they switch, we need to keep the data up to date. We also anticipate that other clients will need the same capabilities.

Back working on some ecommerce changes and helping out High Valley Bike Shuttles with their page request and navigation options. Custom code for where they want to point people on their ecommerce site. They use a lot of our online schedling pieces, out in ecommerce land. 

Working on some JavaScript stuff to help with a link builder inside the mini scan cart settings. Didn't have much time today.

Verifying runners for the Bear 100. Going over the official start list and comparing it to what we had uploaded previously. Making some changes and then sent out emails to the race director and others.

Checking on the Bear 100 race as a moderator/watcher. Recording notes from last few days (9/27 - 9/28).

Phone calls with both Cory and Sean. There was a data import that got mixed up on data 11. We had to go in and back a few things out. We removed about 1,600 items and all associated PO line items.

Working on some JavaScript for the mini scan cart and the link builder on the settings page. Getting things pretty close, just need to do some formatting and tying the drop-down menus into live data vs some testing hardcoded values.

Combing data and then doing a new data import for about 1,600 items or products. Sent messages to Cory, Sean, and Eric to have them go in and test things to make sure all was well.

Checking on some Bear 100 runner counts. It looked like there was a problem. It ended up being that some of the data team (HAM radio folks) changed some records after the race started. Here is what happened. There were a number of people who didn't show up on time to start the race. They were marked as DNS (did not start). Later, at some time, they showed up and wanted to still run. They allowed them to start running with the original group start time. I had already seen the counts, so I had a specific number in my mind. When I checked some of the reports the numbers were different. We got it all figured out.

Phone call with Eric going over the pros and cons of sub/child inventory and parent inventory. We talked for quite a while about the needs, wants, and ins and outs of both options. I put in a plug for the ICC or internal cost correction project that would help allow us to use parent inventory (when needed and there are specific instances where that is better). Anyways, we had a good chat. It comes down to what is best for the situation and for the users. As an analogy, not everyone likes class V (class 5) rapids. Sometimes that's a little too hardcore.

Recording notes from the day. I've been bouncing all over the place today. Part of the gig.

Checking on the Bear 100 mile race. It was still in full swing. Making a few small changes to some of the pages. Now that it had some real data, we added some counters, links, and other light changes. Normally this would be billable to normal adilas but I had already made the check out for this week.