Quick phone call with Hamid. He jumped on the GoToMeeting session, but Bryan and I were still on the meeting. I gave him a call, and he said that he is working on the play at the wall website for adilas API socket stuff. He said that he is working with ChatGPT to get some ideas and how to make it both fun and informative (small pun off of "play" at the wall).

I was going to jump on with Hamid, but he had to help out his daughter. So, I did some light research on the business unmasked podcast. I also spent some time working on my flow for doing screen captures and then marking them up and drawing on them. I tried three different systems and styles. I ended up liking the TechSmith Snagit process the best. I tried Microsoft Paint and the Window's Snipping Tool as well. All of them have different benefits. Snagit allows me to draw and keep recent drawings in the library tray, even without savings. I have it setup so that I can use my print screen key, get a capture, and immediately start drawing and marking it up. I can save if I want, I can also add shapes and use my undo button if needed. It seemed to be the best fit for my presentation and drawing style. Spent some time playing with the different tools.

Working with Hamid. Showing him what I am doing with AI and how the flow goes. We started a new chat session with ChatGPT. Hamid and I worked on it together for the first two hours. He then had to leave. I then finished it up. This was a wonderful session going over the 3D data assembly line and how it ties into world building. Lots of great explanations, discovery stuff, and explaining "the gap" between operations and accounting. See attached for numerous resources. The full chat log, with ChatGPT will be listed below. This was an awesome session.

https://chatgpt.com/share/69bcdbd3-9560-8007-ad64-15d36d272a43

Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Meeting with Hamid. He is going to be building out a new webpage to help with the API homepage. We are going to call it "play at the wall" (PlayAtTheWall.com domain). If you want, here is a small hand drawing of the client/server model that shows the term play at the wall. We are just in the process of doing some planning and gathering information to help him get started. We talked about AI code creation and learning in those processes and environments. We also played around with some screen or text to voice page readers.

Emails and checking in with Hamid via text. We pushed our meeting to next week. Signed up for the Adobe ColdFusion conference in June. Recording notes for the day.

Working with Hamid. We started out and Hamid was talking about quality over quantity. Sometimes we get stuck in different cycles. I told him about some of the switches that we are making internally. We ended up talking about the adilas API sockets and helping to make that section (web pages and external tools) look more up to date, usable, and ready for new outside users and developers. I was explaining a lot of things and going over concepts and flow for the API's. I did a lot of drawing and used a number of existing pieces to show what goes where and how things look. He is going to start working on a new website for the API socket area. We are going to call it the "play at the wall" website (see this graphic for the play at the wall section). It will help with information about the adilas API sockets and endpoints, help files, samples, documentation, visual tools, and other API related stuff. Good meeting.

Meeting with Hamid. We did some work on the number fields (existing form fields) and allowing decimals vs just whole numbers. We went over some code commits and how the code repository worked and such. Small bug fix while doing some teaching and learning session with Hamid. Two birds, one stone. Good session.

Working with Hamid. He was trying to get his old portfolio website up and live again. We had to fix some URL's and some paths and such. He was having fun getting things back working again. We had to flush his cache a few times to make everything show up.

Meeting with Hamid. Going over CSS training stuff. We were watching a video and talking about what the instructor was asking us to do. Good training session.

Meeting with Hamid. Showing him some graphics and then playing with the adilas AI agent inside of adilas. One of the goals for the AI agent is... training and retaining (keeping or holding the info). We then worked on getting his VS Code instance up to date (his code editor). We played around with some code and letting Copilot (a different AI bot) help with some of the coding. We also talked about the value of knowing what is going on and/or what is being prompted/generated by the AI bot. Especially in code, the bot may give you a bunch of code, but you don't know what it does and/or how to fix it or tweak it slightly. You can get yourself in trouble. You still have to know code. Fun little session. Lots of show and tell and light playing around with different tools.

Meeting with Hamid. We did some reviewing of where we left off last time. After that, we then jumped back into the CSS course from Udemy that we were working on. Practicing and playing around with the commands and code. Went through a few chapters and videos. We are both trying to learn more about CSS. I already know some things and I've worked with it before, but never gone through an official course or class. It is surprising how many base level pieces I either thought that I knew or only mildly understood. I'm enjoying the learning process.

Jumped on the GoToMeeting session with Hamid. We were reverse engineering some different web pages and looking under the hood. He is a collector of sorts and had some questions about a site that he visits a lot. Anyways, totally different learning, but we spent the whole time looking at generated code (source code) and searching for small variables and key values. It was kinda fun... Not really hacking, but just looking around and seeing HTML, JavaScript, and CSS stuff. Interesting evening, but still learning.

Meeting with Hamid. We did some catch-up and then jumped into CSS. We are going over some course files and small practice stuff from a Udemy course. We are somewhat co-working on the practice files. We will do things, talk about them, and then go in and play around a bit. We are then sharing what we are learning. That seems to help both of us get a lot out of the practice sessions.

Meeting with Hamid. We went over some of the things that I am learning with Russell and on the Udemy CSS course. We then did a small practice file and did it together. That was fun. It also gave me a chance to use what I know, in a teaching environment. I enjoyed that. That helps it (the learning) stick better.

Hamid and I were playing around with ChartJS stuff. We built a number of different charts, playing with the x and y axis and pulling data from different spots and sources. Fun training session. Trying to get more familiar with the possible graphs and charts.

Meeting with Hamid. playing around with graphs and charts. flip flopping between bar graphs and line charts. playing with options, colors, and data sets.

Start working on some graphs and charts. Should be fun.

Looking into chartJS. Going through walk-through tutorials, playing with options, reading about what is available, and working with Hamid. Both of us were playing around and showing each other what we were learning. Small trial and error/learning session.

Meeting with Hamid. We finished up the intake form for his wife, in Spanish. See attached. This is for a skin care business. Next time we will work on some graphs and charts and get back into developer training stuff. This other project, the intake forms, was somewhat of a side project that we had to do.

Meeting with Hamid. We were working on the Spanish intake forms. Got the second page done for his wife and her skin care business.

Working with Hamid to help his wife with Spanish skin care intake forms. We finished the English version last week. Now we are doing a Spanish version. See attached.

Meeting with Hamid. We finished up the 6-page intake form for his wife and her skin care business. See attached for the form that we are/were working on.

Working with Hamid. We were working more for his wife and on her skin care business and the intake forms. We have now finished pages 1-4. See attached for our progress.

Meeting with Hamid. We were working on his client intake forms for his wife. Lots of work in Adobe Acrobat and building PDF form controls.

Working with Hamid on some PDF documents. These are forms for his wife's business. We took the PDF form and started working on it in Adobe Acrobat and adding in form fields over the top of the existing PDF document. At one point, we jumped into the data 39 box and were talking about data usage and such. We were looking at some of the data and how we got it. At some future point, we would love to see it breaking down details and looking for insights, even more than it already does. Super detailed data.

Meeting with Hamid. We went over some AI stuff. Talked about the future and where things are going. We then went over plans for the presentation gallery. After that, I showed him the Knox report and how that is looking. We then finished up looking at adilas and document management, PDF forms, and how to overlay data and populate PDF forms on the fly. Mostly a show and tell and light play session with code and PDF's. Hamid is interested in learning how to populate PDF's. He is going to prep a PDF for next time and we are going to work on it.

Recording notes. Hamid jumped on and we started building a mock-up for field mappings on a CSV file upload for parts/items. We can already do this, upload parts and items, but we have to hardcode each upload to fit the current corporation or company. They are all different. This new process will be a multi-step process that asks how many fields are needed, then shows mapping options, then eventually does the upload and imports the data. We didn't get to the upload part yet (we'll copy some of our other code when ready), but spent most of our session this time on the mapping stuff. I'll get to that other part later (next week).

Kinda a good learning and training process for him to watch me build something from the ground up, somewhat on the fly. We were able to chat about things before we built it, we would then make it, test it, and move on to the next part of the process. I was having fun and I think that he enjoyed it as well.

Work session with Hamid. He finished up the 12 business functions and the see more features modals and bulleted lists. See below for a list of link (see the section titled see more features per page). We also checked and pushed up a bunch of the smaller PDF's that show the business functions in a printable format. Good work session.

Sales, Inventory & POS System
Customer Relationship Management (CRM)
Calendaring & Scheduling
eCommerce
Accounting & Backend Office
Expense Tracking
Payroll & Time Cards
Reports & Histories
Business Intelligence (BI)
Data Relationships
Content Management System (CMS)
Big Data

Going forward, he is going to be working on some training in CSS and JavaScript until Shannon and I can get him some new content for the presentation gallery site.

Work session on breaking down the big PDF's into smaller pieces. Hamid was working on web modals in the business functions of the presentation gallery, and I was physically adding links and footers to the smaller PDF files. Good little work session. Pushed up files into the master branch. See attached for the 12 business function PDF's (mini versions).

Meeting with Steve to go over ecommerce stuff. Trying to debug some code on sub inventory attributes. Got stuck on some checkboxes that wouldn't work or were having issues. Trying lots of stuff. Multiple attempts. We'll have to come back to that.

Phone call with Dave Forbis. He was asking a number of questions. Lots of questions about social media connections and API's, on demand print stuff, and banks that we have integrated with (for pulling back deposits and expenses to help with bank reconciliation stuff). We also talked about old projects for campaign tracking and GPS tracking. He was looking around and trying to get things lined up. Good call.

Emails and reviewing tons of PDF files from Hamid, for the business functions, on the presentation gallery.

Working with Hamid. He had done some splitting up of a huge PDF file into a number of smaller PDFs. We started working on the sales gallery (presentation gallery) and he will be adding in additional information inside of modal popups for the business functions. His work will show up on the see more features section per business function.

Working with Hamid. We haven't met up since before Thanksgiving. We jumped back into it. We spent some time going over the sales presentation gallery and what is needed there. Hamid may help me get some new content up and moving along. Getting him back into that process. One of his first tasks is going to be splitting up a huge 50 page PDF file into 12 smaller files for the adilas business functions.

Meeting with Hamid. He needed some help with his budget tool project. We spent time deleting budget items from his little app and then being able to edit items and entry transactions. We worked through the process and lightly finished things up. It still needs some loving, but it at least works. Great little training session and mini project for him. I think that he learned a lot. Good stuff.

He's going to send me over a copy of the code and a small dump of the database files for our records. It's not ready for live production, and would need some major work, but it was a great training app.

Meeting with Hamid. Working on edit and delete functions for his mini budget tool. Mostly a work session with some training.

Meeting with Hamid. We looked at his code for a bit. He has made some good progress. He has been working on a small little budget tool. Just to help clean things up, we ended up going back to the database and tightening things up a bit. We changed some tables and column names to help it be more self-explanatory. We then went through each page and made sure that each database query was correct and functioning (with the new changes). That helped a ton. Towards the end of the session, we were populating a results table based on jQuery and AJAX stuff. It looked great. He is going to keep playing with it and we'll meet next week to see what he has done.

Working with Hamid on his budget tool. Lots of training and review on both ColdFusion and JavaScript debugging. He is trying to tackle a bunch, all at once. We are slowly making progress. Mostly a work session tonight.

Meeting with Hamid. He has been working on his budget tool project. He had a couple of different solutions (options that he was working on). We went through some jQuery code and built a dynamic drop-down, that when clicked or changed, populated a sub drop-down dynamically. Lots of training and testing along the way. Going through things line by line. Good session and good learning on both parts (his and mine).

Meeting with Hamid. He is working on a budget tool. We went through things and tried to get his local files back on track. He had been spinning his wheels a bit and needed some help. Part of that is learning. We spent the whole time going over code and team coding on his little project. I sent him a small sample of some jQuery stuff that I made for Cody. Hopefully it will help. He is going to review it later this week and first part of next week.

Meeting with Hamid. We were talking about his wife's business. She has a need for a small scheduling (salon style) software package. She really wants it to be customer facing and able to take credit card payments. They, her business and her clients, take/make a small deposit so that people don't cancel at the last minute. They need the full thing fully integrated. We talked about adilas and how we really want to do more online scheduling stuff.

We then switched over to Hamid's budgeting tool that he is working on (small mini project). We looked over his categories and sub categories for his budget tool. As a side note, he was using some sub queries in his insert statements to do the inserts and look-ups to tie the main categories with the sub categories. We ended up doing a small work session and taking his frontend code (small interface layout) and adding a few database queries to the output. Really simple stuff. For next time, we may try doing some more complicated database transactions.

Checking in with Hamid on his budget project. He sent me a small wireframe via text message, and we talked about some of his notes. He has 4 pages of handwritten notes on what he wants to do. Not a lot to show today but he is working on it. We'll hit it again next week.

Emails and light tech support. Meeting with Hamid. Got his local setup for his new budgeting project. He already started playing with a small database for his project. We setup the ColdFusion datasource and made a new page to make sure that everything works. He will be doing more planning and will present the plan next week. Just getting started on this new project.

Meeting with Hamid. He's learning and going through some ColdFuison training stuff. I gave him a small mini project to work on. I'm going to have him work on a small budgeting tool. Really simple. I also sent an email to Calvin requesting a version of his MySQL Editor for Hamid. See attached for some notes on the budget project.

Quick meeting with Cody to go over progress on the label builder. Printing a quick check for Cody. Quick phone call with Hamid, touching base. He is doing some ColdFusion training. We are going to re-meet up after the 4th of July.

Meeting with Hamid. Sent him over some older developer resources and training materials. Setup a time to meet in a couple of weeks. His current plan is to go through some ColdFusion videos and do some tutorials and training to get ready. We will then figure out a project and have him go for it (another small paid project). Right now, he is just banking some of the hours in the ship B (adilas shop) area.

Meeting with Hamid. We were trying to get his local box all setup in order to connect to a database. Installing drivers and trying to get things connected. Mostly playing with MySQL and ColdFusion trying to create datasources (database connections). We couldn't get it to work. I think that we were missing a connection or Java file. He texted me later (after the meeting) and said that he figured it out. He had to install a newer version but he got it going.

Meeting with Hamid. We did some simple ColdFusion queries and playing with the output. Light training.

Meeting with Hamid over GoToMeeting. Reviewing some ColdFusion code and getting back into the swing of things. He is interested in learning to improve his skills. We did some simple ColdFusion stuff with databases, SQL, and html. Talked about mixing languages like CSS, JavaScript, ColdFusion, SQL, html, etc. For web work, you have to mix 4-6 languages on every page (potentially). It can get deep.

Meeting with Hamid. We were having fun talking about the analogy of chasing a ball down the hill. Just for fun, we were saying that we better stay out of its way so that it does not squish us. Sometimes it feels like the ball is going faster and faster and getting bigger and bigger. Just being silly.

We spent our time looking over Bootstrap code and CSS changes. Bootstrap and prebuilt templates are pretty cool. However, you can get layers and layers deep, and you tend to find yourself going down a number of rabbit holes. Lots of moving pieces and dependencies. We end up needing someone who is good at doing frontend code (designer) and someone who is good at doing backend code (database and code developer). You almost need a small team or a buddy. It's hard to be good at everything, to a master level.

Training session with Hamid. He showed me some progress on his bootstrap training and then we jumped into an Adobe ColdFusion training session. Nothing too fancy, working on forms, URL's, variables, and simple if statements. I showed Hamid a little bit about XSS (cross site scripting) and how to help prevent that type of thing (web security for URL's and form values). Fun session.

We jumped on a GoToMeeting session and went over some Bootstrap stuff. Hamid has been playing with some themes and templates. We got into some debugging and making sure that we had all of the supporting files and folders for the themes. We also did a little bit of work on hex colors and playing with CSS code and debugging within the browser inspect screens. Small work session on playing with Bootstrap templates and themes. Good session.

I did some prep for some ColdFusion training. Once we jumped on, we looked at some bootstrap stuff that Hamid was working on. We then flipped over and did some ColdFusion training together. We will get more into it (dealing with web forms) next week.

Hamid has worked for Walmart for almost 20 years. He was talking to me about their online shopping options. He had been there long enough to see the start, changes, and current direction. Online shopping, pick-up, and delivery have been huge for Walmart. They are even doing special Black Friday type events that are only open on the online store. He was talking about how the online store is tied to your other in-store accounts and being able to help you repopulate your cart with items that you currently buy (personal purchase history stuff). We do some similar things but on a much smaller scale.

We talked about leveraging your data and helping to make things easier and easier for you to add things to the cart and get quick history or purchase history reports. That's some important data.

We are going to skip next week and then meet up the week after Thanksgiving. Hamid wants me to train him more on using ColdFusion and passing form data and values back and forth. Just for fun, we are going to work on a pizza ordering form for some training practice.

Meeting with Hamid. We went through the steps to setup ColdFusion on his local box. We got it running and did some light training and practice. We went over variables, URL scope, and lightly what you can do with the FORM scope. I then showed him some practical application on how we, at adilas, combine variables, URLs, and Forms to make an entire application. Hopefully that makes it more real as compared to just practice stuff.

Meeting with Hamid over the GoToMeeting session. Touching base and then helping Hamid install ColdFusion on his local box. Small intro to ColdFusion with things like variables, lists, arrays, and URL parameters. Small training meeting.

No meeting took place today. We sent a few text messages back and forth. Crazy times. Just trying to get some traction. We are planning a phone call meeting for next week. Everyone's schedules are pretty booked right now.

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.

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.

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 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!

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.

Touching base with Hamid. He is working on a Word Document and outline for our projects. He's going to refine it a bit and then send it over to me. He took all of Aspen and I's post-it notes and reorganized them into an outline. See element of time 10377 for the rough outline and post-it notes. Looks good. We also talked about some screen capture and video editing stuff. We setup a meeting for next week.

We had an update meeting to show progress on ship B stuff (adilas lite and fracture). We had 10 people on the meeting. We had Alan, Hamid, Steve, Sean, Danny, Cory, Shari O., Shannon, Bryan, and Brandon (myself).

We did record it. The recording is right about an hour long. The first 20-30 minutes were from Alan going over market research and tech deck decisions for fracture. After that, I introduced a new website to publish some of our work on the adilas lite or fracture project. Here are a couple of links:

Adilas Lite - Project Home - https://data0.adilas.biz/lite/

Adilas Lite - Videos & Research - https://data0.adilas.biz/lite/adilas_lite_videos.cfm

The meeting went well. As a side note, Shari O. recommended that we have a fun, non work, meeting just to catch-up and say hi and what not. She is kinda like our mother hen, for the adilas team. Fun times. See attached for some other videos and assets.

After the meeting, I spent some time uploading things and doing some light clean-up from the day. Busy day. 

The actual meeting with Hamid was from 4:30 pm to 5:30 pm. I spent the first half an hour doing some prep work. Putting him in the system as a user, assigning permissions, and recording a small video for how to record project timeclocks in adilas shop (just under 4 minutes in length).

During the actual meeting we went over how to add project timecards, different tasks, adding, editing, and looking things up. We built some quick links to help him navigate around quicker. We then talked about Snagit and Camtasia for options for internal and external training. Hamid is going to checkout some tutorials there to see how it works. We briefly talked about some of the billboard sites and options there. The other major topic was dealing with helping to refine some documents and make things more presentable. I gave him a few links to check out and we'll slowly start refining some of the pieces of the plan.

Links that I sent to Hamid

- 10,000 foot view of where we are headed... https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=10377

- More links and research stuff - master plan - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=10179

After the meeting, I did some clean-up, reviewing some Snagit files, different videos, and uploading the new video for adding subs of time.

emails, checking on some domain names, and sending some information to Hamid about some options to work on. Spend a little bit of time recording some notes from the past couple of days. Nothing too major.

Phone call with Hamid. Touching base and going over some ideas for fracture and adilas lite. We talked about possible networking options with our connections. We also spent quite a bit of time going over some tech stack decisions and talking about needs for adilas lite. We went over three main avenues. 1. Is Planning - business plans, tech documents, etc. 2. Training needs - both internal and external, and 3. More billboard sites - sites that point to adilas. We talked about banking hours and no limits as far as investment opportunities (working hours for future payoffs and percentage ownership options). Nice phone call.

Printing out some elements of time as a back-up paper copy. Prep for a group meeting. Once the meeting started, we did some small intros. There were 10 of us on the meeting. We went over concepts of throwing stuff at the wall, seeing what sticks, organizing things, Alan gave a small PowerPoint presentation (see attached). We talked about exposing the peaks, mountains and ice berg (peaks) analogy, tiered versions, pricing matrix, features & who has access, prototyping with code models, frameworks, libraries, the jelly fish model, a new mini jelly fish model, and tons of other topics.

We got into topics of growth, retention, code development, IT/Servers, and Cafe/Marketplace options. Great discussion on R&D and how R&D plays on both the maintenance side (stabilizing and making the current product better) and the growth side (new stuff and pioneering).

Spent some time talking about the SWOT analysis, lessons learned, and mission statements. This is an idea from Hamid, on the mission statement - Mission: Adilas - Build Your Solutions. We got into some user stories, scenarios, and recruiting help from the guys/gals. We talked about who wants to help and what they could do. Overall, a good meeting. We recorded it, at least the first part (first 23 minutes). It stopped recording when we switched screens and switched presenters. Anyways, see attached for some other notes, the PowerPoint slides, and the link to the video recording.

Good group meeting with a progress report on the ship B, adilas lite stuff, and fracture.

Trip to Logan to meet with Hamid. We met for lunch and talked about fracture and adilas lite. Fun meeting. Here are some of my notes, from the meeting and just driving around.

- Model out each section, similar to the virtual obstacle course we are playing with (see # 10294). It may also be fun to model it out via the plates and cups model (small way of teaching one-to-many relationships for objects).

- Focus on one part or piece at a time. If you don't focus in, it, the whole fracture project, seems way too big and massive.

- If we get lost, we could always focus on mapping out the existing core. That is a "known" and needs to be done.

- We still want to do the rest of the billboard sites (other or outside sites that lead people to the main adilas.biz platform).

- We could offer preset packages for adilas lite. We could also offer an a la carte type option, where they can mix, blend, and pick and choose what they want or don't want.

- Hamid would like to play along with us on building out the dream. He has a number of ideas that he could throw into the mix. Eventually, he would like to transition over to more technical job. Future plans. Once again, great lunch meeting.

Pushed up some files for the business zipper website. They still need a little bit of work, but I wanted to push them up. Meeting with Hamid (developer who did the site) later today.

Digital storytelling - using data and drill-downs - to tell the story. See attached for a multi page document that Shannon and I were working on (a couple of years ago). I was proofreading and doing some editing on it. Not sure why, but I was thinking about this older document and decided to reread and revamp it a bit. See attached for where I'm working at - still under construction.

Communicating with Hamid about meeting next week for lunch.

The document has an analogy of how people use a video recorder to record and duplicate scenarios and actions. As part of the analogy, it relates what adilas does in the digital storytelling to help with full world building. I thought that it was kinda fun. The document goes pretty deep. Spent lots of time rereading, adding and taking away little bits, and doing some proof reading. Only got about half way through it.

As a fun side note, I sent it to a contact, even though it wasn't fully finished. Trying to get the word out.

Final sign-off for a promotional website done by Hamid. We looked at code and I printed him out a check. We chatted for a bit and he handed me over the code for the business zipper website that he was working on. I'll look over it a little bit better and then get it pushed up to a live server to be an actual site. This promotional site was going to be kinda like a billboard that talks about a certain topic and then points the users or visitors to the main adilas.biz website. We are calling them billboard sites, a form of light advertising.

Meeting with Hamid (adilas intern) to go over his progress. He is almost done with the billboard site for the "Business Zipper" site. A billboard is basically a site that points people to another place (like to adilas.biz from the business zipper site). Anyways, he had a lot more content this time and it's looking good. This is just a fun starter project. We chatted and made some plans to get the full version up and live. I'll wait until he hands me off the files and then we go from there to review it, push it up, and have it go live. Making progress.

Meeting with Hamid. He was showing me the progress on the business zipper website that he is building (small side project). I gave him the URL for our old site and told him to read the bottom portion that talked about the concepts of the business zipper. Here is the link and some of the text (you have to scroll down to the bottom portion of the page to get to this info).

-------

Older website text

-------

Many people over the years have asked us, what do you guys do? Why do you do that? Where are you trying to go? How long does that take? How can you do such and such and others can't? And what makes you so different? Those are some great questions. The answers vary depending on the time someone is willing to listen. :) This is somewhat of an inside joke, but sometimes we feel like saying "Did you pack a lunch?", meaning it can get pretty deep pretty quick.

To answer plain and simply, we are in the business of tracking people's data. We are a virtual data portal. The word "data" means different things to different people. The word "adilas" also means different things to different people. To some it may be CRM functionality (Customer Relationship Management). To others it might be inventory, sales and POS information (Point Of Sale). To others it might be ERP (Enterprise Resource Planning) or backend office functions. To others; general operations tracking, JIT inventory tracking (Just In Time), manufacturing, online expense tracking, business intelligence (BI), paperless office, document management, a CMS (Content Management System), financial data and reports, paperwork, payroll, timecards, scheduling, etc. Because we say we track "data", we need to be as deep and diverse as the term itself.

Our goal is to help you, as a user or a company, get in, get out, and be happy. Along the way, and depending on what you consider to be data, we try to help show you the whole picture of what is going on. If what we have helps you out, great! If not, that's ok. We enjoy sharing what we have learned. The adilas.biz business platform is a huge integrated tool set that allows you to play in multiple different areas. It is very scaleable and caters to custom settings and different permission levels. Your use of the system, depends on you and your needs.

The words "system" or "platform" denote more than one piece working together in harmony. A full system allows you to do things that others can't do, simply because everything may not be there.

One of our biggest strengths is helping you get your data into the system. Once in, it becomes part of the big picture. Data coming in usually means some form of "operations" or the day-to-day business that happens. We love this and have a strong focus on helping on the operation side of the equation. We try very hard to follow a logical or linear model in helping you to get your data in and out of the system as quickly and easily as possible.

We also offer some great backend office tools and accounting features. If truth be known, the reason we are able to offer you accounting-type features is directly related to how we track your data and help you do your operations. We, at adilas.biz, are actively working on a new and more modern model for accounting as compared to the current, somewhat antiquated, double entry accounting system embraced by most companies. We can run your operations regardless if you use adilas for your accounting needs or not. If you are looking for a traditional credits and debits accounting system, we may not be your product other than for your operational needs. However, if you are willing to try a more modern and nontraditional approach to accounting, you will love what we do and where we are headed. Straight up, it is new and different and we are still pioneering on a daily basis.

Here is a little background on the traditional double entry accounting model that dates back to the fifteenth century (500+ years old). Luca Pacioli, an Italian monk (friar) wrote one of the first math text books called "Summa de Arithmetica". In that book he explained about how the Italian merchants kept track of their sales which we now call "double entry accounting". This guy was a genius and a math wizard for his time. Here is the kicker, this text book came out in 1494. Two years prior to that, Christopher Columbus, in 1492 sailed the ocean blue to show people that the world was round. People were just coming out of the dark ages and entering into the age of the Renaissance. The only way that businesses could track their "data" was in giant notebooks called journals and ledgers. They had large rooms with tons of paper copies and went through different processes of recording, adjusting, and posting their data between the different journals and ledgers. Sound familiar?

Basically, they were trying to track different states and statuses of the data. Some of the processes that they used to track these changes and states of the data were called "debits" (negatives) and "credits" (positives). These debits and credits were added to things called "T Accounts". The different T Accounts made up a bigger thing called the "Chart of Accounts". The Chart of Accounts usually had a numeric value and a name associated with it. This is how they tracked things, on paper and in different notebooks. These Chart of Accounts were then added up and used in financial documents called the "Income Statement" (profit and loss statement or P&L) and the "Balance Sheet". The goal was to make sure that everything got recorded and accounted for. In order to make things balance, they had to do one entry on one side and then a matching entry on the other side of the T Accounts. Thus the term "double entry accounting". This standard has been followed for years and is currently the accepted way to do accounting. As a mater of fact, most computer systems that do some form of accounting, have basically computerized the 500 year old model and added their own little tweaks to the process.

So what makes us so different? Well, we spent the first five years working on operations. The original goal had nothing to do with accounting. The goal was to start tracking inventory and other data. We wanted to be able to quickly view things, pull reports, and even be able to show where that data was or what had happened to it over time. Through a step-by-step approach to solving our own business problems, we stumbled upon a new way of doing accounting. Basically, once we had the operations in place (this is a big key), we just kept asking the question, what happens next? We would then build the system out to that level. As we kept going, the path began to be rolled out and we just kept taking the next logical steps. This process took years and years and was only possible because we kept working at it. Concepts that were only a dream or a wish started to be right in front of us and we simply reached out and grabbed them.

Adilas can virtually track objects and data over time without using the old double entry accounting model. We still simulate some of the pieces of that model, but we do not have any journals, legers, T Accounts, Chart of Accounts, and other standard accounting features that are considered traditional requirements. We don't use the words debit or credit and we try to use as few adjustments as possible. We use technology, good data, flags, dates, checkpoints, approvals, permissions, and business mapping to run things in a linear fashion. Every entry or data object has a life-cycle and we simply track it. We are then able to go back in time and virtually ask the objects or items questions. What's your story? Who created you? Where have you been? Where are you headed? Who are your buddies? Where do you belong? When did you finish? What is your value? And the list goes on. We call it "roll call accounting". At the end of the day, we still produce an Income Statement (profit and loss or P&L) and Balance Sheet. We just arrived there through mapping data and running objects over time.

We are still pioneering and developing steps to the roll call accounting process. We've had a blast creating it and we can't wait to share it with you! Although our accounting system is not completely finished (fully automated to the highest level), we have had many companies happily use it for years. We just keep adding new pieces that make it better and better. Remember, our main goal in providing the adilas.biz system or platform is to help you track your data. Adilas can help you with your operations, accounting, or both. The model is open and flexible.

We invite you to check it out. We would be happy to meet with you in person or give you a live online demo. Give us a call TODAY! Call 719.439.1761 and ask for Steve or email us at sales@adilas.biz.

If you want more information, there is a brief history document of the making of adilas at the bottom of the page. It is a short 6 page read that tells the story of what happened when and who was involved. It has been a wonderful journey thus far and we're still going!

Just for fun, we wanted to list a few of the core concepts if you don't want to read the history document. This is just for fun... :)

When we first started, back in 2001, our original goal was inventory tracking. As things progressed, one of our main goals was to figure out a way to help fill the gap or create a "bridge" between operations and accounting. There seemed to be a very large and visible disconnect between what was happening in the field (operations) and what the final output was (accounting and final numbers). In one of our brainstorming meetings, we came up with the analogy of a "zipper". One side of the zipper was operations and the other side was accounting. Our goal was to start bringing them together one cog at a time, like a zipper being pulled upwards until it came together.

We came up with the theory "track every penny in and track every penny out". With this thought in mind, we started to track each penny from start to finish. What we found was that every transaction had a life-cycle that it went through. We decided to enter the items and data as easily as possible on the operations side and then track it through a number of steps until it found itself finished or completed. Along the way, we started time-stamping each step with a flag and a date. Each flag and date combo became what we called a "checkpoint". As each new flag was added, we would lock the prior steps below that based on permissions.

This process of passing data from checkpoint to checkpoint, based on permissions, is how we track your data. A great analogy of this process is if you imagine what it takes for water to turn into ice. This process doesn't happen all at once, it needs to go through different phases, states, or status levels. As your data passes through these different phases, called checkpoints, we simply help you flag and date the data as it runs over time. Just like the ice analogy, the water droplets are very loose at first "operations" and slowly become crystals, then slush, and finally become completely frozen or ice "final numbers and accounting".

We then use a process called "roll call accounting" to virtually map backwards in time to where the data was at a given date or time. Another synonymous term for roll call accounting is data mapping. The reason we use the term roll call accounting is because that is what we ask the computer to do. Imagine data that is flagged and dated as it goes through certain checkpoints. Pretend that the computer is an army General giving out a roll call or a flag/status report. The computer says, "I need all of the invoices that were not fully paid at such and such a date to step forward". Only these invoices would then be counted - based on flags and dates. You could then use the computer to do the math and give you the totals you need. Each time you want more information, you simply tell the computer what criteria to use for the roll call and eventually it will tell you the story of what is going on.

To sum things up "literally", by keeping track of your normal day-to-day operations, we can get very complex results like aging, histories, usage, reports, final numbers, and accounting. Thus the accounting becomes the date sensitive sum of the details. These values are what make up your "Business Intelligence (BI)" or "Big Data" concepts. It all comes back to managing and tracking your data. Because every piece of the puzzle still exists in the database, you are able to virtually go back in time and see what was where and when it moved out of each checkpoint. If the data is correct, let it flow. If a modification is needed, make the correction, lock it down, and let it keep flowing. The accounting becomes more of a check and stamp of approval rather than entering numbers from different journals or locations. When you put it all together, what do you know... All Data Is Live And Searchable.

Touching base with Hamid, an adilas intern. He is starting to code his website project for the business zipper site. It's still pretty basic but a fun first little site. He's been putting in a little bit of time each day, working on things. This new site will end up being a form of a billboard type site - a separate smaller site that promotes a bigger site (the main adilas.biz site).

Met with Hamid to go over his wireframe for the business zipper website. This is a small side project that Hamid is doing as somewhat of an internship for adilas. Eventually, he'd like to get into some backend coding and database stuff. See attached for a couple of mock-up and wireframes.

Meeting with Hamid Karbasi, new adilas intern. He will be building a small web site on the topic of the "business zipper" and how we came up with that analogy. Hamid was referred to us by Russell Moore. They had worked together as student and teacher at Bridgerland, in the web development department. Anyways, we got on a Zoom meeting and started going over things. We did a small get to know you session. We then switched over to a small about us and where we came from orientation. I did a light intro into adilas.

We then talked about a small assignment to build a billboard site for the business zipper domain (businesszipper.com). As of right now (3/1/23) it is pointed to the main adilas.biz website. Our goal is to create a new mini site or billboard site (think of a billboard or sign as you are driving down the road that pointed you to something else). In Hamid's words, "all roads lead to adilas". I thought that was good and fun.

We have a number of other domains that we may work on in the future. All of them will be billboard sites or mini sites that point to adilas.biz or a feature or concept within the adilas network/family. We made a small plan and then I gave Hamid a number of resources, info, links, and such. We will get back together in the next couple of weeks to see how things are going.