|
Adilas.biz Developer's Notebook Report - All to All - (749)
|
||||||
|
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
| AU 1031 |
|
Daily Ideas | 12/24/2012 |
-If we give out the code, ask that the companies and the developer give credit where credit is due. This includes God above! Thanks! -I’m thankful for being able to record and write things down. Writing and reading things that have been written help remind us and expands the options. Otherwise we have to keep re-learning and we are never able to stand on other people’s shoulders (their learning, mistakes, knowledge and experiences). -From Joseph Smith – “Teach people correct principles and let them govern themselves.” What a great way to do it! -Empower the people and your users. Then let them take responsibility for their actions. This is called “return and report”. -We need to update and clean-up the help files. We could add graphics, step-by-steps, videos and other links. This could be a huge but needed project. Teach the people! The subjects come second. -Help people get inspired! -Help people see the options and take their own spin off of the vision. This could be training, niche, set-up, consulting, web, design, sales, education, accounting, distribution, etc. -Education for the upcoming generations. -Broad strokes – general sweep of business functions. -Teach people how to do dynamic searches using built-in wild cards. -Elevate the knowledge of those who are willing to learn and play. -We enjoy doing this – it has been a ton of fun. Sometimes stressful, but really fun! Every day is like Christmas! New toys and lots of excitement! -Our goal is not to balance, our goal is to show you what we have and help you balance. -Get back to mapping out the system – see notes from 10/6/10 to 11/6/10 (loose papers). Transfer that information into the steps for success. -As a general note, if you jump in, it is easier than staying on the sidelines and watching. Come on in and get some experience! It is fun! -Kind of like a buffet or self-service restaurant. -If you need help, you need to ask for it. -We can help hold your hand, no problem. We consider that an additional service and will charge for that. You can pay us directly or use an independent rep to help where ever you have a need. Those reps will bill and charge you directly. Adilas never sees that money or those transactions. That is between the reps and their clients. -We don’t have a contract. If you like our service, keep paying for it. If not, that is up to you. We want to make you happy. -I am so thankful for paths, trails, maps and roads. There have been some very kind people who have gone before us! I think that is great! -The goal is to get people to think! (For themselves) -When teaching a class or giving a presentation, request and get feedback and ideas from students. This could be copies of notes or some other kind of voluntary type of sharing. -Harness the creativity of others! Then give back in a way that benefits others. -Wayne Gretzky – “Skate where the pack’s going, not where it’s been.” Head is up and we are actively looking and planning our next couple of moves. -What are the next 3 thing we need to do? -All we need is 200 happy customers! -Think of a time line with multiple levels or lines on it. What business functions are needed for what level? What types of businesses reside or play on what level? -I went to a Christmas party and my brother-in-law had a table runner going down the middle of the table. It was striped with lots of different colors and thicknesses of the lines. I used that table runner multiple times to represent a timeline, difference industries (businesses), and different functions that run or have run over time. It was great! I’d love to use something like that for teaching and demos. -“TIME” is one of the biggest keys to the whole puzzle. It is a moving constant. Because it moves, it could be considered a variable, yet it is measureable and finite. -I’ve got pages (10-12 loose pages) that were part of the brainstorming on elements of time. Make sure and get those documents and record them digitally. -Going back to the party (Christmas party) – we used real objects to talk and teach concepts. We used cups, plates, pans, etc. -You could put pieces of paper in the cups as they moved through time. You could create bridges or relationships. You could run things together; you could create objects and run them through time. We even compared what we had (our objects) to old traditional ways of doing accounting and book keeping. Because the objects had so many pieces, it virtually broke the old model without tons of extra work. It made sense to just map back to the object and have it report what it had. -Show and use simple objects to teach object lessons, cups, cans, plates, string, paper, etc. -To push the object lessons a little further, you could even break things into smaller pieces, job functions, or virtual areas of operation (like permissions). Each person does their own piece of the puzzle or process. In the end it all comes together. -Lean manufacturing and just in time inventory functions. Similar to the above ideas but for data not inventory. -If you relate this to the multi layered timeline, you could use different lines to make or create different components and outcomes. -Everything is headed to the mobile world and mobile level. We need to make certain parts of adilas and our business model into an app or at least be mobile friendly. On the go? No, problem! -I was up snowboarding and rod the life with a guy who I used to work with years ago. On the lift rides up, we were talking up a storm and catching up. He had been a mechanic and used appliance repair guy. Anyway, we talked about tons of life lessons and learning on the job. Here were a few of the notes from our conversations: 1. Cater to your customers and don’t worry about the other guys. For example in the appliance market – was the customer looking for something new at Lowe’s or Sears or were they looking at a used item or appliance? 2. Pace (speed) – start clean and organize as you go – keep things clean. This saves time, energy and frustration. 3. Explore all options to get around the financial burden. 4. Flow, setting yourself up for success and good flow, and documenting flow, steps and processes. 5. He was talking about a good airplane mechanic and the guy would literally flag things as he found possible problems. They, the mechanics, would then write on the flagging what was wrong. If they were off or the next shift came on, the flags were literally there to help with communications. Anyway, I saw some great cross over options for us and what we do with flags. Good stuff. (General flags, dates, flex grid tie-ins, elements of time, etc.) 6. Get the tools and supplies read in advance. 7. Make a plan for the process. 8. Best practices – do it right the first time. This is a huge time saver. Even if you are in a hurry, do it right. 9. Pace – constant movement in a good direction. 10. Eliminating distractions – for example: walking away from your project to take a phone call. 11. Be candid and honest – let your customers know what they are getting. (Expectations) 12. Knowing your customers – who they are and who they are not? 13. Who is your competition and who is not your competition? This part of our discussion led to the comment and thought – our biggest competition is tradition. 14. Along with competition, what level are you playing at? 15. Time (development time) can be an asset or it can be an enemy. For example: His friend had an idea to develop a product line for teens. It took 5 years to develop. The graphics were cool 5 years ago but not when he tried to release it. However, the friend was stuck on the idea because he had, had so much time, energy, marketing, focus groups and effort into the project. The time to market was a big problem. I can see that our time to market needs a boost and an upgrade to what our clients want. We live in a fast paces world that often changes based on expectations and other outside influences. 16. Leaving plenty of time at the end! Wrap things up, test, walk around, touch and push on the changes. 17. Price point – we don’t have to take crud from people, we are good at doing what we do. 18. Map things out! Paper works great! 19. Harness other people’s work. What do they do to be successful? Mix and blend and be your own style. 20. Teach people how to use the product. This includes common features, concepts, underlying technologies, dynamic templates, dynamic searches and build your own stuff. -Some of what we do is considered “smoke and mirrors”. It is not magic; it is showing one thing while doing another thing. This helps us give the appearance of one thing while still satisfying something else. -I’d really like to go in and chop the database into smaller pieces. Then have the application code connect and join things on the fly. My initial thought were make new tables for every 25 corporations. It may be better every 10 or for each corp??? Not sure on that, we’ll see. |
||
| Adi 866 |
|
Intellectual Property Workshop | 8/21/2014 |
Brandon Moore, Wayne Moore, Cheryl Moore, Shannon Moore, and Dave Forbis attended a workshop on intellectual property in Logan, UT. The workshop was put on by the Small Business Development Center, Cooperative Extension of USU. The presenters were a law firm that dealt with patents, trademarks, copyrights, etc. See attached for my notes. What I got out of the workshop was basic information, timelines, ball park figures, and what is required. My favorite part of the workshop was dealing with how patents, trademarks, and copyrights can be denied and/or rejected. This might sound random, but I think that our goal is not to secure a patent on every little feature. Our goal is to defend patents being put on to core concepts. We need the model to be open and free. If not, it will swing power potentially in the wrong direction. So, in a nutshell, by us talking about things, publishing things, teaching, instructing, and building with openness in mind, we are helping to keep the patents out of the core of the ideas and concepts. Let people patent smaller pieces of the puzzle, that is no problem. However, we need to protect and educate people on the core of what we are doing. I have said this in private before, but I would bet that the core concepts that adilas.biz is built on are 100 times more valuable than the code that we have written over the years. There could be thousands of possible code angles on these same concepts. That is well and fine and a known fact. The important piece is protecting the core concepts and principles of what we are doing. We kinda fell into this... this wasn't our original goal. However, I do feel that we have some super important things that we are developing such as:
Anyways, those are some of the pieces that I see that we are doing and developing that could potentially be patented and/or copyrighted. They are listed here to start the process. |
||
| AU 2774 |
|
Intellectual Property Workshop | 8/21/2014 |
Brandon Moore, Wayne Moore, Cheryl Moore, Shannon Moore, and Dave Forbis attended a workshop on intellectual property in Logan, UT. The workshop was put on by the Small Business Development Center, Cooperative Extension of USU. The presenters were a law firm that dealt with patents, trademarks, copyrights, etc. See attached for my notes. What I got out of the workshop was basic information, timelines, ball park figures, and what is required. My favorite part of the workshop was dealing with how patents, trademarks, and copyrights can be denied and/or rejected. This might sound random, but I think that our goal is not to secure a patent on every little feature. Our goal is to defend patents being put on to core concepts. We need the model to be open and free. If not, it will swing power potentially in the wrong direction. So, in a nutshell, by us talking about things, publishing things, teaching, instructing, and building with openness in mind, we are helping to keep the patents out of the core ideas and concepts. Let people patent smaller pieces of the puzzle, that is no problem. However, we need to protect and educate people on the core of what we are doing. I have said this in private before, but I would bet that the core concepts that adilas.biz is built on are 100 times more valuable than the code that we have written over the years. There could be thousands of possible code angles on these same concepts. That is well and fine and a known fact. The important piece is protecting the core concepts and principles of what we are doing. We kinda fell into this... this wasn't our original goal. However, I do feel that we have some super important things that we are developing such as:
Anyway, those are some of the pieces that I see that we are doing and developing that could potentially be patented and/or copyrighted. They are listed here to start the process. |
||
| AU 2783 |
|
Brainstorming on 3D Operations and 3D Acconting | 10/14/2014 |
This morning, Tuesday, 10/14/14, Brandon and Wayne Moore were on a morning trail run. The subject was what goes with time? Brandon came up with space and Wayne came up with money. When you put all three pieces together, you can actually get 3D Operations and 3D Accounting. In Wayne's direct words... (written in an email to his friend) "I think you will like his 3-D approach to Operations and Accounting. X = Time, Y = $'s, and Z = Space." Great early morning conversation - done while running and hiking in the mountains of Northern Utah. |
||
| AU 3736 |
|
Brainstorming - GPS & 3D Event Tracking | 12/3/2014 |
Phone call with GoToMeeting session with Barry & my dad (Wayne): - Barry & my dad - GPS & CalAmp - Gpsicu.com - Esa #____ - Vehicle ID - Vehicle name - Vehicle description - Odometer - Trip meter - Speeding: o Speed threshold – ____ MPH - Idle: o Idle Durations - ____ minutes - Stopped: o Stopped Duration: ____ minutes - Mileage: - Switches: o Switch input 1 • Estimated Fuel Usage: ____ gallons per hour o Switch input 2 o Switch input 3 (PTO) – • get to subtract this back out o Switch input 4 - Land Marks o Sub locations o Inter - Histories of the truck - Vehicle id - Name - Last heard (central) - Speed (mph) - Heading (degree) - Battery (volts) - Id 1 – unit # - Id 2 – ESN # - Intervals of action - Timing - Managers look after certain subsets – assigned to certain fleets - IFA – International Fuel A____ (not sure) - Full dispatch, routes, gallons, price per gallon, reports, etc. - Google Earth - Multi-screen – quick snap shot Reports: o Mileage by vehicle o Mileage by date o Places by vehicle o Places by date o Places by place - Tell the story - Bread crumbs… audit trail - Reports as needed… - Last 7 days current, then archive the data - Hours of service templates o Driving, working, stopped, o 4 roles: • Admin • On-service drive time • Working but not driving • Sleeping o Simple time - Pulse – code the device based on what is needed – puls.calamp.com - Lots of divisions and sub division, groups - Config scripts - Phone # of the sims card - Buy here pay here - Texting, email, web, API – different communication levels - Maps - Quick visuals - Manually ping the device - Maintenance server |
||
| Adi 974 |
|
GPS, GIS, & RFID tag tracking - Sub of Time | 3/30/2015 |
First $5,000 paid in by Wayne Moore - Logan, UT. 2/7/15 Third Calvin Chipman did some internal development out to a light demo mode Fourth: Josh Sagert did a google earth simulation tied in to cell phones. |
||
| Adi 1089 |
|
Bulk Uploads for Photos, Scans, Images, Files, Media, & Content | 5/19/2015 |
Currently you can do some bulk uploads on media content. Not yet on photo section. Might change as we roll over to AWS. Photo gallery section has been revamped by Wayne. Could have some advances soon. |
||
| Shop 3829 |
|
Virtual Post-It Note | 10/15/2015 |
New sites for:
Concept based sign-off procedure-we need to build it. Reread the project management document.
|
||
| Shop 3831 |
|
Virtual Post-It Note | 10/28/2015 |
SHOP
|
||
| Shop 1766 |
|
Working with Shannon | 9/8/2016 |
Shannon came to Bridgerland and we had a small work session. We talked about progression and how to balance new vs. older more stable technologies. We also made a tech support call about a cross-browser issue with sub inventory templates. Some of those things get hard to trouble shoot because of browser differences. After that, Shannon and I went to a retirement party for Wayne Moore (my dad) there at BATC. Good stuff. |
||
| Shop 2586 |
|
Adilas Time | 5/11/2017 |
On the morning GoToMeeting session. A guy by the name of Wayne Andersen joined the meeting. He was calling from Portugal. He has been programming for about 40 years. He has written a number of applications from the ground up. For the last 10-12 years he has been in the HV/AC industry. Lots of work with time capture and time calculations. He also worked with some light job costing and then do some reporting. He has done lots of database stuff and written in lots of different languages. He is looking for 5-10 hours a week and/or a smaller project. He wants a challenge and wants to do some things here and there. He is looking to help with projects, API sockets, automated unit testing, etc. Contact info for Wayne Andersen: powertoaster@gmail.com 208-991-3205 After meeting with Wayne, Steve and I chatted about some different things and such. The rest of the session was spent doing emails, recording notes, and other small to do list stuff. |
||
| Shop 2638 |
|
Adilas Time | 5/15/2017 | On the morning GoToMeeting session with Steve. We had Wayne Andersen and Alan Williams join us for a bit as well. We got Wayne introduced to Alan and then got Wayne setup with a bit bucket and adilas account. We chatted there for a bit and then moved on. Steve and I went over some finances and then worked on our own projects. Right towards the very end of the session, we had some issues with the data 1 and data 3 servers. Spent some time on the phone with Steve, Kelly, and tech support. | ||
| Shop 2652 |
|
Adilas Time | 5/23/2017 |
On the morning GoToMeeting session. Wayne Andersen popped in and we talked about general files and folders and a general overview of the file structure. He was working and looking around. He had some good questions. Steve and I worked on some small elements of time stuff tied to sub inventory. We are just barely touching the surface of what elements of time could do for countless projects within adilas. I'm excited to see what happens there. As a fun side note, Steve was talking about how we could use elements of time to virtually create our own little sub processes and create our own timeline with checkpoints and process pods (user-maintained mini groups, pods, and processes). We would really like to define that for things like the concept of the digital data assembly line and such. Shawn and Steve got on and worked on Steve's new laptop. They were messing around with the display settings and screen resolution. I then started to jump back in on the planning part of the mini conversion project. I spent some time recording notes from post-it notes into the system. |
||
| Shop 2771 |
|
Adilas Time | 6/14/2017 |
On the morning GoToMeeting session with Steve. Wayne from Portugal came on and asked a couple of questions and we got him all set. Steve and I then took most of the rest of the session and talked about budgets, commissions, expenses, and other internal things. Here are a couple of notes from the meeting: - To do: Change the max commission rate to 20% vs. the up to 40% for tons of accounts. This is on the adilas career & job opportunities flyer. We haven't had anybody get up to the 40% rate as of yet. - Help people pay online if they owe us money... let them know and give them a login (virtual or real)... let them pay for things online. - We ran some light budgets and came up with some benchmark goals. If we could get to 50K per month we could keep all of our current players in play and happy (minimum). If we got up to 200K per month, we could hit some special caps and magic numbers for the different players. See attached for a small file that we were playing with for some numbers. - As of July 1st, 2017 - We will start charging the developers for time with Brandon or Steve. We need to lightly cut the strings. We are thinking of 1 hour a week free per developer. Then $50/hour for other time working with Brandon or Steve. - We really need to get to a level where we charge for data storage, bandwidth, and files (media/content and photos). Currently our pricing model is somewhat of a guess or stab in the dark. We need to base it more off of what we are doing for the clients. - We may want to increase the amount of adilas time that we dedicate and put on the schedule. We are thinking of claiming 5 hours a day vs. the current 3 hours a day. That will help push the ball forward more. - On taxes and tax calculations... we may want to go up to 10 custom tax fields. We currently have 5 custom tax fields. We want to increase it a bit and expand the number of decimal points as needed. There seems to be a small bubble that is rising in the sales tax area... We need to look into that. Overall a great meeting. We got a bunch of things done and felt good about the progress and discussions. Good stuff. |
||
| Shop 2774 |
|
Adilas Time | 6/20/2017 |
On the morning GoToMeeting session. Wayne Andersen popped in and we talked about the goal and vision of the company. We rolled through a ton of ideas about corp-wide settings, dynamic naming, custom code, special wire jobs, real in-line extensions for database tables, flex grid tie-ins, static vs. dynamic, etc. We then talked about some financial pieces and such. About that time, Eric popped in and Wayne and Eric were talking about things. After that, Steve and I moved into a session to work on the tax expansion project and sales tax re-write. Getting organized and re-reading the notes and making the plan more solid. |
||
| Shop 2853 |
|
Adilas Time | 7/12/2017 | On the morning GoToMeeting session. Wayne Andersen was on and we talked briefly about a time for him to do a demo for Steve and I to show us some frameworks and how some of that could play in as we roll forward. The rest of the session was used to do emails, light tech support, record some bills, and make a small tweak on how the customer queue sorts its records based on sub queue filters or a request to see all records. Minor things. | ||
| Shop 2870 |
|
Working with Wayne | 7/14/2017 |
On a GoToMeeting session with Wayne Andersen (chiming in from Portugal). Steve and I were on the meeting. - CF Wheels framework - Model view controller strategy - A model is specific business groupings (say our 12 main players). - The view is how the pieces show up and/or be displayed. - The controller part is the logic and/or rules for each section. - Object oriented programming - Inheritance - Beefing up the actual methods and frameworks to have all of the custom validation on the methods themselves. - Using the database to help populate and drive the page layout, display, logic, validation, etc. As you change the database, the page automatically flexes and rolls out the new fields and values. This could even help us run the custom logic and pieces. - Think one-to-many on code, logic, functions, display items, etc. - Getters and setters - playing with smaller pieces. - Using a related folder structure vs. page names. For example: a users folder, customer folder, invoice folder, etc. Currently, the page names hold the underlying things such as add_edit_customer or invoice_home or view_cart. - We are getting more mature and are seeing more of what is going on. We could really plan and lay things out better and better. This is the nature of the beast. - Noodle code, sprawl, and custom add-on's - currently, we have code all over the place and have tons of different developers working on different pieces. We need to reorganize and plan things out more fully. We then, at some time and/or while we are running, will need to do a full re-write and then make that transition into a more robust framework. - The more we go into an object oriented framework, the easier it will be to help train and bring on new developers. That is huge... Right now, we spend months and months trying to bring on new developers and trying to help them find their way around. Imagine if we could bring them in, get them oriented, and then help them get in easier and do their job. - We will still need to allow for custom code, custom display, and custom logic, but we could really benefit from a standard framework. One of our goals is to become a full on platform that others could build off of, duplicate, extend, re-use, re-purpose, and/or consume as needed. - We want to provide our users with their data... that could be web, html, csv, excel, xml, json, pdf, etc. We have tons of critical data that our people need. It would be so cool if we could provide any data or data tables or tabular data in all kinds of ways at the click of the button. As far as the data goes, it is their data, we just need to allow them to get it and provide it in as many ways as possible. - The look and feel is huge... many of the sales start right there. Some people don't even look past the cover to see what we have under the covers. We need to change the appearance of what people are seeing. In some ways, we have been lightly hiding. We may need to come more out in the open. We need to keep the logic and view on separate layers. Right now, we have a number of files that are intertwined together. We need to somewhat break things apart and allow the logic and data to be on a separate level than the display. - If we use a framework, we are using some existing pieces that already exist and then we get to leverage those functions how we want. We could really harness that and it would save us tons of time. - The API layer (application programming interface) is huge. This is the path to the data. If you make it so that you use the API for all of your calls, it makes it really strong. Currently, we use the same methods but internally we use native ColdFusion. Externally, we format things into XML and JSON and run our methods through other pieces. If we used the same thing for both... It would be very stable and a well beaten path because we are using it all the time. Currently, it is lightly coupled but it is separate. It would be really nice if we could tie things together. - We want our more senior developers to work on this project. This is not for our beginner and/or junior developers. We need to make it stable, good, easy, etc. Totally possible. - Steve would love things to go toward the gaming level. Full on interfaces, levels, characters, worlds, etc. Virtual environments, custom interfaces, and showing real-time data tracking. Take real processes and then simulate them in some kind of a system. Similar to the idea of harnessing our users clicks and navigation patterns. What if they could help us do the things we need to... Take real actions and turn it into science and/or data management, internal processes, warehousing, etc. Great meeting and some really fun progress. Good stuff. |
||
| Shop 2873 |
|
General | 7/15/2017 | Working on some small tweaks. Paid some bills, ran some reports for payroll commissions, and made a couple small code tweaks to files that I was using. Uploaded new files and did some light testing. Sent off a custom data upload project to Wayne in Portugal with some details and information. Trying to clean-up my to do list. | ||
| Shop 2856 |
|
Adilas Time | 7/18/2017 | On the morning GoToMeeting session. Wayne checked in and showed us his progress on the QuickBooks checks data import. He is pretty good at that stuff. Fun to see what he is doing and how he is doing it. After that, Steve and I looked at our outstanding projects that are in the works and just made some comments on the state and status of those projects. We then jumped into a work session for the sales tax expansion project. More work on in-line dollars off discounts. | ||
| Shop 2858 |
|
Adilas Time | 7/20/2017 |
On the morning GoToMeeting session. Wayne Andersen checked in a number of different times. He was showing me some code for his first data import of QuickBook checks and expenses for a client. There were over 1,300+ expenses, and some with multiple line items. We had to tweak some code just a little bit here and there and then ran things live. It looked good. In the meantime, I was working on the advanced add to cart javascript to help with in-line dollars off discounts and new tax settings. |
||
| Shop 2892 |
|
Adilas Time | 8/1/2017 | On the morning GoToMeeting session with Steve. We started out and did some JavaScript tweaks for a report that Steve was working on. He needed to flip some hidden values when a certain button was clicked. We then worked with Wayne Andersen on a digital export and import for customer invoices. We looked over some of his code and helped him get things prepped and ready. I then did some basic to do list stuff and then started back on the JavaScript for the advanced add to cart and the in-line dollars off discount stuff. This is part of the sales tax expansion project. | ||
| Shop 2893 |
|
Adilas Time | 8/2/2017 | On the morning GoToMeeting session with Steve. Most of the day was a work session on the sales tax expansion project and in-line dollars off discounts. Still working on the advanced add to cart page and all of the JavaScript to make everything work. Towards the end of the session, I helped Wayne run our first invoice data migration project for a client. Everything went really smooth and well. Good stuff. | ||
| Shop 2903 |
|
Adilas Time | 8/14/2017 | On the morning GoToMeeting with Steve. We got caught up on some of the happenings over the last week or so. We then went through and fixed a couple of outstanding bugs and things that needed some loving. We ran some stuff for Wayne to wrap up a data import project. We helped out Eric with a customer queue question. Other than that, we fixed a few things and worked on emails and such. | ||
| Shop 2914 |
|
Adilas Time | 8/21/2017 |
On the morning GoToMeeting with Steve. We were looking into some sub inventory bugs and how to help prevent any cross-corp contamination of the data. We are having users with multiple tabs and multiple windows that are flipping between the corps. We just went in and added some validation to help make sure that all of the data comes from the same place. Part way through the session, Wayne jumped on and we went over his newest data migration project for PO's between corporations. We also did a small training session on the flex grid and how that all works. Good session and Wayne picked things up really quickly. I can tell that he is quite sharp. That is exciting. Steve and I finished up our tweaks and changes and pushed up new files. We did some testing and also talked about how browsers and sessions worked between multiple tabs, multiple windows, and even multiple browsers. We stopped in time to go out and check out the solar eclipse that is happening today. Good session. |
||
| Shop 2916 |
|
Adilas Time | 8/23/2017 | On the morning GoToMeeting session. I looked over some corp to corp migration tools that Wayne was working on. I spent an hour making comments and doing light tweaks. His stuff is looking good. I entered some expenses and then rolled into other projects. I got back on the sales tax expansion project. Still working through the differences between in-line discounts and standalone discounts. Lots of testing on the advanced add to cart page. I think it is getting pretty close. | ||
| Shop 2982 |
|
Adilas Time | 9/7/2017 |
On the morning meeting with Steve, Alan, Wayne, and I. We started out talking about needs on servers and database stuff. We then touched base on some other projects and just chatting here and there. - Wayne has been spending some time thinking about options and such. - What are the goals and what are we trying to accomplish? 1. a better, cleaner, more modern type interface. 2. a more efficient and faster database model. 3. simplifying the code and doing some clean-up to make things easier and more efficient. Think more along the one-to-many type model. 4. present a full featured API socket set - Lego type building blocks and ability to mix and bled to make custom solutions. - Currently we have business logic, database code, and look and feel all mixed together in the same page. Some pages and sections really mix things - almost to an unrecognizable level of what is what. - CSS is a very easy way to change the look and feel. This could be even set more per corporation than it already is. - Model View Control (MVC) standard. This has three different pieces. You have the model, the view, and the backend controller type functions. The model is an object of some kind. Often the model is related to the database structure. The view is what you see (HTML, CSS, JavaScript, graphics, etc.). Keep this as simple as possible. The controller piece takes the action and/or data and does something with it. These are the rules, the logic, and the decision making pieces. Basically, somewhat of the traffic cop helping to control flow, decisions, and traffic. - Helpers that help with the views... visual displays that show the users what things will look like. Virtually, they see what they will get and help with the sorting, show/hiding, verbage, aliases, data types, rules, etc. We would love to create custom tags to help build the forms and report output. Maybe think along the lines of cf_some_custom_tag. - If we build these custom tags (for building HTML and other visual displays) but we still want the final output to be customizable. - We use the black box customization options all the time. We want to maintain that ability. We could have multiple different builders and/or helpers. In the end, we really need to allow for the dynamics and customization. - How do we go from custom one-off number 1 to a base class or standard feature. This will happen over and over. Someone will have a great idea and build it out as custom. We then get other requests and eventually we want to make it a standard feature and/or option. - On the class models... we start out very broad and then start branching out as we get lower and lower in the structure. The deeper we go, the more specialized we need to get. - Usually there is a main controller and then smaller sub controllers. These could be the different actions and/or functions that could take place per model and/or object. The controller level is where you put the input validation. The controller helps validate the basic requirements. Does this data fit what is needed (super basic and/or generic validation). The model needs to control the details of that transaction. - We need to make lists of what is required and what is optional per model (per object - say each of the main 12 players). - We need to document the database, the data types, the field names, what they need, and what they require. We have started this, but it really needs to be pushed. This will help all parties. - In order to start this... you first start with a goal and then you start building the smaller pieces that will be required. Look at individual pieces and then start applying things as soon as possible. It is not recommended that you globally take over everything. Log and pick your battles... Maybe even take an inventory of what we have and then figure out where the hottest pieces are and work there. - Consistent automated testing... We keep running the tests until everything passes. As new changes happen, we rerun all of the consistent automated testing. This will help with consistency and debugging. Wayne was saying write the tests and then code to the tests. Slowly put test coverage that keeps testing other pieces as it goes out and expands. Basically, instead of testing individually, we test as a general coverage or more of a blanket type feel. This increases confidence and stability. - Taking the version control programs and such even further. Taking it clear to the test, build, test, and deploy to production. We are over writing each others code... who has the last cookie. Some of the developers have too much access to the system (FTPing files). - We could also code in teams and do some peer reviews. Currently we are still in the wild west and shooting from the hip. - This is all part of the growing process. - Setup the models based off of the database data per model. Basically, we document the model in data that could be given to all developers. That helps us have a standard piece that becomes the master plan and/or design. There are all kinds of layers within these pieces and objects. We have data layer, service layer, logic layer, etc. - This is kinda funny and silly... but Steve back on 6/22/17 said we should call our company "Fracture". Everything keeps unrolling and going deeper and deeper into subs and sub functions. - Currently we have methods that we use internally, methods that we use through API sockets, and methods that we use for custom code. We then have to maintain multiple sets of code which may or may not get updated. That flows back into the consistent automated testing and making sure that everything still works and runs correctly. It is amazing to see how everything is truly a system and integrated model. - The software maturity level. Eric would like to see things work towards a higher level. We don't want to get this high, but a level 5 maturity level is what NASA runs at. Jumping up those levels takes time and a good team. The higher the level, the more the cost and the slower things go and flow. Eric was saying that maybe we should check things out and then shoot for a level that looks good for our company (say level 2 - just off the hip number as an example). - We may be able to do some performance changes and then all of our servers are doing so much better. Currently, we keep adding more and more servers to get the performance we need. We need to find the balance between database optimization, code, and hardware/server technology. We will need to mix and blend as needed. We may need to get to a clustered server model and/or look into other options. |
||
| Shop 3035 |
|
Adilas Time | 9/25/2017 | On the morning GoToMeeting session with Steve. Doing some catch-up from over the weekend. Wayne came on to ask a couple of questions. Then back on the sales tax expansion project. I was working on testing the add to cart page and logic. Lots of new changes afoot. Lots of testing and test cases. Eric jumped on and had some questions for Steve and I. | ||
| Shop 3050 |
|
Adilas Time | 10/3/2017 |
On the morning GoToMeeting with Steve. We were talking about how quickly we could do a patch job for mini conversions. This is just a quick patch, not the real deal. Basically, you could create a new small table. The new table would have an auto id, a corp id, and the stored QR code value (text entry with a max of 50 characters or a varchar field). The QR code values would be in this format: qr_7777_77_7777 where it follows this pattern: "qr_subId_price_weight". The new table would use the auto id as the new barcode value. We were talking about the ^ (carrot sign or symbol). Say something like: ^27 or ^3555. The barcode would be that value. We would need a special page to take off the carrot and then look up the QR code value. It would then translate what was needed and pass it to the normal QR code page that Steve and Danny created. This is a simple way to use a standard barcode (smaller than 15 characters) and have it do the same thing that a 50 character QR code could do. The other things that were important were which pages to add code to help intercept the barcode searches and what pages to put links out to the new barcode generator. Steve took some notes and some screen captures of what we needed to do. Bryan Dayton and Steve will be working on this project. Both have already done some prep work and such. Steve built the original QR code page and Bryan has a small JSON object solution for storing and looking things up. The new patch would be to take that (both Bryan's and Steve's) code and make it into a new small mini table and a couple of pages to get the job done. We also talked about a number of other fun things on the horizon. These are just some small notes to help us remember what we were talking about. - We are excited to be working with Calvin and seeing what kind of fun internal 3rd party pieces we could come up with. We could do a texting service, bulk labels direct from adilas, exports to CSV files, and even getting back into GPS stuff. We talked about a bunch of options and even lessons learned from past projects. - We've got Alan back on with the database project - We've got Wayne working with the new frameworks and model view controllers (MVC's). - Bryan with custom projects - Russell with other projects, design, internal and project management - Nick small black boxes and icon menus - Steve made a comment that we already have a great popsicle. We just need to make it easy by putting it on a stick or on a popsicle stick. The easier we can make it, the better. It needs to have tons of functionality built-in behind the scenes... if we can make it look and feel easy, then we really win big. Keep it simple and easy. - Another comment that Steve made as he was talking. This one came from Kelly Whyman, an adilas consultant. "The sales taxes and tax pieces must be like the nervous system in the body... it goes through everything." We loved that the comparison was to the body and how things work. Wayne Moore (Brandon's dad) has made similar type analogies comparing body system to internal adilas systems. You could make some analogies that way. Think of the skeletal system, the nervous system, the digestive system, the endocrine system, the whatever system... It could be really cool to take it out to that level. - Steve was also saying that the key to keeping things going is delegation and training. We then let each person keep improving their own processes and such. - One other topic was dealing with possible look-n-feel/functionality of a one pager with multiple feeders, tie-ins, and even asynchronous loading and variable visual displays. Think of dashboards, drill-downs, charts, graphics, placeholders, movable pallets, expanding windows, etc. Thinking about future options and where we want things to go. Good session and lots of fun ideas and such. |
||
| Shop 3102 |
|
Adilas Time | 10/16/2017 | On the morning GoToMeeting session. We took care of a few loose ends and then started working on our different projects. Wayne from Portugal checked in on some data migration stuff and most of the session was just a work period. I was working on Shawn's dynamic percentage withholdings for payroll. Steve was doing other projects and checking some code that he and Bryan did for the new barcode values that allowed the users to enter a QR code value but use a simple barcode to access it. Pretty creative. | ||
| Shop 3105 |
|
Adilas Time | 10/19/2017 |
On the morning GoToMeeting session with Steve. Wayne Andersen popped on and we talked about object oriented ideas and options. We talked about new getters, setters, objects, underlying logic. I told Wayne that we really wanted to focus on "running all objects and data over time". We talked about time pods, checkpoints, permissions, wrapping everything in a time based manner, and data assembly line concepts. I even jumped in to the photo gallery that Russell created for me to talk about some of the concepts. Wayne is working on a global import tools from QuickBooks. He wants to be able to set a known cost and allow the users to use a super cool import tool that already knows what to do and how to work. Pretty cool idea and Wayne is on top of it. After Wayne left the meeting, Steve and I were talking about - The way we are joining parties and persons together. We are having fun working with and watching how our business model is playing out. The concepts of the bee hive, company trust, and pushing things forward as individuals that are formed into a loose group and/or team. As part of our conversation, we were talking about and asking questions such as: What kind of people do we want to attract? What are their strengths and virtues? Our only competition is "tradition". Russell's word "Dependables" - this is what our people are to adilas or to our company. A dependable could flex in and out (say like a break or a vacation) and then they come back and help push things forward. They are not an employee, they are a dependable. After that, I started working more on the edit paychecks and payroll functions for the new dynamic percentage withholdings. |
||
| Shop 3109 |
|
Adilas Time | 10/26/2017 |
On the morning GoToMeeting session. We started out by talking about updates and getting Alan to help with the sales tax expansion project. We got him online and lightly ran over the project. Wayne Andersen came on and we went over some new getters, setters, and customer object stuff. He is working on his QuickBooks import tools. They are coming along and he is making some good progress. We then got on a conference call with Paul from Green Stock - Supply Track Chain Software. Chris Johnnie was also on the call. Here are some rough notes from the call. - We still need to fix the sales tax issue for Canada. Each providence gets to decide what they want to do. - The tax revenue is the key. Each entity wants to get their share. That is a huge driving factor. It affects inventory levels, sales, receivables, payables, and other accounting branches and pieces. - We talked about training dollars and having states, counties, and providences help pay for that - they are willing to throw monies in that arena. - The sales tax expansion project is at the top of our list to get done. - Funding monies and who gets what and how do we book things? - We don't have any zones (talking about adilas sales). If you set things up, you could service leads from any area - Spain, Canada, US, etc. - Being able to create jobs. That is a big hot button for government agencies. If you spun up an instance of adilas in Canada or some other country, you would be looking at over 100 new jobs in IT, consulting, sales, training, setup, etc. - We have been rolling out tons of new interface enhancements, custom code, features and functions. - Adilas has an independent model. We need more people and/or teams who want to play. We talked about a 30% overall profit margin to help estimate costs and such. We talked some commissions, numbers, and setup fees. - The new servers need to be setup in a cluster type environment. We need data servers, content servers, etc. - Consolidated reporting to government agencies. If you have all of the data in one place, you could really create a very customized system. Think of the power of having one system doing the whole thing. You would still want checks and balances, but you could really cater the whole thing to be whatever you wanted. - Steve pitched an Adilas super training facility - in a major city - people come and get trained - they bring money in - it provides jobs - and brings people to the major cities and such. The major cities have restaurants, hotels, air ports, transportation, etc. Towards the end of the meeting, we got a hold of Alan and recruited him to help me with the sales tax expansion project. He will start Monday and we'll tag team it. After that, I spent about half an hour doing emails and trying to get updates out to other parties. |
||
| Shop 3110 |
|
Adilas Time | 10/30/2017 |
On the morning GoToMeeting session. Wayne popped in and we worked with him on some migration projects and his QuickBooks import/export tools that he is building. I then worked with Alan and going over the sales tax expansion project. This one is pretty big. Helping Steve get his git and bitbucket branches merged in and updated. |
||
| Shop 3154 |
|
Adilas Time | 11/1/2017 |
Morning GoToMeeting session with Steve. We met with Wayne about defaults for the parts or general inventory table. This is for imports of general items (part numbers). We met with Alan about questions on the sales tax expansion project. I then started to do some planning for sub payroll project for Beaver Mountain (see EoT # 3197). Towards the end of the session, I was talking with Steve about using elements of time to help track the _z axis and sub phases and sub locations. The _z axis deals with space or layering type details. What happens to something inbetween or as it goes from stage to stage or phase to phase? Does it move, change, morph, expand, contract, build, destroy, etc. We also talked about some requests from a client dealing with their specific needs and processes. See attached for a copy of the email. It is requesting some help with the PO process and basically asking for the _z level tracking options that Steve and I were talking about. |
||
| Shop 3167 |
|
Adilas Time | 11/27/2017 |
On the morning GoToMeeting with Steve. We had Wayne Andersen from Portugal pop in and ask about some invoice field defaults. We then worked on fixing a bug we found last week. I ran an update page on all of the servers to flip a few inventory types around. I paid some bills and then went back to merging code for the sales tax expansion project. Small side note, we did talk with Wayne a little bit about business objects and setting up an internal project queue of sorts to help us manage our own projects and what not. I'll be we can use the existing queue and sub queue system with minimal tweaks. We could tie it out to elements of time and go from there. Great idea and we just need to do it. |
||
| Shop 3231 |
|
Adilas Time | 11/27/2017 | On the afternoon GoToMeeting session with Steve. We mostly just did a basic work session. Wayne Andersen popped in and we helped him setup some new local corps for testing. He is working on custom database updates and data imports. The remainder of the session was used merging code between projects. | ||
| Shop 3437 |
|
General | 12/30/2017 | Chatted on the phone with Wayne Andersen about a data upload and migration project. Then back working on the year end forms and such. Pushed up new forms and did some testing. I then made a couple small changes for Beaver Mountain and opened up the duplicate time or setup reoccurring time pages and looked over code. I would love to get back on that project. | ||
| Shop 3370 |
|
Adilas Time | 1/2/2018 |
Morning GoToMeeting. We got on and Wayne, Steve, and Calvin were on. Wayne had some questions about some data migration projects. We helped him out and then Calvin gave a report on some of his projects. After doing some emails and such, I started to work on the stock/unit portion of the sales tax expansion project. We are trying to get it all done by end of the month. We still have quite a ways to go. Towards the end of the meeting, I was helping Steve with some dynamic gram tracking for his corp-specific cart mini's. We spent quite a bit of time going over the logic and how the dynamics convert into real values. His stuff is pretty complicated, but he is doing quite well. Good stuff. Around 12 pm, Calvin jumped on and had some questions on some of the reports for the sales tax stuff. We got him pointed in the right direction and he reported in on progress. |
||
| Shop 3381 |
|
Adilas Time | 1/10/2018 |
On white labeling... we need to set up our own company as if we were one giant white label. Think of the options for ski areas, campgrounds, nurseries, trailer dealers, insurance agents, law firms, toy stores, bowling supplies, etc. We could do special interfaces and custom themes for waste management, hazmat, agriculture, restaurants, deli's, hair salons, motor sports, you name it. Our goal is going to be providing the underlying platform and system to support these different white labeling options. That is where we need to keep heading. Good stuff. Working with Steve on the morning GoToMeeting. We had Wayne and Eric pop in at different times. We have a lot of great people working with us. Most of the session was doing individual projects. Steve was working on his plant phases and sub phases stuff. I was working on the main elements of time page. I added in a general text filter and worked on the next month and previous month buttons to allow them to go on and on forever in any direction. We also talked about helping our developers with ideas and direction. If they get a big project, we want to put in our two cents on how things could and/or should work with the system as a whole. We don't want a ton of small band-aid type projects, we want the whole thing to work as a platform and cohesive system. anyways, we chatted about options to help our guys out and even pushing monies their way to help it all tie-in together. |
||
| Shop 3497 |
|
Adilas Time | 2/6/2018 |
Working with the guys on the morning GoToMeeting session. Steve showed me a bug with scanning custom barcodes. We then started working on the scan QR code page for custom barcodes and custom QR codes. We did some major clean-up and also added a store/location filter. Steve and Alan were talking about keeping data updated with outside 3rd parties and making a custom database to catch and sync up the grouped data. We then talked briefly about getting everybody off the bus and only adding corp specific tables as needed. There is a lot of coming needs on splitting up the database and doing our world building project. We then did a GPS demo with Wayne Andersen. We are seeing more heat there and things are getting excited in that area. After that, Calvin came on and we talked about some GPS stuff and progress on his other projects. We ended up talking about mobile apps, cell phones, GPS tracking, RFID tag tracking, and options on those fronts. |
||
| Shop 3532 |
|
Adilas Time | 2/20/2018 |
On the morning GoToMeeting session with Steve. We started out and paid a number of credit card bills. We paid them off in full. This is a huge step for us. We have had some credit card debt since 2013. Boy, that feels good to get rid of that. Good stuff. Alan and Steve were working on some bugs on Leaf Data pages and I was paying bills and such. We then chatted with Alan about progress on the sales tax expansion project. - Wayne Andersen - Failure is an opportunity. - Wayne Andersen - If the big thing that you are trying to accomplish, can be done in your lifetime... you are thinking too small. |
||
| Shop 3535 |
|
Adilas Time | 2/26/2018 |
Joined up with the guys on the morning meeting. Steve, Russell, Alan, Wayne, Calvin, and I all participated at different times. We started out with Steve and I working on some code. Then Russell came in and we worked with him on some look and feel direction. We want him to focus on the frontend and what we show to the customers and/or potential customers. This deals with new and updates, list of features, and some of the marketing and packaging of the items. Russell pitched a couple of ideas and we listened and then came back to the frontend look and feel stuff. He would love to add some live chat options, email forms, automated settings, and other cool features. He also showed us a cool and simple task management system that he was working on for some training. Alan and I touched base on some projects and then got back to work on what we were doing. Alan is working on both the sales tax expansion project and finishing up some Facebook integration for Campaign Rise. Wayne had some questions on database stuff. Later on, Calvin had some questions on info that he is collecting from Caisson Labs. Lots of good progress for all of the guys and things are moving forward in a good manner. I ended up using the last couple of hours doing emails and tech support. We had to call a couple of clients and go in and checkout some of the code and what not on the data 9 server. Basically, the whole morning was bouncing around and jumping from here to there. It must be Monday. Yee haw. |
||
| Shop 3563 |
|
Adilas Time | 3/1/2018 |
Notes from the morning GoToMeeting session: - Steve and Alan - working on the Metrc API - Wayne showing us some cross corp migration stuff - data tree and checking cross corp - Remote datasources on dedicated servers and updating firewall rules - Test bed from data 3 to data 7 - support ticket - Have Alan and Wayne work on the world building project - Unit testing - testbox - data access object - real SQL calls (database) vs mock data result objects - mixing functions and DAO's (data access objects) - Basically we need to separate things out between data access and other code logic. We also would like to be able to simulate data. - We have thousands of functions to change... the good thing is that we will do one function at a time vs doing everything. - If we keep going as we are... we will keep getting deeper into the spaghetti bowl. If we want to make things stable and easy to update. We need to start and revamp things so that things get planned out and setup unit testing and stability along the way. - This is a change for the long run. As we do it, more opportunities will pop up. - As we make things more module, we will open things up to possible future changes. This could be changes in the database engine and/or even backend code such as ColdFusion, PHP, ASP.net, Ruby, etc. - If we get a good model and/or sample section (set of pages and/or code section), we could help train the developers that we are headed into this new methodology. - Wayne is building things out right now but is looking for ideas, critiques, and feedback. What we are looking for is a bigger company buy-in. - We talked about cleaner code and actually having our guys like it more because it is easier and cleaner to look at. In Alan's words... I (me) am kinda scared of code that looks to scripty - kinda funny. - We will breaking things into smaller, cleaner, more re-usable code. - Evolve or die - We can still get quite a bit of mileage out of ColdFusion. We just need to slowly move more towards an object oriented system and code base. Once that happens, it may make a transition easier. Take one piece at a time and keep things focused. - Alan and Wayne really think that a testing framework needs to be in place. We have so many players, we really need to make sure that things are stable. The goal is confidence and agility. - Copy and paste introduces the most number of errors. - Get some good people together and keep refining things. - Maybe Brandon and Steve will be grounded from doing the primary coding - They could do all kinds of different things. We are happy to walk behind the guys who know and hold up the banner that they suggest. We are ok giving up some of those key pieces to allow others to grow and lead out. - Steve loves to do the sales stuff and tackle other business verticals. He would love to be an advisor to help with look and feel, usage, and even the code side. But playing more of an advisor type role. - If we went more toward object oriented programming, we could reduce the number of duplicate sets of code and start standardizing things better. It would also help us organize things better into one place vs spaghetti coded throughout the entire system. - Wayne is seeing the long-term vision on the coding side. - Russell is seeing the long-term vision on the user interface side. - Alan got a charge from Steve - Alan, lead the way and we'll follow. - Russell gave Steve and I a demo and showed us some new changes. - Being positive and persistent helps us keep going. By small and simple things, great things are brought to pass. - Training sessions and being able to charge for that. - We talked with Russell about promoting more of our model and helping to get that information out and available to others. We also talked about the news and updates and helping people know and understand about the concepts, models, features, advantages, and benefits of using adilas as a business platform. - On the media/content, we want to upload things one time and then being able to reference and/or connect things without re-uploading things every time. Russell did a small demo of how he has a virtual gallery of images and he could just click a button and say set as a picture. The code behind the scenes, takes the existing item that is uploaded and just links or references that same image and/or file to the other location and/or page. Just a good way to help upload once and use many vs uploading new every time. - We talked about page modes and page views. Lots of talking about charts and graphs. We also explored some fun options dealing with CSS, themes, white label options, etc. - Ideas kept to yourself die... they need light and expression to grow and thrive. - Calvin popped in and did a light report on capturing GPS stuff over a cell phone. He has been tinkering around. Tracking and distribution stuff. Steve would love to get some kind of a GPS demo put together so that we could start marketing and trying to get interested parties to know what we have and where we could go. - Working on what you want to do really helps you be motivated. |
||
| Shop 3570 |
|
Adilas Time | 3/6/2018 |
On the morning GoToMeeting session. I spent some time doing emails and paying bills. Wayne jumped on and did some presenting on object oriented stuff and data access objects (dao) models. He wants to setup a meeting and do some show and tell for the guys. Kind of a meeting to get some direction and what not, as well as get some buy in on what is going on with some of the changes that he is making. - On the object-oriented programming stuff, Wayne liked the analogy of virtually asking the objects questions. They then respond with already known answers and/or knowledge. This requires that the objects themselves have all of the data and logic, built in to them as the objects. We don't want to burry additional logic out further in the application. If the objects can know and understand everything from the get go, it just becomes easier. If we want some data or output, we just ask for it, and hopefully we have already formatted it and/or have it ready for quick output vs running additional logic on the output and/or answers. Anyways, that is the analogy. |
||
| Shop 3571 |
|
Adilas Time | 3/7/2018 |
I logged into the morning meeting and then started working on different things. Lots of emails and tech support stuff. I chatted with Russell over GoToMeeting and we just touched base on a few things. I did some more emails and changed the adilas shop over to the snow owl theme. I wanted to be able to use the HTML editor to keep the notes and such looking better. Later on, Alan popped in and we chatted for a little bit. I showed him a brief outline of what we are planning on doing for the revenue sharing stuff. He seemed to be ok with that. I also spent some time and did a group email to invite different parties to the preview meeting tomorrow with Wayne Andersen (object-oriented programming and data access objects). Recording notes and doing some other clean-up stuff. |
||
| Shop 3572 |
|
Adilas Time | 3/8/2018 |
On the morning GoToMeeting session. I helped Russell get some login credentials for the data 0 box. He is going to be adding some new databases and PHP options for the WordPress part of the site. Wayne jumped on and we chatted before the meeting. Some of his stories about growing up in Idaho. He also showed us some stuff that he has created in Mindcraft - a huge super detailed castle. - He started with a question, is the world round? His answer was, it is round, and that is what I choose to believe. Sometimes we don't understand the who, what, where, how, and why. We just have to take the information and either choose to believe and/or challenge it. How well do you accept things at face value? - Things that are true and obvious at one point in time, may change as things progress. The same is true with programming. It is ok to question things and even challenge the norm. Be willing to break the models. We talked briefly about building and breaking things and then doing that again. - Why do you write code? Alan - it is like a puzzle and I like to figure out the pieces. When you finish the project, you can be proud of what you did and created. - Sometimes we like to show what we did and/or finished - that is a form of motivation (external feed) - We also love to talk and show people who can appreciate and understand what things are and what it takes to make that. - Eric - He likes to build things. He loves the design part of it and then seeing it come to fruition. - Russell - Easy, pretty, and powerful. Making things easy for others. - Programs and technology can really make or break a company. - What are the downsides to programming? Unpaid time that needs to be spent, people who don't understand, unbillable hours, the unknown, underestimating needs and/or requirements. Feature creep, pioneering and making things that don't end up getting used, etc. - Eric - He likes to bill by the hour. He swallows some of the cost and calls it his ongoing learning process. - Testing and test driven design - what is the style to do that and how do you accomplish that? Sometimes we get ourselves into our own little traps. If we take some time, sometimes we can step back and look at things from a different angle. - Why do we test and why do we write tests? Confidence. Being able to verify that it does what you want it to do... Reliable and secure... What about the design? What if you did test driven design? Instead of just writing code, you virtually think of the tests that it needs to pass vs just the plain action code. What is your vision? - Start with a test, then write the code to pass the test. The test might be the scenarios and/or the steps we want it to take. Have a bigger vision, but be willing to test and design as you build the component pieces. - Think modular code and being able to test independent pieces. Super complex code that isn't modular may be bad code. - Lots of emphasis on style. Appearance, the way things are done, systems, naming conventions, consistency, flow, a set of standards, easy to follow, other people/developers can follow along, patterns, directions and verbage, etc. A familiarity or comfort level. - What is our style? Wayne likes to spread things out, spaces, white spaces, lots of comments, lining things up for easy reading. There are also section headers and/or natural breakpoints. Wayne really liked to break up walls of text into tabbed sections. He liked to line things up and make it more readable. That really helps. - Wayne is using TestBox (testbox) a component of ColdBox (coldbox) for his testing. - He broke his code into setup, before, after, and tear down type functions. - Unit tests - tests a single set of code in an independent model. - Database calls may be expensive (bandwidth, speed, and traffic). We need a way to emulate and/or fake the database calls. That allows the logic tests to be performed without full access to the database. - Being able to mock things up is a huge key. Can we send fake data through the existing tests. - DAO (data access object) - This could be a real dataset from a database or a fake or mocked-up dataset. The key is that the test can run if the data is real and/or fake. Either way, it is still able to run. This may not go here, but Wayne was breaking up existing methods and almost making mini black boxes even within the functions themselves. - Where do you do your error handling? Wayne was specific where the error handling was and also where it was not. - Simulating real database calls with mockbox (mock-up data). - Formatting the data before the data is returned. Help prep the data so that it is ready when presented to the outside. - Test suites (a family of tests). Wayne set these up with a keyword such as testGetPermissions, testObjectInit, testSomeotherFunction. The key word was the string test on the frontend of the function name. - They, the guys, started getting more technical and actually looking at code and going over some of the test scenarios. - If you really go into full on test driven design and unit testing, you have to be to a certain level. Similar to project management, if you are not at a certain size, you could totally over do things. You need to match both the testing and the project management to the size of the application and the size of the project. - One of the goals of this test driven design approach allows for multiple different developers to play in the same sandbox. It helps to check tons of inter-dependency relationships (functions calling functions or other dependent options). It also helps your own code and making sure that all of the different scenarios can still play through. So, instead of retesting each condition, you already have tests in place to help it be more fluid and have a good confidence level of what is going on. - Code once and use many. Having said that, don't repeat yourself... that usually means that you are writing bad code. Wayne was showing how he often setup a valid object, and then he changed one param at a time. That made it easier to see what piece had changed. Efficiency and trying to simplify where possible. - What are the tipping points? Too repetitive, too long, too many forks, too many switches, etc. - Wayne, on purpose, was showing tons of different coding styles. His goal was to show that we could do it in any number of different ways. We just need to format the style to fit our company and then try to go from there. - Test the code that you wrote, not the code that some other company wrote (such as Adobe or Microsoft or Java or something like that). - Labeling and getting things organized. Try to group like things together. - Copying and pasting is very natural. It is very helpful, but can really duplicate problems. It can also make things fail due to lack of going back through and cleaning things up. - As you mature, as a company, you will really want to continue upping the unit testing and get use to test first, then code, test first, then code. Once things are in place, the future changes get easier and easier. Especially having good tests in place. - Russell asked for a step-by-step video on how to create things and even some best practices on what to do and how to do it. Wayne offered some other URL's, references, and links that will help us. How to install, how to tweak, etc. - Alan's question - How do we help independent developers to buy into this? They are already somewhat fighting us on basic code sign-off. What are they going to say and/or do if we force testing, unit tests, and test driven design? Wayne was saying that if you get it, it will really help with future skill sets. There was then some back and forth questions on where are we going and what are we requiring? Both Alan and Wayne were talking about things. Wayne is going to go back through and create the initial test sets and then we'll need to go from there. - All of this will get easier as we go along. - Wayne - without proper testing... Adilas will fold in on itself due to the weight of the codebase and number of virtual cooks in the kitchen. It will start fracturing and crumbling without the pillars and support system. The test driven functionality and design will end up being part of the culture. - Alan - we currently have some mega functions, that do way more than they should... those are really hard to test. We need to break things down into smaller and smaller function and be more focused and/or encapsulated into specific functions. - Wayne - by learning how to do test driven philosophy... it has made his job so much more enjoyable and fulfilling. This is a life style change for programmers. - Alan - If we go with test driven design and development... that means more dreaming on the frontend. He then said, Brandon, you will enjoy the more dreaming part of this. - Eric - testing is sometimes dangerous being left to the original programmer. Sometimes we need a separation. - Eric and Alan - MVC (model view controller) stuff - We have replicated things over and over again... As we get things better and better, we'll get a much cleaner code set. He really wants us to start pulling things into smaller pieces where we can get to what we need without all of the extra weight that currently exists. Think of adilas going on a code diet... we could really cut some weight and become more efficient. All we need is that little bit of logic or that little bit of validation. - Maybe moving trims (trimming functions) out of database queries and up higher in the process. Setup the trims higher and then use all of the trimmed values as part of the re-usage. Once it becomes correct, use that value. Otherwise you could get disconnects and possibly be passing different values to different pieces without even knowing. - One of the main goals is maintenance and starting to reform this code and application in new ways. Making the code rewrite that much more possible. |
||
| Shop 3584 |
|
Adilas Time | 3/8/2018 |
Looking over new black box code that we got off of the live servers. We have a number of developers who do custom code and we never see it in the master code branch because it is fully custom. I went to all of the servers and looked for certain files. I pulled them in and briefly looked over them. I also did an email update on the meeting this morning with Wayne Andersen about test driven design and what not. I sent the notes along as a PDF and uploaded the video from this morning. Other email stuff and recording notes. |
||
| Shop 3590 |
|
Adilas Time | 3/13/2018 |
On the morning meeting with Steve and Russell for the first little bit. Steve and I were talking about the balance between custom code and internal code and development. We spend a lot of time on custom stuff. However, it also helps to pay for our guys and we gain some benefits by allowing it to happen. We do need to be careful, but if we keep it balanced, it can and will work great. We talked about using the Ice-down dates and ICC (internal cost corrections) per locations to help keep things straight. This could be done to help close things out and keep parent costs in check. The real answer is in sub inventory and cost controls, but we have met with some resistance, especially from older or prior clients. They don't want to take the jump and do that extra step. Anyways, as Steve and I were talking, there was a definite undercurrent of the users need to use the tools provided and/or pay for future development. We would totally wear ourselves out if we did everything that was asked of us by our clients. We simply can't do it all. We need to make the dreams meet reality, on both sides of the fence. Good conversation. Russell and Steve chatted about changes to adilas ecommerce while I started paying bills and fixing a small bug on the BSI (balance sheet items stuff) to expense/receipts. After that, I jumped off the GoToMeeting session and did my own stuff. I did a bunch of emails, paid bills, and got Wayne setup with Newtek as an authorized adilas rep to open and check on support tickets and such. After that, I started to work more on the sales tax by customer type changes that Kelly is waiting for. This is a smaller part of the bigger sales tax expansion project. That has been a long time coming. |
||
| Shop 3610 |
|
Sales Tax Expansion Project Time | 3/20/2018 |
Joined the morning meeting late today. I had a dentist appointment. Got on and chatted with Steve about some new things that are happening and gave a light report. We talked about some light finances and budget stuff. I worked on the sales tax expansion project while I waited for Wayne to join the GoToMeeting session. Once he came on, we worked on adding cross-server DSN (datasource names) between servers and databases. Everything went pretty well. We stopped because we were getting an error. Everything else went well and Wayne was going to check with tech support on the error message. It could have been a firewall issue or a driver issue. After that, I got on a phone call with Calvin for a few minutes. We were going to meet today but we will hit again tomorrow. Back on the sales tax expansion project. |
||
| Shop 3669 |
|
Adilas Time | 4/16/2018 |
On the morning meeting with Steve, Russell, Alan, Wayne, and myself. We started out and Russell needed to do some code sign-off. He had a number of new CSS changes, verbage changes, and small changes to links and news and updates. We went over the changes and pushed things up live to the servers. That took about an hour. After that, Wayne and I talked about QuickBooks integration and doing both exports and imports to and from adilas. This is a custom project that Wayne is looking into and has a client that is paying him to plow some ground there. We also talked about some more advanced cross-server data migration projects and such. These are a couple of points that Steve brought up after the other guys left. - Plan most of our changes for 100+ people and/or users... think bigger than just one or two. That helps us make the best decisions. All other things that might swing one way or another should be permissions and/or settings. Great advice. - Steve also sees a whole new round of permissions coming... it is amazing to see how each things needs to virtually break into subs to get the level of control that you need. |
||
| Shop 3671 |
|
Adilas Time | 4/17/2018 |
Online team meeting to cover security, adilas API sockets, black box code, and upcoming white label options. We started out with a number of reports by the different guys. /////////////////// here are some of the quick reports by the developers: - Eric - Fixing custom carts and working on the pricing engines. Lots of custom one-off's. Working on loyalty points and special tracking accounts. - Russell - News and updates - new API socket feeds and such. WordPress site and other look and feel things. - Wayne - Refactoring code, testing based design, and underlying framework. QuickBooks integration stuff - imports and exports. As a side note, Bryan has had many customers asking about similar type features. Wayne is also working on other database stuff and migration. - Bryan - White label stuff for outside parties. Tons of custom projects. - Calvin - Hybrid API to Windows desktop app. Custom PDF labels and printing. - Alan - Helping Steve with Metrc API stuff. Working on tons of tax and in-line discounts. Helping Brandon with other projects. - Danny - Generating sales - Props to the developers who are creating the functionality. He pitches the idea that the developers are accessible. Custom labels. - Shawn - Helping with payroll, federal withholdings, state withholdings, and county level withholdings. - Brandon - Helping the developers and doing small projects. Merging code and maintenance stuff. - Steve - Grateful for the help with the Metrc API stuff. Working on phases and sub locations. Steering the ship. New approval levels on other state traceability systems. //////////////////// meeting notes: - Talking about the Adilas API and system - dealing with security. Facebook was brought before the senate due to a breach. They allowed an outside company to come in and develop an app for Facebook (basically a 3rd party solution). The problem was... what does that outside service actually do and have access to? The app ended up doing some internal data mining and then sold that data. - We want our users to be successful - we want to enable them but we also need to protect them. - Small switch in the sales focus. The older model was one-by-one and dealing with reps and consultants. We are seeing more of a switch to bigger companies that virtually take over the sales force and are wanting to sell our product more as a white label type application. Lots of mixing and blending of products and services. They are allowed to provide all of the supporting services that support our product. - Ideas from the group about security: - Russell said, bold it or make it red and let them know what they are exposing (meaning the API sockets). Allow the agreements between the parties... we are part of it, but we let them create the relationships between themselves. - Steve said, we don't want to make our users work harder... to turn things on, but we do want to make sure that the clients know what they are getting in to. Example of what happened with back in 2015 with Hypur and Emerald Fields (two of our clients). Basically, the 3rd party solution (Hypur) got turned on and then it kept growing (what Hypur was doing and/or requiring) and eventually was trying to get at more sensitive sales and inventory level stuff. Eventually the client was super upset due to the lack of disclosure of what was going on and what was open/available to the outside party. - We are seeing that most of these 3rd parties and white label people tend to expand what they are asking for. Bryan is seeing that more and more auditing type levels are wanted by these 3rd parties. We have also had a number of questions about different server levels and certifications. Our clients want to make sure that their data is safe and secure. - Russell brought up the point and the difference between a couple of if statements on a page vs a full on white label type solution. We need to develop and standardize that white label type path. They need to pay for it and also be able to help maintain it (meaning the white label company). Taking things clear out to a white label theme (actual files and folders). White labeling is basically bulk black boxing but you can still use any of the classic pieces. We drew some small diagrams and talked about possible options. - Shawn chimed in and started talking about building a city. Basically, kinda like urban sprawl or older parts of a bigger city - no plan, no alleys, buildings touch other buildings, and not a well planned layout. - We need to stay on top of things. Keeping code and the database structure up to date. If we do this... it will help us be more efficient and save us time. - Eric chimed in and said "process" is the solution vs simple communication only. Basically, as we are growing, we need to get to a more standardized process of development. We have a huge landscape to consider. Lots of moving pieces. Ultimately we need to adopt a process oriented approach. Wayne agrees. Different levels within software development. From critical and saving lives to making sure that we have solid code and pieces. It gets into speed and flexibility against slow and more stable type processes. Maturity in software development is sometimes measured in how well you implement internal processes. Eric thinks this is the next step we need to take as a company. - Danny has been threatened... :) He was talking about levels that people rely on our solution and how all of that plays in and such. - Small little analogy of the little red hen... everybody wants it but they may or may not want to participate. In real life, things cost money and take time to get done. - From Brandon - Let's make this thing what we want it to be! - Any core elements need to be merged into the master branch. This is required. - Steve was saying... be on the lookout for companies and what they are wanting. That could help us know how to play with them... Maybe look deeper than the current project. We really need to protect our client's data. He was talking about the adilas market (adilas world) and also the 3rd party solutions page. We need to point outside parties to come through the main monitored pathways. We need to keep those sections updated and let the clients know what is being opened/exposed. Very important. - The value of oversight and/or having someone to help watch them and help them out. This seems to be new trend. If that is the case, we need to make sure that they know what is going on and what is opened and what is closed (talking about data). - Brandon will write up some super basic pieces of what our current rules and processes are. - Alan pitched the idea... Local, live, and then into production - talking about a testing server that will be coming this year. We ended the meeting and allowed people to jump off the meeting. We basically said we would be doing this again (meaning a team meeting) and would get them some info and instructions. /////////////////////// after the meeting - Alan and Steve were talking about breaking up code into logical pieces and making the road map more object oriented. Basically, organizing the use and flow of data - making the map for others to follow. Currently, we are just using Brandon's memory to help guide people to the right spot. We need a better road map that others can follow. - They got into some technical conversations about threads, processes, RAM memory, read/write times, etc. - Part of our process needs to be setting up and monitoring the servers (actual eyes and reports or dashboards). We need more information, stats, what pages are being used, what processes are running, and what data is being accessed and how often? - We talked about caching, traffic, threads, database transactions, data mining, and changing from transactional data to more of an aggregated type model (summing up things and organizing things for reporting features). We need to keep allowing day to day operations but also need to optimize things for reports, exports, and other bulk reporting features. - Alan and Steve were talking about the challenges of using outside API's and syncing up data between systems. Lots of options, but also lots of moving pieces. - On the API sockets... We need to provide good samples of how to call things and also good response type data. It is really nice if we can format things as well. It just makes it easier for our guys and also outside developers. |
||
| Shop 3690 |
|
Adilas Time | 4/23/2018 |
Recording notes and on a Zoom session with Calvin. We talked about his progress on his custom desktop application. We went over the submit cart page and talked about new API sockets that he would need to use for doing invoices, line items, and sub inventory. After that we talked about a meeting between Calvin and Wayne Andersen. They swapped some ideas and Calvin gave him some code to help Wayne get started on project. |
||
| Shop 3727 |
|
Adilas Time | 5/3/2018 |
Light tech support and emails. Wayne popped into the meeting and had a few questions. Most of my time was doing small bug fixes and working on documentation for the adilas API sockets. |
||
| Shop 3762 |
|
Adilas Time | 5/21/2018 |
Small updates on where things are at with different developers. As a fun side note, we had our first person register for all four days of training and pay online using our ecommerce site. We have had people paying their monthly bills for quite some time, but this was the first start to finish ecommerce sale for a training event. Kinda fun. Wayne popped in and wanted to talk about QuickBooks integration. He is working on the customer integration process. How do we sync things up and who is the master. Is it adilas or is it QuickBooks. It sounds like a setting. We also talked about other possible options such as flex grid, custom tables, etc. Wayne would also like to help us out with our servers and such. That would be awesome. Keeping things standard and really automating things. He would love to setup things programmatically vs full manual processes. Currently it takes us 2 to 6 weeks to setup and get a new server fully ready. After I got done speaking with Wayne, I went in and worked more on the reoccurring elements of time. I have a working version done, but it is not currently tied into the system. The page is uploaded to all servers but it has not yet been standardized and/or help files fully created. The page name is top_secret/secure/setup_reoccurring_time.cfm?id=190 (some real id number - the master id to copy). I'll get back to it a little bit later on. I'm just glad that I could get it this far right now. It still needs a little bit of loving. |
||
| Shop 3764 |
|
Adilas Time | 5/22/2018 |
On the morning meeting with the guys. Quite a few of us were on this morning. Steve and Alan were mostly talking and dealing with some changes to the Metrc API and state systems. Wayne popped in and chatted with Steve. Wayne is looking to play a little bit deeper and be more of a regular developer. He is retired but looking to re-enter the scene a little bit more. Russell popped in and he and I did a different Zoom session. He showed me some of the news and update feeders. Basically, he is designing the snow owl footer to be able to consume internal corporation information (elements of time) as well as outside feeders from WordPress sites and feeders. Tons of new options and such. Pretty cool. Russell and I chatted about how deep things need to be in order to play the game. On the programming level, we have to go super deep, but on the surface level, we have to make it look very simple and easy. Somewhat of a paradox. While Alan and Steve were working, I was working on in-line discounts and in-line dollars off stuff. //////////////////////// Meeting with Anthony Harrington from All Greens. We did some light reviewing of changes since our last meeting on 4/10/18. I made some searches in the adilas shop for "pricing engine" and for "Anthony". Once the results came back, I read through and reviewed some of those notes. We talked about pushing the my cart favorite buttons to a higher level. He would love to get the buttons tied to time and to days (for example, just show up on Thursdays, etc.), be able to discount based off of category, and being able to apply those discounts in-line using percentages and/or dollars off. I did a small demo and showed him where we are headed with the in-line dollars off discounts and such. We went through a couple of scenarios. - On PO's, once you verify a PO, it still allows you to modify things. We talked about Ice-down dates and I showed him a demo of how things work on the invoice side of things. We talked about getting that functionality available for all of the other main system players (12 main player groups). - He had a question around rounding tickets or invoices to the nearest dollar value (no left over cents). He would like for invoices having $0.50 or less, go down, and $0.51+, go up. I quoted him at $200. He wants this new feature for corp id #1114 on data 6. This same functionality would be really cool if it was a setting... yes/no for auto rounding to the nearest dollar. We would also need to know, what are the levels? Such as, round up on anything over 50 cents or round down on anything below 60 cents (or whatever). Basically just settings to help it know what to do. We may also need to know what part number (id) to use and what verbage to use such as: convenience fee, rounding difference, etc. - He had a question on allowing invoices with partial payments (not fully paid). This would be an awesome setting as well. Image a setting that says allow credit to be extended or require full payment in order to submit cart for processing. Some new settings could handle that and help make it more automated. |
||
| Shop 3768 |
|
Adilas Time | 5/24/2018 |
On the morning meeting with Steve and Dustin. I merged in some code from their branches. Wayne popped in and showed Steve and Dustin a small demo on what he is doing to help rewrite some of the Metrc stuff. He loves to rewrite things and make it look more simple. After that, Steve gave Wayne a demo on his cultivation process that he is working on. Good stuff. Alan and I spent the last half of the session working on in-line discounts and doing some deeper testing. We were testing and making notes on bugs or light fixes that were needed. Excellent back and forth checking, debugging, recording, and testing. It made the testing so much more fun to have two eyes on the same tasks. We'll do this again. |
||
| Shop 3789 |
|
Custom migration for Data 8 | 6/3/2018 |
Late night, after hours, working with Wayne on a custom data migration. We had 6 corporations to move off of data 3 and onto the data 8 server. That server, data 8, has been ready for almost 6 months. We were waiting for the sales tax updates to happen and take place prior to the migration process. We finally decided to just do it. Anyways, Wayne and I jumped on and did some prep work. We started pulling data for the corps and transferring it over to the new server. We then had to go through each folder on the data 3 box and make sure that we had the latest and greatest files for the new data 8 server. That took quite a bit of time. Towards the end of the session, we had two database tables that were giving us problems. We had to switch tools in order to get everything migrated. Then at the last second, we found out that we had one other (newer) corporation that needed to be migrated. By the time we started onto that one, the clean migration process ended and the new data 8 server started getting used by the company. The last minute request for the new corporation failed in a number of places due to duplicate id numbers. If we would have known about the seventh corporation before hand, everything would have been ok. But we didn't learn about it until users had already started working for the day and thus claiming new database id numbers. Pretty crazy. |
||
| Shop 3782 |
|
Adilas Time | 6/6/2018 |
Doing code sign-off with Russell. He is getting better and better at running tests and creating his own components. Coding once and using many. Wayne jumped on and had a few questions as well. After that, Steve and Wayne were talking about smaller functions and using getters, setters, and smaller functions. Cory jumped on and was talking about inventory thresholds and buffers for inventory levels. We talked about simple maxes, mins, and buffer levels for single items and single locations. To really do it well, we need to get it to a full on multi-location level so that we can play the game. They also talked about some bulk print options on the PO side of things (ad the users bring the items in to inventory). That would really help them save some time. The other request was dealing with really small barcodes and really small labels. Cory and Steve then talked a ton about custom check in/out flow, sub queues, ecommerce, personal devices, and getting people and items into the system as quick as possible. We have tons of these features built out, we just need to know how to combine them. It is interesting that each client needs a slightly different mix of how they want to organize and control the flow of both customers and products. Very interesting. While they were talking, I was working on adding in rotating and revolving password for the contact us pages (email forms). We had someone go in and try to hack things and use our contact forms for sending spam. We live in a crazy world. |
||
| Shop 3783 |
|
Adilas Time | 6/11/2018 |
On the morning meeting. Wayne and I were trying to figure out cross server datasource names (DSN's). We kept getting denied and couldn't get it to work. Wayne was going to call Newtek and have them help check on things. He later reported that he was able to get things fixed. As part of the morning, I got an email stating that something was causing a problem out in ecommerce land. I did some checking and made a couple of quick tweaks. Hopefully that will help. It is amazing how many different things we need to be aware of in order to make things work. I am so grateful for our user base that communicates needs, errors, and requests. It makes adilas into a live and growing idea farm, and that is super cool. Good stuff. Towards the end of the meeting, Steve and I were trying to check some errors on the data 2 box. We were logging in, checking database tables, and then looking for other possible errors. We talked about error handling and ways to help all of us out in the process. |
||
| Shop 3780 |
|
Adilas Time | 6/13/2018 |
Talking about creating a smaller sub theme in adilas and called it "fracture". This would end up being an adilas fracture account. We would like to rebuild things from the virtual ground up and add in all of the subs of subs and database field level control. This would be a full on internal white label and/or internal theme that goes down to the micro level. This deals with database field names, settings, permissions, and all of the sub settings and sub permissions that are needed. It could also deal and use smaller getters and setters as well as individual databases, custom API access levels, etc. This is kind of a dream, but it would be so cool if we took the time to virtually rebuild the entire thing from the ground up and use and apply all of the ideas and lessons that we have learned getting to this point. That would be really exciting. It would really be cool if we had the money, funding, plan, and people and talent assets ready to play the game as well. That would be a huge but awesome project. Just an idea and/or a dream at this point in the game. Talking about scalability and how to manage up and down swings without shooting ourselves in the foot. We were talking about load balancing and monitoring usage, storage, and bandwidth. We have been seeing some light push back on price from the consultants. Basically, they are charging a certain amount and then promising that our services are and/or will be a certain rate for life. We are also seeing that some of our clients are growing as they come on to our systems. That is hard to know what is going to happen when they first start up. Technology keeps changing and pushing things forward. This is a crazy world and we need to build on the dynamic changing environments that happen all the time. This is not a static model. Traditionally, software companies build versions and then release that version. They then build in the background and make the next version and then plan the release of the next version. Our model is literally build and deploy on a daily, weekly basis. Alan was saying that our clients are paying for what the current adilas system does and can do... they are not paying for the future developments. However, some of the client demands are almost all speed, bulk, and future related. Tons of cause and effect relationships, pros and cons, and maintenance things... lots of talk about concepts, styles, and preferences. After our discussions, we all went back and worked on our own projects. I was working on adding in the customer type id filter for sales tax reports and advanced invoice searches. Steve and Dustin were working on Metrc API pieces and bulk QR code labels. We also had both Wayne, Alan, and Calvin pop in and help with different questions and projects. Busy work section. Also some light phone calls and tech support stuff. |
||
| Shop 3779 |
|
Adilas Time | 6/25/2018 |
On the morning meeting with Steve and Wayne. Light catch-up from missing a week at scout camp. We then got a small demo on some of the code that Wayne is writing for the data transfers and data migration stuff. He is adding in universal unique identifiers (UUID's) and data check sums. On the data check sums, Wayne was taking in all of the data, fields, and values. He was then putting all of that together, running a special hash on the data, and the storing the smaller hash value. Then later on, he could compare that smaller hash value to another smaller hash value to see if any of the other pieces had changed. So, in real life, imagine a database table that has 50 columns of data and thousands and thousands of records. If each record (set of all 50 columns worth of data for a single record) could get a small little hash for the grand sum of the data. If anything changed, the mini hash would then change. This helps so that you don't have to individually check each of the columns and data to see what has changed. Great idea and huge time saver. This is also really important for migrating data while a customer is working on things. If the hash remains the same, you know you have the latest data (all synced up). Very creative. You just need to make sure and update the small check sum if anything changes. That is kinda the key. This is the same process as a last modified date, but deals with data vs dates. Similar concepts. Part way through the day, we got called out and had to do some major work and checking on the data 2 server. There was tons of web/API socket activity and it was bringing the server to its knees. We ended up disabling the data 2 API socket access port and did some checking on the local server. There had been over 72,000+ web/API calls this morning alone. We figured out that many of the calls were dealing with full invoice details and customer data look-ups. That raised some questions. After running a number of queries, we had some conversations about dedicated boxes, API socket access, and how to help monitor and load balance things. See attached for a few of the queries that we ran on the data 2 box to check things out. |
||
| Shop 3884 |
|
Adilas Time | 7/3/2018 |
Dustin, Alan, Wayen, and I were on the morning meeting. Small demo by Wayne on object oriented coding. We were seeing all kinds of service objects, data objects, database access objects, and other models. This all goes back to the keeping the data, the validation, the business logic, and the database stuff all on different levels. That just makes the code more re-usable and more logical to follow (both internal and external). All of this makes things more modular and easy to use. We spent a little bit of time talking about MVC's (model view controller). Each area is different. You have the model, the view, and the controller piece. They are all kept separate and run on their own levels. You can then mix them as needed. We talked about DAO's (data access objects) and using universal getters and setters to get at the data and the sub pieces of those concepts. The guys were getting into what will and won't work and why. They were talking trade-offs of simplicity vs flexibility and other factors. Other topics ranged clear out to security, XSS (cross site scripting), SQL injections, etc. They were talking about transactional records, commits, roll-backs, try/catches, and other safety measures. They were talking table level locking, application flow, traffic, scalability, and usability. They were talking about unit tests, global testing, and other pieces. Standalone tests, mock-ups, and sequence tests. Having their testing already ready and done really helps them to go in and change things with confidence. Test driven design and getting that peace of mind, knowing that you have a number of prebuilt and preselected tests to run on your old and new code. It is a real time saver and helps them have the confidence that things are working, even with changes. We are changing the implementation (how things are done) vs the background core principles (why or what is being done). Pretty technical discussion. These guys are masters and are good at what they do. We are trying to get the entire application out to the web/API socket level. We need a way to structure things and yet have modular data and open access to all. After the demo/meeting we all split up and worked on our own projects. Steve, Alan, and Wayne kept working on some Metrc plant code. I was working on the developer's notebook project. Then after that, we jumped into a discussion about servers, virtual servers, and how to help optimize the different servers. We were talking heap sizes, through put, and other optimizing and server asset management options. |
||
| Shop 3881 |
|
Adilas Time | 7/9/2018 |
On the morning meeting. Wayne popped in and wanted to get permission to setup a server to help monitor the other servers. We talked about it and decided to let him setup a server on AWS (amazon web services) to monitor our other servers. He will build things out and then report back to us on the progress. Basically, that allows us to experiment without jumping in hook, line, and sinker. We spent a good portion of the meeting going over code, options, and answering questions. Back and forth between myself and Steve. We also talked quite a bit about optimizing database and queries. Light tech support to help Steve, Dustin, and Bryan. Around 11 am, Bryan popped in and we worked on a server primary domain mapping issue so that new and/or white label custom domain names could work with the adilas.biz application. Made some tweaks and pushed up new code. Emails and other tech support stuff. |
||
| Shop 3891 |
|
Adilas Time | 7/10/2018 |
Steve, Dustin, and I were all on the morning meeting. I was working on the developer's notebook pages and project. Currently working on a page that shows web ready (public entries) elements of time in a grid type breakdown by month and year. The goal is to help web spiders and other web crawlers to be able to get to the elements of time and then index and archive the content easier. This is a big part of the developer's notebook project. Our underlying goal is somewhat of an attempt to help publish and publicize some of the core concepts that adilas.biz is build on. Going way back, we went to a workshop on intellectual property and how to patent, copyright, trademark, etc. As part of that, they said that if there was prior art or prior work, you couldn't do the patents, copyrights, and trademark stuff. So, in a way, we are trying to make some of the core concepts become part of the public knowledge bank. We are basically trying to make it so that the core concepts are unable to be patented or trademarked. We need them to be open and available for all entities. Wayne popped in and he showed us some server monitor stuff using a Nagios server. We setup some server monitors for all known servers. |
||
| Shop 3892 |
|
Adilas Time | 7/16/2018 |
On the morning meeting with Steve, Dustin, and Wayne. Steve and Wayne were working on a bunch of different things and updates to Metrc stuff (state compliance API calls). I was answering emails, light tech support, and checking on random bugs. |
||
| Shop 3878 |
|
Adilas Time | 7/17/2018 |
On the morning GoToMeeting session with Steve, Dustin, Wayne, and Alan. We were all working on different projects. Alan and I were primarily working on in-line discounts and making sure that the new excise tax calculations were playing well. Lots of back and forth debugging. Wayne and Steve were working on new Metrc plants, packages, and cultivation stuff. They were working through a small date issue with the databases. Lots of testing and micro tweaks on all sides. It was also nice to have another pair of eyes for the different projects. Sometimes Alan was helping Steve or Wayne or I was helping Steve or Wayne. Lots of back and forth, all using the same meeting. Good session. |
||
| Shop 3880 |
|
Adilas Time | 7/25/2018 |
Spent most of the morning meeting doing tech support and helping Steve and Wayne merge in some new code. Wayne Andersen is taking some our older code and turning it in to more object oriented code and script. Steve and I were looking over things and drawing up analogies to help internalize some of the new changes. It is kind of the old school meets the new school on tactics and logic. We looked at code and tried to digitally diagram and talk about what was doing what and what options that brings to the table. Kinda interesting. I got a call from the Utah Workforce Services and they had some 1099 questions about tax year 2017. I spent some time getting them info, PDF's, numbers, and contact info for our independent developers. |
||
| Shop 3896 |
|
Adilas Time | 7/25/2018 |
Uploading a number of new files that Wayne has been working on. Some of them required us to login to each server in order to set up some sub folders to put the new files in. There were about 63 new files and we had to push them to all live servers manually. Light tech support and emails. |
||
| Shop 3931 |
|
Adilas Time | 8/14/2018 |
On the morning meeting with the guys. Bryan and I used up the first 45 minutes wrapping up where we were at on the application flex grid planning. Wayne popped in and reported. He has been sick for a few days/weeks. He will be helping out with a server to server migration project later tonight. We also talked about an existing project of inter-migrating data between two fully running servers. That is very deep and is actually a C sharp project (server-side software). Very deep. Steve and I worked with Dustin and tried to help him on his mapping and custom dynamic settings page. We had to go back in time (on the code) and look-up some older values. They still existed, they had just been renamed and it made it hard to figure out if we were still talking and dealing with the same pieces. Steve and I talked about how in-depth it would be to do a full server to server migration while the systems are up and being used. We went clear back to a project (world building) that started with Highland Vineyard and wanting a full duplicate copy of a corporation so that an older owner could have their data and the new buying company could have their own data. We have had a need here for a long time. It is totally unknown and might end up being a super huge project ($150,000+ level). At the end of the meeting, Eric popped in to work on the loyalty point and such. We are going to get back together after lunch. |
||
| Shop 3978 |
|
Custom server migration project | 8/14/2018 |
Wayne, Steve, and I worked on doing a custom data migration for 21 corporations. We prepped things, grabbed all of the custom code, images, scans, look and feel pieces (logos and watermarks), and migrated over 12,000,000+ records. All of that info and data was migrated to a new dedicated server. We had one database table that gave us problems. We ended up splitting it into multiple smaller pieces, in order to get it to migrate correctly. Good combined effort. Long night. |
||
| Shop 3938 |
|
Adilas Time | 8/16/2018 |
Jumped on the morning meeting. Steve and Dustin were on there and so was Wayne. Steve and Dustin opened up a Zoom session and worked on that. Wayne and I worked on a huge database field list with tables, field names, and mapping out of the foreign keys (database columns that link tables together in a relationship). We went over 4,000+ fields during our meeting. Most of the time was spent mapping out what foreign key values where and how they mapped to what primary tables and columns. We saw lots of activity in the payee (users and vendors) table as well as the corporations (worlds or business companies). Good session. At the end of the session, Wayne showed me a sneak peak at a tool he is calling the Adilas Database Sync tool. It is a C sharp program that compares two different databases and makes sure that they are all synced up. I got excited on a few of the cool and creative features. Here is a small list. For more info, talk and ask Wayne for a demo. - Super cool idea for comparing records... He would put all of the data together in a huge string (column value, column value, column value, etc.). He would then run a quick hash on that data. A hash makes a small 32 character unique code (really small amount for storage). He could then store that hash value. Then later on, when he was checking the data, he could put all the new data together and re-hash it. If the hashes matched (the two small hash values), no updates were needed and he could skip the record. If the new hash was different than the old hash, he would run the update that know what fields to update. This helps sync the data and also allows the system to skip something that doesn't need any changes. Very cool. - He setup the whole thing to do non-destructive adding and updating based on using recursive functions (building logic as needed vs doing a, then b, then c). He also built in some options for taking care of the exceptions. - This new Adilas Database Sync tool will have a huge time savings attached to it. Just a day or so ago, we migrated over 12,000,000+ records for a server to server migration. With Wayne's tool, we could set it up to do the sync even days before the actual migration process. It could run while you sleep and even run over days and days as needed. Then, when you are ready to do the final migration (deep pass over the data), most of the work would already be done and only new updates, additions, and/or changes would need to take place. That is huge. This also opens up possibilities of doing some mirroring and having back-up data servers. Very cool. - We talked about using this database sync tool for doing for testing... We could copy over specific customer data, code against it, do the tests, and then go from there. Huge options. - We briefly talked about Calvin's Auto Process Tool and custom code options there. Once again, both of these programs use server-side software to get major crunching power while still allowing for a normal web-based interface. Imagine what we could do if we built some connections between Calvin's auto process tool and Wayne's adilas database sync tool. - We talked about how developing server-side software using something like C sharp is so much faster than web-based languages. We talked about how many levels of conversion the code goes through and/or does in order to run it... Imagine ColdFusion code being interpreted by Java and Java be interpreted who knows what, and that being interpreted into system or unit code, etc. You get the idea. There is also a huge difference in the timeout windows and how long process are able to run without manual and/or user interactions. - We could schedule out long running tasks, report, exports, and/or other tasks. We could get away from web session timeouts. That would be awesome. Sometimes it feels like we are trying to fit the whole world through a revolving door (analogy of trying to hit the web timeout rules). - We could also use some of the C sharp tools to flip indexes and database column level defaults. Some of these things are text fields currently set to latin 1, could be changed to UTF-8 format. We could change default dates and times from default dates of 0000-00-00 to 1990-01-01 (a real date value vs the generic placeholder) and default times from 00:00:00 to 12:00:00. Once again, we could skip all of the web session timeouts and just get the job done. All good things and it could be done very quickly with minimal clicking and babysitting. That is where the value lies. Good stuff. Looking forward, I'm not sure what the future holds, but I'll bet that it will have both web code, server-side software, API sockets, and other hybrid type solutions. Each thing is good at a part of the game, we just need to mix and blend as needed to get the different jobs done. Exciting times ahead. |
||
| Shop 3943 |
|
Adilas Time | 8/16/2018 |
Emails, tech support, and recoding details from the morning meeting with Wayne. Next up, working on the training schedule for the upcoming September adilas training event. |
||
| Shop 3952 |
|
Adilas Time | 8/27/2018 |
Wayne popped in and we talked about database transfers between servers and how to handle duplicate records. We came up with a plan and he will be moving forward with the plan. Eric and I setup some dedicated times to work on loyalty points and special account tracking. We are planning on 2 hour blocks for the next two weeks, from 1-3 pm, Tuesday, Wednesday, and Thursday. That will be good to get some dedicated times to work on things. ------ different topic ----- These were some other questions that I wrote on a number of post-it notes... we are just trying to get organized and figure out a better plan for handling all of the pieces that are coming in. - There are so many needs - There are so many new requests (new things) - There are quite a few bug requests (old things) - Who does the work? - How do we inform them? - What is the plan? - How can we duplicate ourselves? - How do we create the funnel type approach.... things come in, we record them, we organize them, we distribute them, we work on them, we can check in, get reports and put things to bed - If I add to my to do list... it never gets done - Who can I use and what are my budgets? - How do you prioritize request, projects, and bugs? - Who gets assigned? - What do we want to be? - What are we becoming? - Who are we wearing out? - How do we mange that? - What are our goals? - We need some help - See a need... fill a need - I kept coming back to this... this may be the next step. - Help people manage themselves - I feel like I'm climbing with a dresser on my back - so many pieces, we need to simplify. - What teams (people assets) do we have? How are we going to use that? - I'm running and hiding... - We need some help - Kinda like facing giants - Get the Lord's help - Get some good help - See a need, and then fill that need... make a plan! - Focus on one thing at a time - it is hard to switch and transition. - We may have to keep people at bay while we do things. - Schedule it out and stick to that if possible. ------- meeting with Steve ----- - Departments and who gets what - We sometimes have multiple people looking and checking on the same things. That is not effective and/or efficient. Say an email that is sent to Steve and I, we both look at it and then both respond. This is just one example. - How do things come in? Do they start with support or do they start with a call to a rep or something else? We might need to start catching things and then funneling them around. - There is not a book on "SaaS" Software as a Service. We are kinda faking it as we go. That is for real. Basically a pioneering project. - Maybe talk to Shannon and see if we could get here back. Maybe have her come back in as a different role. We could really use an internal project manager of sorts. Maybe a higher or overall approach. - We may need to use elements of time and create our own support system and/or support tickets. That could be really quick, now that we have some things ready and done. - We would love to have a sorted tick list... What are the top 10 maintenance pieces, top 10 bugs, top 10 new requests, top 10 upcoming projects. Then keep rotating through that. - We love the concept of the data assembly line... What about our new needs... We have done of data, tons of servers, tons of requests, tons of needs... how are we going to track that process and take the actions that are needed. - We might need places where we have ideas, projects, maintenance, bugs, etc. - We often talk about the burning platform... it is amazing as we keep going, the burning platforms get fixed, and then there becomes another burning platform. - Steve and I need a shield to help us filter some of the outside static and/or noise. Once it gets boiled down, we could get a list of things to do and work on. - We feel bad about not being able to get emails, phone calls, and texts. We are just getting too many. We may need a person to help shield us a bit there. - Steve and I have thousands and thousands of emails and thousands and thousands of text messages. It gets too much for one person to handle. - We are in the business of data management, storage, processing, and such. We need to help categorize things and help filter the number of requests that come in. - Filters... We need someone to help us catch things and then basically boil things down into a manageable list. - We need to be able to allocate resources as we see fit. There are always limits on people, talent, time, money, etc. We need to manage our resources. - We have some guys that are top notch... We are seeing Wayne, Alan, Eric, Bryan, Will, Dustin, etc. They are all shining and showing more and more potential. That is exciting. - We also have Shari O., Shannon, Drea, etc. on the tech support and customer care side. - We will be working on a running list and trying to be more effective. - We really want to reach out and have the people run and excel where they have skills and talents. - We are going to be reaching out to and contacting some of our people. We have a great team... if we use that team wisely, that will open up options. - Kinda funny, we use to ask our clients, where is your pain? Let's start there. We'll we have the pain now, so, I guess we start there and work forward. Yee haw! |
||
| Shop 3939 |
|
Adilas Time | 8/28/2018 |
We came on this morning with a notice that one of the data servers had been compromised. Someone had hacked in and changed some file names and some background services. Basically, they, the hackers, change the files names so that the computer can't find what it is looking for. It doesn't mean that they take anything, it is almost just a calling card saying, hey, I've been in here... got ya. We have the server team working on things and will be resetting all access usernames and passwords. Wayne popped in and we worked on some questions that he had with the sub inventory attributes and custom dates, numeric, and custom text values. That part of the system gets pretty deep. Good stuff. |
||
| Shop 3932 |
|
Adilas Time | 8/29/2018 |
Got some reports that the data 1 server was having issues. The two reports were that it was not finishing the invoicing process on any corp and that a person could not edit a user account. I logged in and took a look at what was going on, sure enough, the invoice process was stopping part way through. It took awhile, but we found that the problem was the invoice history table. That table was tied in to both the add and edit invoice processes. Because we had ordered a full server restore, it was replacing tables with older data from a back-up. We also had a couple of people still on the server trying to put in new data. Just the way the tables worked, it created a conflict and was giving us a duplicate record error. The other problem was the main user table. Originally, it looked like it had been hit as part of the server hack. We later found out that it too was trying to sync old data and new data and just needed a little bit of loving. In the meantime, we posted a temporary login page and added notes to it throughout the day as we found out new pieces and made small break throughs. It was pretty stressful on our side of the fence. I know that some of the clients, on their side, were stressing it as well. Throughout the day we 7 or 8 of us here at adilas helping out. We had Calvin helping me on the servers and checking database stuff. Wayne popped in and helped us reset a number of things and do some looking around to see if we could see any other harmful activity. Alan popped in and helped us with fixing the database problems towards the end of the day. None of them were very straight forward. Steve was helping to coordinate who was doing what and testing with fake data to make sure things were flowing through. Shari O. and Drea were doing emails, phone calls, and text messages. I was digging through log files, working with the other guys, and back and forth with the server team in Arizona. Very busy day and it took the whole team to figure out different parts of the puzzle. I'm super grateful for their help. Only the one server was down, but that was pretty crazy. Lots of lessons learned and it was re-restored, released, and pretty heavily tested by around 6 pm. We added a link to the main login page on that server to show a link of what happened and some notes from throughout the day. One of the most stressful things was wondering if the problems were part of the hack job or just circumstances of mixing old and new data from the restore from back-ups. On a positive note, I would say that the biggest lesson for the day was - enjoy the learning process. Sometimes that is fun and sometimes not, but the cool thing is, if you enjoy learning, it will always make you better. Pretty cool. Long day. |
||
| Shop 3959 |
|
Adilas Time | 9/4/2018 |
On the morning meeting with the guys. We started out with Wayne asking questions about payee/users and how they can and do criss-cross and how they can cross between corps. We talked about options and why we did what we did. We got in to migrating parts, items, and PO line items. We then has some conversation about splitting up databases, indexing, and other processes that could either optimize the data processing and data retrieval process. Calvin and Alan popped in, they were working on labels on the content server. Alan helped Calvin wrap some of his code in a try and a catch. It was awesome and he was able to push the cfcatch variable. That allowed us to figure out what we needed to do to fix it. Super cool. Steve and Alan - "We break things and then we fix them." Fun little saying. Alan would like to rework the forgot password project. He wants to rework the security and how that process would work. He would like to beef things up a bit and make it more bomb proof. Alan would also like to work with Wayne on breaking code into smaller blocks and working in a more MVC (model view controller) type model. Basically, making baby steps and making things into a more object oriented code base. Alan was talking about encapsulating and modularizing functions, data, and components. Lots of code reuse and minimal duplication. Question - Build new or build on what you have? We are leaning towards refactoring existing code vs re-writing new code. Adilas' goal is build as if for years. We were talking about sub inventory and taking that whole new level and pushing it out into an object oriented model. We also talked about implementing Wayne's testing framework along the way with the new changes. The goal is trying to limit the number of times we are re-writing the same thing. We want to reuse code as much as possible. We talked about strengthening our foundation so that it could handle more weight and also allow for flexibility and fracturing, which will still occur, no mater what we do. Light talks about black box code and who pays to keep it updated. There seems to be two different levels. There are critical updates and non critical (optional) updates. We need to figure out a standard procedure to deal with custom code and black box code. Sometimes, if we have a problem and we are forced to think about it, we can usually come up with a pretty good solution. If we wait too long, we are forced into emergency surgery and sometimes that is not the best approach. We want to be pro-active on our approach and on our development. Steve and I were talking about some hanging projects... One is the invoice due dates and watching for outstanding receivables (David and Shari O. really need this). This was a Russell project that only got half baked. We need to finish it up. The goal there is for us internally, to be able to see what companies owe what and what the dating is. Then once it gets to a certain level, we could prompt for payment and/or be able to shut things off. We also talked about how it takes a whole village to raise the upcoming generation. We are really trying to build the adilas community and adilas family. We have many talented persons who are playing the game along with us. |
||
| Shop 3960 |
|
Adilas Time | 9/5/2018 |
Got on the meeting early to work with Steve and Alan. They were looking into some server issues with the data 5 box. Alan was on the box and Steve was browsing through the web. They were running checks and looking at things. Most of the corporations were doing fine, the problem was with one of the bigger ones. It seemed to be at the database level. If a super huge query was being ran, it was clogging up the queue to run other database queries. Alan ended up looking into temp table sizes, heap sizes, and max levels of memory that were available. He made some small modifications and we fully rebooted the server. When it came back up, it seemed to be running much faster. Alan then went to all other servers and adjusted database max levels to match the new settings. In a small way, this is just part of the performance tuning that needs to happen. Basically, you run into a wall, figure it out, and try to expand the corridor. Shari O. popped in and we had to look into a small issue on the data 1 box. Alan was on the box and we had a table that had locked itself. We did some repairs and were able to get the table back up and running. Wayne popped in and had a few questions. Dustin then worked with Alan to get some JavaScript rounding errors taken care of. Alan and I then started to look into the sales tax updates for other tax 6 through other tax 10 (new custom tax fields). This is one of the final steps in the sales tax changes that we were making earlier this year. |
||
| Shop 4013 |
|
Meeting with Alan | 9/13/2018 |
Alan and I had a small meeting after hours in our hotel room. The general topic was were are going and how are we going to get there. This is mostly ideas... but some of it is real and may come in to play as we go down the road. - Alan noticed that there are special headers in the old AFB settings pages. We may need to swap those out. These are the snow owl theme settings page, the ecommerce settings page, and the custom email settings page. - We might need a new level between black box (custom), bulk black box (them), and the classic. Sometimes we need an option but we don't really want to go to a black box per corp - Kinda like the shopping cart view... we have multiple options to choose from and that is tied to the personal settings. - Maybe hire a designer to help with CSS and user interface stuff - What about an adilas fracture account - Are we in the race, out of the race, or working on something else? - Where is the puck going to be? - What are our goals? - What are our defined roles & how does that play out? Currently, things are pretty loose and multiple people play through the different roles. - Who is going to do custom? - Goals and roles - those are big subjects. - We really want to get back to the custom database fields (show/hide, sort, name, alias, require, custom instructions) like we did for customers. - We really want to do a similar things with the reports. Imagine a way to select what fields show up, what order, what base or starting filters or criteria, pagination defaults, etc. That would be really cool. We already have some of that in the save your own reports pages, but it would be cool to make that happen on a page setting level. Basically, here is what is available, what would you like to see and how would you like to see it? Great idea. - Just a thought... what if we stopped custom coding for a while? It sure would be nice to be able to use all hands on deck for certain internal projects. As a side note, custom code has become part of our model. - Maybe try teams - There will be growing pains - The view cart page mixes black box technology and corp-wide settings and personal settings. We may end up with more hybrid type options like that. - In general... we have really taken on a lot... people want us to keep building both out and up... question for us, is the core strong enough to support that? - What would it take to stabilize certain parts of adilas? Some of the pieces haven't been touched in years and very stable. Other parts still have virtual wet paint and are still changing. The goal is to get some of those morphing pieces to become more stabilized and steady. - Education and maintenance may be more important than new features - Some of the reps are getting sick of training the same things over and over again - Go through the whole system and black boxing pages and adding icon menus - What if we went back to the web_page_id. That field was originally designed to be a page specific id number. We could then tie-in in help files, videos, page level settings, etc. Every page in the system would have its own id number. - Working in strategic teams. Say teams of 3 like Alan, Wayne, and Brandon. Or Bryan, Wayne, and Alan. You get the idea. - Balances...moving balances - We have seen problems with planning too much and planning too little - there needs to be a balance. ----------------------- Fast forward to the next morning... Friday, 9/14/18 - Just keep going and don't do anything crazy - let it keep cooking and growing. - Maybe have a contest to see where we are going and what ideas we have. |
||
| Shop 4003 |
|
Adilas Time | 9/17/2018 |
Back on the morning meeting. We did a light summary of the training event and talked about what else we could do next time. We are happy with the turnout, energy level, and the topics that we covered in the Denver training event. We are already talking about going to Phoenix, Arizona, in January for the next training session. Alan, Steve, and I got in to looking into some pagination values and how to quickly show the correct number of records. That took us into some of the Snow Owl data tables and looking around. We also talked a little bit about getting into the graphical homepages and showing totals, reports, graphs, charts, summary data, etc. If you do a search for "graphical home" on the developers notebook, there are a few older entries. What do people do on the invoice homepage? They want to see counts, totals, and problems (that way they could fix the flagged records). We may want the data just to display the last 7 days vs the last 30 days (current page load). We could still show the totals and counts, but we would only show the actual data that is needed. Going back to the pagination stuff... We found a small bug in the older pagination vs the newer Snow Owl pagination. Pagination is a term for showing the next page of n (some other number of total pages). The problem seems to be that the system pulls all the data but only displays a certain number of records. The page can only then work with the number of showing records vs the number of records in memory (show vs memory). Anyways, we were looking into some options there. Josh popped in and was saying that most times, people are only looking for the last few entries vs the last 30 days worth of data. We may be showing too much and making the servers work too hard for something that may not even be needed. We need to head to a quick snapshot of the data and totals and then allow them to drill-down and get deeper if needed. We had Wayne Andersen pop in for a bit. He had some questions about servers, setup, performance, and security. He is working on some of those pieces. We authorized him to look in to setting up some play sites in the AWS (amazon web services) virtual environment. We want to see what that looks like. We also has some light discussions about how awesome it is to have some of the boxes completely separated and setup as a standalone environment so that all of the corporations (worlds) don't catch the same cold (viruses, database problems, traffic problems, etc.). Good talks with both Wayne and Steve on some of the topics. Towards the end of the session, Steve and Dustin were working on reporting batch numbers out to the state tracking systems. We talked about a way to push and send over hidden details and then how to gather up those pieces and make our own summaries from the data that was submitted. We pushed up the pagination changes from earlier and then did some light testing. Recording notes and wrapping up the morning meeting. |
||
| Shop 4005 |
|
Adilas Time | 9/20/2018 |
On the morning meeting. Steve was talking with all of the guys about all of the different projects. Lots of good stuff going on. - This is somewhat new, but we may need a transactional PO (on order and maybe even pre-payments on inbound inventory) just like we have a transactional invoice (QTI - quote to transitional to invoice), this would then be mapped directly to the balance sheet. This includes a new PO type, tracking the period while in transition, and then being able to flip it from the transitional period into a real PO that hits normal inventory and normal payables (if not fully paid off). Anyways, we have a working model on the invoice side with the transitional invoices (work in progress and pre-paid stuff). We may need the same things for the PO and ordering side of things. - Wayne popped in and showed Alan and I his database migration tool. Pretty cool. - Creating a test suite... what pages and/or sections do we want to visit and check before releasing a new server. This will be really important if we are changing versions of software. We may want all of the developers to chime in on this list and include it in the test suite. Think - if I were going to a newer version, what pages and/or functionality would I test? - Alan was talking about some of his query optimization and query tuning. As part of that, he had to pull down some bigger test data sets to run the queries against. Our smaller, normal test data sets didn't give him much to work with. After the guys came in and gave their reports. We all split up and worked on our own projects. I was in testing on the final changes for the sales tax stuff. This is the dynamic naming and introducing custom taxes 6-10 (5 new custom tax fields). |
||
| Shop 4078 |
|
After hours data migration | 9/23/2018 |
Wayne and I got on an after hours migration task that was scheduled. We were running Wayne's cross-server database sync tool. This was the first time that we have run this program live. It has all been test data prior to this run. The program ran without errors and we checked record counts and all seemed to be good to go. We flipped some switched to point the corporation from the data 3 server to the data 8 server and then logged in. All of the data looked great, except for one primary table. Because everything wasn't perfect, we re-pointed the corporation back to where it was originally, and disabled it on the new server. We will check that one bug and then reschedule the migration. We want to be certain that everything transferred correctly. Wayne will be reaching out to the client to let them know that we need to reschedule. No harm done. By way of a history note... This corporation was supposed to migrated almost a month ago with some other corporations. It was left off of the list of a multi corp migration process. When we do this, a normal migration - in the old way, we have one shot at taking any number of corps from one occupied server to another, unused or new server. Because this corporation got left off, we basically started all of the other corporations using the new server and thus created potential id conflicts (auto id numbers per corp). Within the first 15 minutes after we opened up the new server, they informed us that we didn't migrate one of the corporations (it was completely left off the list to migrate). In that small of a window, already 6 tables were unable to merge without id conflicts, thus blocking us from migrating the data between servers. In the past month, Wayne has been working on a database sync tool that crosses between servers and non-destructively mirrors and duplicates the data without hitting the id conflicts. It has been a major undertaking with multiple test runs, one-on-one info sessions, lots of emails back and forth, and writing a complete program to fully automate the process. The tool is amazing and will end up saving us thousands and thousands of clicks and hours and hours of developer time. Today was the first live run. I'd say we hit about 95%. With a little bit more tweaking, it should be fully ready. Kudos to Wayne and his cross-server database sync tool. I'm excited to see what it can do when it is fully done. |
||
| Shop 4022 |
|
Adilas Time | 9/24/2018 |
On the morning meeting with the guys. Steve wanted a report on Wayne's cross-server database sync tool. We reported and talked about some future options and where we want to go. Lots of potential there. After that, Dustin and Josh started talking with Steve about some of the Metrc stuff that they are working on. They are making some great progress. Steve was the leader there. He knows his stuff because he has been in there in the trenches on implementing the Metrc and state compliance stuff. I was doing emails and light tech support. We have a client who is wanting to charge some special fees based on certain payment types and then not have those new collected fees show up in revenue. That is possible, but kinda tricky due to the mapping of non-revenue based fees and still having the fees show up as an invoice line item. I also was working with the guys on the Bear 100 mile race and getting their runner list for this years race. The Bear 100 mile race uses adilas as their race (leg and aid station) tracking software piece. Lots of different projects. Eric checked in and we chatted on the phone for a bit. He has a random error coming from one of his custom shopping carts. We will look in to it more later on today. Shawn popped in. Alan popped in and chatted with Steve. It seems like all of the guys are going in a good direction. |
||
| Shop 4042 |
|
Adilas Time | 10/8/2018 |
Alan popped in and showed us all some demos on the new invoice homepage (with graphics and charts and summarized data). A couple of us saw a demo last week. Everybody else was just seeing it for the first time. We then went into a discussion on permissions and setting those per user per session. Alan was showing us some new functions and working with database access objects (DAO's). Great demo and discussion. Wayne popped in and reported on his database migration project. He took some time and explained some of his process and also told us about some lessons learned. He spent some time talking about unit testing and doing test based or test driven design. Good stuff. Steve and I briefly talked about Calvin and the adilas label builder. We talked about rounds, versions, and where it still needs to go. We are all on board and headed forward. It is fun to see all of the projects that are coming down the pipeline. We have some other clients that have requested some backorder and shipping pieces. They submitted some specs and requests over the weekend. We will be looking into that project and breaking it into smaller pieces and seeing who we can get on the projects and who will help fund what parts of it. Later on in the session, I started looking through the email and attachments that they sent us. As I got deeper into this project, there may be some pieces that we could do internally (all adilas clients need) and other pieces that are fully custom. I put the ball back in their court and gave them some contact info for a couple of the developers. I also tried to lightly let them know where I could play without charging them. If it goes beyond that, I would have to charge as well. Basically, I will help my guys and do some initial stuff to get things going for free. If it goes deeper than that, I'll have to charge them as well. |
||
| Shop 4035 |
|
Adilas Time | 10/29/2018 |
On the morning meeting with Steve. As we were going through emails, we had more requests for custom homepages and even some users wanting to go back to the classic invoice homepage vs the newer graphical invoice homepage. We then started talking about all of the different levels of custom... We went into corp-wide settings, group settings (12 main player groups), page level settings (page control - how does it look and what does it contains and how does it work), and clear down to personal settings. That got us into a small talk and conversation about an adilas "fracture" account. This is a concept of breaking everything down into mini pieces that could be stringed and/or put together in any combination. This could include pre-sets, pre-built options, special skinning, etc. It could also get into real in-line database extensions, themes, core black box options, etc. What we are really selling is... We have tons of things pre-built and have a viable solution that has tons of functionality. This is ready and out of the box. We then offer people the chance to build their own application and virtually extend the functionality to what they really want. Basically, Steve was talking on a sales level, and was thinking about having a number of checkboxes... when meeting with a company, you could virtually check the boxes of what we have, we could also allow them to then pick and choose what they want to add on. Basically, we, as adilas, could tweak out our own product and create all kind of custom wire jobs. We need to apply our own client filters and see who wants to play. We don't want to get over our heads, but we have a great number of guys who can do and handle certain pieces. We have a solution that is usable, right out of the box. We also have a platform that is customizable and moldable (like clay). Steve was also talking about selective selling and really selling our model vs just the system. Not everybody is a fit for what we do and/or offer. Idea from Steve... Run the system for 6 months and get good at the system. Then come back and tell us what you want to tweak out and/or change. People want major functionality... however, they also want it to look a certain way (how pretty is it), they also want a level of control (what can they tweak and change). Function, form, and control - Alan was mentioning the word "Control" - that gets clear down into that fracture type level. We could have preset templates, show/hide settings, toggle on/off settings, permissions and sub permissions, main pieces, sub pieces, and even show/hide of the different modules. Currently, we have everything available... we may actually want to look at module level controls. For example: do you use payroll? do you use stock/units? do you use x or y? Idea from Alan... What if we did some testing on new users and had them do certain tasks. We then see how intuitive the process are. This would be a refining process and then work from there. As a side note, we have been adding on for years and years. That is our current model. Maybe we need to rework our inter core and make it more module based and then be able to show/hide and/or be able to toggle things (full sections and/or pieces) to an on/off level. We also talked about packaging and limited packaging of the system... For example: The limited package, the standard package, the deluxe package, and the mother load... package. Not sure what to call things... but it could be really cool. Basically, it all exists, we just show it (smoke and mirrors) in certain ways. Based on the package style and/or level, we could show/hide other pieces and/or features. Another analogy is a race car engine and then we offer the body styles like cars, motorcycles, vans, trucks, semi trucks, or even UFO's (see attached for an older image). Adilas has a lot to offer... but what if I only need it for this or that? It sometimes feels like taking an army tank out to hunt birds, say something like pheasant hunting or duck hunting. Almost an over kill. What if we could dumb it way down and make it more approachable. Make it into smaller bite size pieces and then let them get deeper if they want. As a side note, like the ice berg analogy, we only show the most basic pieces. Then, if they want more, we allow them to get to it. Maybe either offer certain packages and/or hide everything by default and make them turn it on (at a corp-wide or world level and also at a payee/user level). Steve - how do people want to buy things? We then need to cater to that level. See the photo gallery for an inverted funnel analogy. Currently, we have people enter with all options (like the top side of the a funnel) and then have them select what they want to get to the smaller level. What if we flipped that model and started out super small and basic... then they could either buy and/or turn of additional modules and/or features as they need them. So, basically, we start super small (like the bottom of the funnel) and work outward (getting bigger like the top of a funnel). Alan - would like to do a cognitive walk through... What path do they take to do a task? Where did we want them to go and/or do? Where are their eyes on the page and where are they spending the most time? How easy was it for them to follow the path that is wanted? The cognitive walk through would include a small user group, and then the persons being tasked with the tasks would have to explain (verbal and/or written) what and why they are doing what they are doing. Basically, getting into the minds of the users and what they are seeing, focusing on, and/or actually doing. Wire frames (interactive outlines) and getting to the basic decisions and taking that research back to the coding project. What is the phycology behind the decisions. What are the human levels that we might be missing and/or could really enhance just by display, menus, and structure. In Dustin's words... "putting rails on things". We also talked about doing different cognitive walk through groups (users not familiar with the system) and how they would do their own different tasks. If they get stuck, why? What were they looking for and what were they expecting? This is more of a cognitive (brain activity) exercise to see what the thought process is and/or could be. One of the challenges for us might be - so many different business verticals and so many different choices... we might need to get a sample and make sure that we aren't hitting just one niche and/or personality type. Lots of different flares and possibilities. We would like to match who would be using the program with what we would be asking them to do. This testing also has some down-sides, such as preconceived notions, using other existing and/or older products, and actually testing people who would be using it. Alan and I were talking about who we knew and what resources we could tap into to get some basic testing. Just throwing around some ideas. We added in a new community funded project to get in there and do some research and some of the cognitive walk trough's. After that, Alan and I were reporting on our different projects. We love the options of having black box code, but there are teeth to that as well. We are starting to see the black box section as a huge time sink for the developers if they are making core changes. We have code that is not in master (in the main code repository), it could be changed at any time, and no one knows who has the last cookie. The developers work directly with the clients, and thus, they think that they have the latest code, but a new change could have been cascaded through to the other pages. We definitely need the black box code options and framework, but we need to eliminate as much duplicate code as possible. It is becoming an issue. It is not on fire, but it becoming a thing that needs to be addressed. Wayne popped in and reported on the database migration project. He is planning on running some new tests tonight. He went backwards and did some major back testing and going back to a test driven design philosophy. He said that he got a great reminder on why we need to stick with a test driven design philosophy (watching out for the little things). The data migration process is super deep... it is basically allowing two different servers to run as they are... then in the background it takes data and tries to re-sync the data to get a perfect match, even though they are different databases with different auto id numbers. That is advanced mixing and blending. We got into a bigger discussion about standardizing data and using special tables such as flex grid tie-ins and custom dates, numeric, and custom text fields. Some of those tables are great double agents and/or chameleon type tables (they switch as needed). Good stuff and it really seems like Wayne is trying to think beyond the current project. We are constantly chasing a moving target... part of the fun... :) |
||
| Shop 4039 |
|
Adilas Time | 10/30/2018 |
On the morning meeting with the guys. Steve reported on some progress with his extraction (production) pages (internal build PO's). Wayne popped in and we had a small discussion about the data 8 server. It seems to be having some random problems. Not sure what it is. When it is up, it seems fast and slick. When it is down, it just grinds and/or stops. On the phone with tech support with the server guys. I made some small changes to the PO line items page and added an outline type numbering system. This only comes into play with parent/child inventory. |
||
| Shop 4025 |
|
Adilas Time | 10/31/2018 |
Happy Halloween! As a fun side note, both Steve and Josh have Halloween as their anniversaries. They were able to chat and have fun talking about that. Calvin popped in and we got some API stuff working on the adilas content server. He needs that functionality for the new adilas label builder app. Good stuff. Alan, Dustin, Josh, Steve, and I were on the morning meeting. Steve had a couple of questions about some emails that were going around. We pulled in Alan and chatted about some database restructures, re-indexing of records, and full table rebuilds. We then talked briefly about a client that has a bunch of custom code but hasn't really been able to get things going. They are currently not paying their monthly bill and not responding to the David B. and Shari O. We have decided that we need to turn them off as it is costing our company trying to chase their company. If they want it, we can easily re-flip the light switch back on. Wayne jumped in and we did some checking on his database migration code. We logged into the dedicated server and ran a couple reports. All of the data looks good and he will be contacting the client to let them know. This project has been ongoing for about 2 months now. Basically, we migrated about 10 corporations off of one of the shared servers to their own dedicated servers. Well, once we finished and released the new dedicated box, they came back and said, what about this other corporation that we had no notes and/or record of. Because it missed the normal migration process, and the new server was already live and consuming auto id numbers in the database, we couldn't do our normal migration process. Instead, Wayne had to write a new program that allowed for both servers to keep running at full speed and still be able migrate and copy database records across between servers. That may sound easy, but think of all of the auto id number and foreign keys based off of the auto id numbers that could get messed up. This was a very deep project. It looks great and seems good to go. That is awesome. We intend to use this same program (actual software we have to run on the physical servers) to help us migrate other clients off of shared environments and into either other shared servers and/or to their own dedicated boxes. That is a huge break through for us. Good stuff. After that, I jumped in and did some emails and tech support stuff. Towards the end of the meeting, Calvin jumped back in and we made two of his permissions go live for the adilas label builder. We then did some light testing on the live servers. It still needs some lovin, but we had a successful live test between data 0, the content server, and Calvin's adilas label builder app. That is pretty cool. He was going to make a couple changes and then get back with me. Pretty cool and some great progress. |
||
| Adi 1435 |
|
Invoice due-date project - also A/R controlled page header | 11/6/2018 |
10/6/22 Videos for the auto email, email report and invoice due date functions. 10/6/22 Page URLs for completed project. Note: These URLs are primarily from the auto email part of this project. The URLs for the email history report, use credit terms and invoice due date project were not included as it would take a significant amount of time to dig up this past information. Large edits 1. public/afb_email_preview_action.cfm 2. public/auto_email.cfm 3. publictop_secret/cfc/Services/EmailService.cfc 4. top_secret/cfc/Daos/EmailDAO.cfc 5. top_secret/secure/classic/email_report_body.cfm 6. top_secret/secure/email_report.cfm 6. top_secret/secure/afb_corp_email_home_action.cfm 6.top_secret/secure/afb_corp_email_home.cfm Small edits 1. Application.cfc 2. public/auto_email.cfm 3. top_secret/cfc/search_15.cfc 4. top_secret/cfc/security_4.cfc 9/29/22 The auto email project was pushed live and tested. It will be used by Shari O for a week or so then the automation will be added to each of the servers by Wayne. The auto email project was completed and pushed to data 0 about a month ago. Several bugs were identified by Bryan and Shari O, but were put on hold as other higher priority projects were being completed. 6/13/22 Met with Brandon to clarify some specifics on the 2.2 plan. 2.2 Email history report (email_history_home) 1. new table (not the same as invoice history) a. new update that creates table I. Look at tables for examples (history and text) II. Email_history table variables – like custom_text table: email_history_id, corp id, payee_id, datetime, app_type_id, main_id, table_name, special flag, history_note (13, 3076, statement). III. Types of special flags: Invoice, quotes, pos, statements, customer, eCommerce, custom, auto due date, multiple invoices. 2. Set up history capture on email a. design email capture (from/to email addresses?, status: success/failure) b. search for pages to put history code on by using adilasuniversity.biz c. add email capture on all pages 3. Create email reports page a. be able to search by: type, time period (day, week etc). I. model after invoice_home_basic.cfm 4. Show email history on invoice history, PO history, quote history, and statement history reports (invoice_history.cfm etc). a. bold line below reports saying “Email History Actions” and then email reports b. ? auto_sent column in email_history. 5. Report on my_history.cfm page a. Tie to invoice app type similar to how statement works. 6. If it goes out manually it also goes into the history. 5/31/22 Met with Brandon and developed plan for part 2. Broke it down into 3 sub-sections 2.1 Add setting (Use Credit Terms) and if selected change due date on Cart 2.1.1 Add "Use Credit Terms" settings to Corp Wide Settings 1. create database update and add tiny int 2. research standard invoice credit terms 3. standardize credit terms on Corp Wide Settings, add_edit_customer.cfm page and Corp Email Settings page 4. Add verbiage to Corp Wide Settings Page 2.2.2 Use Credit Terms to switch out default session due date 1. Working on cart_4.cfc 2. check if "use due date" has been selected in settings 3. get due date session default 4. check if "use credit term" has been selected in settings 5. if "yes" get credit term variable. 6. check if a number exists in it and it is less than 100 7. if "yes" switch out the session default variable 2.2 Check due date and automate email (not planned out yet) 2.3 Email history report (not planned out yet) 5/27/22 Met with Shari O regarding moving forward to add auto email to the Invoice Due Date function: 1. Bug on invoice due date: the due date is showing current date. Is this a normal bug or happening at server update? (1:59). 2. Can we make due date default "Credit Terms" on the Customer (add_edit) page. If Credit Terms is different than due date it will trump. 3. Email template "due date" reads from due date or credit terms. 4. Different (edited template if paid). Reads from due date or credit terms. 5. Auto send out reminders if 5 days from overdue. Adilas is due upon receipt, late fee at 30 days and shut down at 45 days overdue. Alan is making good progress as of August 2019. This is an invoice due date project. It is a prep step to get a corp-wide header that could go from server to server to help prompt for overdue payments. Basically, a way to speed up the adilas receivables or A/R accounts. Once the invoice due date feature is in place, we can then figure out the aging of how old an invoice is, regardless of payment history. Once again, this is a prep step for a bigger project, but much needed. Russell and Brandon started the project back in December of 2017. Due to craziness, it got almost finished and then mothballed. We (both Brandon and Russell) picked it back up on 2/23/21. Project turned over to Bryan on 5/17/22. See media/content for a 26-minute video overview of the project. |
||
| Shop 4139 |
|
Adilas Time | 11/7/2018 |
On the morning meeting with the guys. We had both Wayne and Calvin pop in briefly. Most of the morning session, Dustin and I were working on his code to auto increment these huge RFID tag numbers. Basically, you start with a huge 24 digit and/or character tag and then increment just the tail end. It has tons of zeros, alpha/numeric values, and an incremental portion. We spent a lot of time going over the sub loops and loops within loops. We got it and it seems to be working great. Around 11 am (ish), Steve was showing us some cartoons about a dog. Anyways, Kat, Danny's wife, was telling Danny (one of our sales guys and label developers) that adilas was kinda like a dog. You tell it to go and do something, and it tries to go and do it. Anyways, Danny took this idea and worked with a guy from his church and came up with some fun cartoon dog images. Really fun. The artist's name is Naters Art from the Salida, CO area. Adilas is the word Salida spelled backwards. Kinda fun. Anyways, Naters came up with some great images of this dog, rolling over, with a bone, searching, and tilting it's head. The developers on the morning meeting were saying that they could see some of these images being used as icons while waiting, searching, success messages, error messages, info messages, etc. Lots of good laughs. See attached for a screen shot. 11 am - meeting with Gene Spaulding with the SAL Management Group. GoToMeeting We started out the demo and meeting with letting Gene show us around in his spreadsheets and what was connected to what. Really cool and he has taken things to a huge and super deep level. Steve and Gene were able to briefly talk about how both of them started at the spreadsheet level and then eventually grew out of that and into a database type technology like adilas. Good stuff. One of the main pages that they had was titled - Census and Roster - who is where and what is what (simplified operational and accounting data). This fed the rest of the reports and pages. Steve - what would be mission critical for you guys? They answered that it was the census and roster reports (getting data into the system). Simple screen to gather that information and then disperse it as needed. They do have a 3rd party that does all of the onboarding platform stuff. All the paperwork, contract stuff, legal stuff, etc. They have looked at some of the big huge platform applications out there... they are kinda looking for something smaller and maybe more custom. We did a demo and I think it went pretty well. I had Dave Forbis and Steve on the call with me. They had a controller and head manager on the call. Good back and forth and we had some fun. |
||
| Shop 4134 |
|
Adilas Time | 11/13/2018 |
Wayne and Steve were talking about servers and some of the new updates that are going on. Wayne is helping to fine tune and monitor the servers. He wants to be in charge of that portion of the puzzle. He is very good at it and knows what he is doing. Steve and I are trying to encourage him to keep going in that direction. Some of the discussion items were dealing with servers, up-time, redundancy, database table locks, response time, active vs passive monitoring, and empowering our users and clients to view stats (maybe limited views) on the server. There was quite a bit of talk about new news and updates talking about the server monitoring and even possible mirror and/or redundancy back-up and/or mirror server options (insurance and roll-over technologies). Wayne was asking some great questions about the current model and where we want to go with things. Steve was responding and answering the questions. We left off with a charge on Wayne to get in there, dig around, and come back with a plan. We may end up rolling some of the new changes out over a series of months. Good stuff. We touched base with some of the other developers on the meeting and then broke out into our own work sessions. I was working on the sales tax branch and trying to cascade new sales tax changes through the black box pages. As a fun side note, there are around 400 (ish) black box pages that are part of the master code branch. That doesn't even include ones that are created and uploaded without being merged into the master branch. What that tells me is, that our clients like custom options and that section, black box or custom code, is a huge part of our model. It can be a pain in the rear some times, especially if we are trying to update things, but it also fills a need and our clients seem to like the options of being able to customize things. That is awesome. Once everybody left the meeting, we all just worked on our own little projects. I was doing tech support and follow-up on some sales calls. Towards the end of the session, Steve and I chatted briefly about the client who may want to do some tracking on their assisted living facilities. We talked about maybe setting up a play site for the assisted living and running things with locations, elements of time, etc. Lots of good ideas. We also talked about the adilas label builder that Calvin is working on. We are getting close on this round of the project. We would like to see where all of that goes and what comes out of it. We are looking to close out phase one and then start using it to see what else may be needed (round two or phase two). Steve - we are a solution for solution minded persons. We are really seeing that the clients that like customization, they tend to be some of our greatest clients. Very interesting. We are also seeing that some of the reps are a great resource and are throwing some ideas and monies at things (pieces of the puzzle) that they need and/or want. Some of them are getting funding from their clients to help push things forward. Random idea... what about opening up the door to our customers to get their own developers and let the custom side of things grow a little bit deeper. Maybe use the adilas market and let some of the independent developers run with things a little bit. Training - we were talking about ideas and timing. Things are a little bit crazy right now, but we don't want it to get out too far before we circle back around and setup some more training. We were also talking about costs and paying for that. On a different note, we have tons of hidden benefits like hooking up Marisa and Drea on training. We also have Calvin who was at the last training and got tons of great info and feedback about his labels and Gmexting (group mass texting). Lots of hidden benefits and getting people trained and more involved. |
||
| Shop 4137 |
|
Adilas Time | 11/14/2018 |
Just for fun... Steve, Dustin, and I were talking about the cartoon adilas dog concept. Steve had a colored prototype of the little adilas dog and we were talking about it. See attached for a colored prototype of the little dog adilas. As a question... what will I train my little adilas to do today? Steve was working on some changes for ecommerce and being able to show tiered pricing out in ecommerce. Alan popped in and had some questions about in-line discounts for my cart favorite buttons. We are trying to see where they need to be attached. We are seeing three possible options. One is on the exact search (known item or known sub item), as a standalone or cart as a whole option, and also as part of the smart group buttons (tiered pricing). Alan is going to check more into this and get with a client who is looking for these options. Wayne Andersen popped in and help both Alan and Brandon with some server stuff. He is implementing some server monitors that check services, CPU usage, RAM memory usage, database activity, and other monitors. He gave Alan and I a small tour and had us setup some things, in order to play. |
||
| Shop 4138 |
|
Adilas Time | 11/15/2018 |
Talking with Wayne, Bryan, and Steve about new servers, specs, and the configuration process. Wayne was talking about a virtual recipe for the servers and then using a program called Puppet that helps with special configurations and even bulk server setups. Bryan has been helping us with some server setups. We are trying to get things transferred over to Wayne and let him run with things. He really wants to do that kind of stuff. He used to do it for his other company that he worked for. - Looking at server configuration options and such - lots of ideas and options. - Steve had some questions about inbound and outbound API socket access (external traffic above and beyond what we know about and/or control). This could be outbound pieces to state compliance tracking systems and/or inbound ecommerce requests or inbound API socket calls (general data stuff). Lots of unknown potential and/or uncontrolled amounts of traffic (in/out). That is a big variable and is widely unknown. Steve doesn't think we have even remotely seen what is possible and/or on the horizon. - Wayne was talking about a frontend software application called Cloud Flair or Cloud Flare. It helps to filter the traffic good/bad and what actually hits the servers. We were talking about protecting servers against attacks and what not. - We were talking about different models where we break up the databases and keep things all on their own servers. Or we could build super structures and configure a super Linux box with a non web facing database server. We could then have a number of smaller web servers (code files) that connect to the super structure. See the attached for a couple options that we were drawing (possible configurations). - We were talking about amounts of time, costs, and resources to duplicate things and spin things up and then manage them. Currently, we are on a two-week to a month spin up process for a new dedicated box. We would love to get that down to under 24 hours and/or something similar. - Steve was talking about doing some costs analysis, prototyping, and calculated experimentation. Lots of good ideas but still lots of unknowns. We need to be smart as we venture forth. We need to keep the main adilas ship rolling along so that we can fund some of these new experimentations. - As we improve the process, we are planning on circling back around and bringing the older servers and older software versions up to speed. We may end up cycling through the servers and slowly bringing them up to a new standard, as that get established. Lots of new ground. - As part of the meeting, Wayne was showing Steve and I some of the Nagios (monitoring server) and its stats. We were seeing what updates ran and did not run, what CPU usage was going on per server, and what database traffic load was going on per server. Some of the servers, are close to 2 million queries since the nightly reboot at 1 am. It is only 10 or 11 am and already they are close to 2 million queries into the day. That ends up being between 30-50 (ish) queries per second as an average. That is tons of traffic. With some of Wayne's tools, we can now see some of the stats and trends. Pretty crazy. |
||
| Shop 4149 |
|
Adilas Time | 11/19/2018 |
On the morning meeting with Steve and Dustin. We started out with some light catch-up on what everybody did over the weekend. Steve had a question on some ecommerce stuff. He is working on getting some tiered pricing out into ecommerce. Bryan Dayton came by my house to get the Dymo label printer. He is working on some custom labels for a client. Wayne popped in and gave us some updates on the servers. Having someone dedicated to watching and helping the servers out will be huge. Alan was on as well, working in the background while the meeting was going on. |
||
| Shop 4152 |
|
Adilas Time | 11/20/2018 |
Steve was showing us a small demo of some of his tiered pricing out in ecommerce. We had Kelly come on and gave him some feedback. It is literally crazy to hear what they, the users and consumers, really want. It gets super crazy and they want a multi-flipping gymnastic display with super easy functional and beautiful at the same time. The deeper we go, the more things are really flowing and trending towards more configuration settings and then being able to display things in a really simple format. Another thing that I am seeing is the need for specialized and specific interfaces, per business vertical. It is crazy how much people want and how quickly they want it. That makes for a tough mix. Creating a layered approach seems to work better. The user experience is huge. On that same level, we are seeing a growing need for a developer to code it and a designer to help with flow and the user experience. As Kelly and Steve got deeper in the ecommerce demo, they, were asking for more searchability, more multi select, more JavaScript show/hide filters and menus, etc. They want the moon and even demand it. Kelly would like to do a different session where they, (Steve, Kelly, and Dustin) go in and do a look around on other ecommerce sites and get ideas of good/bad/ugly and then make a plan from there. These are some questions that are going on in my head, who is coordinating all of these decisions? How is it all going to work and play out? Who is funding what and who is driving what functions and features? Assuming that we have the funding, who is going to plan, design, and code it? Huge demands and huge questions. The conversation started rolling over into complaints about look and feel, server up time and/or perceived up time, and other perceptions for the users. They were talking about levels and costs to get to those levels. It then got into a discussion between web, on-sight servers, software, hardware, hybrid solutions, apps, mobile, etc. What are the expectations and what is expected? Kelly wants us to get pricing on what it would cost for this and that. Steve came back and was talking about how the system keeps growing and developing and who is going to pay for this and/or that. Kelly then was talking about costs and choices that need to be presented to the clients. If you want this and that, you need to pay for this and that. If you only want a smaller set, you would hope that you only need to play for that piece. Steve was talking about the cost of, even say, your worst employee? It most likely will be $2,000 to $5,000 per month. What is the cost of the adilas system? Say maybe $200 - $400 per month. There is a known disconnect, the adilas system provides tons of functionality, but yet, the price is itsy bitsy tiny and therefore sometimes perceived as less important. The conversation then turned to how do we support the bigger clients and what are their needs. Wayne popped in and was reporting on servers and server stability. FTP and FTPS - normal and/or secure file transfer protocol issues. He had some questions on how do we keep the servers up to date, synced up, and how do we manage the custom code (things that are different per server or per corporation). Custom code is somewhat of a wildcard piece and/or variable per server. We talked about core adilas code and custom code and how they relate and interact. We also talked about ways to manage custom code and who has what code and/or reports (we need a system of recording who has what and what it does). We have had requests on the client side - am I running custom code? We have also had requests on the tech support side - are they running custom code? We have also had some developers ask the same question - are they running custom code? Kinda interesting - lots of different angles to cover and what not. I got a call from Bank of America to talk about some term loans and/or revolving business credit lines. I was on the phone for 20 minutes and the rep is going to be sending us some information. They have a couple nice looking products that have way better interest rates as compared with Kabbage and other high interest options. Steve and I were talking about the future of software of a service is - we do build a product that has as many permissions and features as we can see to solve the needs. The future is that the clients want to customize the results and/or the output. They all want some kind of specialized output. Each client wants to mix and blend the variables in a different way. This could be seeing the data in a certain way (report and/or dashboards) or they have a slightly different process (add/subtract certain steps). Steve is seeing that there is a cost to switch systems, so we are hoping that our clients have basically, choose your platform and then invest in your solution to make it almost your own. Custom solutions that fit people's needs and how they want to play. Sometimes with bigger clients, you actually get beat-up more and they still may not be happy. We need to find the clients that are happy with us and even bring us donuts... :) We want to find the correct level for us and our company. Bigger is not always better. From Shannon - it is an abundant model. That is awesome. Picking your battles and multi-concept decision making. That is quite the game. Fun, but very challenging. Question - who wants to play? Great, let's play. Lots of indicators, you just have to make decisions according to those indicators. Adilas is a giant idea farm. We will keep building and breaking things. That is somewhat of our model. We want to help businesses succeed. Those who want to play with that model, we love it, let's play. On the financial side, we are so glad that we don't owe anybody huge amounts of money. That is freeing to the mind and the soul. Good stuff. This is on a different note, we would really like to circle back around and see where we are at on the accounting side. Most of our current efforts are still focused on operations and operational flow and process. There is some huge potential for future growth in that area. We need to keep working on and refining our plan. The other area that could really use some loving is the user interface and the look and feel. There is a constant progression from one thing to the other. That is fun and exciting to see and even revisit those pieces. Steve jumped back into a recap of where he started with the coding and development side - simple HTML and web stuff on the old steps to success. As you get deeper and deeper, you keep needing to step outside and get deeper in the complexity and background pieces. Lots of moving pieces under the hood, but it looks super simple on the outside. Steve and I are realizing that we can't do this whole project by ourselves. We have a great little team and we are even refining things within that model. That is exciting. It is the team that wins the battle, not an individual. We are learning tons and tons about the software as a service (SaaS) model. Our plan it to keep going at the current pace, keep building, and keep listening. Our plan is to run as fast as we are able within the bounds of not running faster than we are able. We are happy to keep building up the core pieces. We are seeing numerous outside parties that are catching the vision and building out more and more custom stuff. |
||
| Adi 1443 |
|
Wayne Andersen would like to get direct deposit setup - include Craig | 11/20/2018 |
We currently do direct deposit. Research this for Wayne etc |
||
| Shop 4155 |
|
Adilas Time | 11/26/2018 |
- Tons of emails and light tech support from things over the Thanksgiving weekend. - Brandon and Steve talking about updates on people - we were talking about Shannon, Russell, and Dave Forbis. - Alan popped in and had some questions about his new projects. He is working on discounts on my cart favorite buttons. - We lightly talked about vertical (business verticals or industry-specific) templates and settings. Make it easy to cater to specific verticals. - Talking about system stats and storing that info in a daily watcher or feeder type table. We also talked about queued back end services that run on daily routines. We also talked about pulling reports and monitoring growth and changes. - We were also talking about "rules" or standards per vertical (industry). Each industry is different, and thus may need some general rules based on the type of industry that they are. Basing the pricing off of processing and storage vs charging for the code. Some users may or may not be using certain features and/or modules. This discussion ended up going into questions about what do we want to do with the adilas databases (make it bigger and better or break it up into small faster pieces). This is still an active discussion and we are trying to gather pros and cons of both. - Alan was talking about vertical and horizontal scaling - add more and more servers (distributed or cluster model) vs single server and up the capacity and resources. This lead into a small discussion on back-ups, redundancy, and disaster recovery options. Currently, we are doing somewhat of a modified horizontal scaling method. - Steve had some questions about the API socket level and what that load may be and/or take? - Alan had some ideas on risk mitigation and how to help our clients even do their own risk mitigation processes. Lots of talk about what are the vulnerabilities and how do you treat, track, and deal with those vulnerabilities. It always tends to come back to an analysis of what is the threat and how much do I care, need, want, and/or require? Talks about server up time and reliability. What maters most and what are we willing to pay for and/or spend? - We would love to show all of the corporations (virtual worlds) what their stats are and what we (as adilas) are carrying and helping them out with. That helps us show a benefit and advantage for those who use adilas. - We lightly talked about an offline adilas mode and allowing a user to use the main web system, if a problem, they could use a local copy, and then sync up things later on. This sounds awesome, but it could be a huge project and could be riddled with loop holes and gotcha's. Possible, but hard to tell what the real costs are and/or would be. - The technology wave and what is here, coming, and already gone (outdated). We are constantly riding those waves and making decisions. Alan lives down there in Arizona and could maybe pop in and check things out with the actual server farm. We could even branch out and spread out our exposure to other server farms. - We could update older servers to help with stability and up time. We could upgrade to using solid state drives, bigger processors, more RAM memory, and updated server and software packages. That could be a great upgrade for the time being. We also talked about optimizing our existing servers by tweaking settings and such (performance tuning). - We may end up needing some new training on how to configure and upgrade the things that we need. This is just a possibility, but there is an upcoming ColdFusion summit convention coming up in April 9-10, in Washington, DC. Just looking at ideas and options. Our goal is to get the most out of what we can by either upgrading to the newest models and/or versions and getting the proper training needed to make it dance and sing. ColdFusion is allowing more and more scripting languages and is gaining some momentum. - There was some small talk about upgrading from Windows servers to Linux servers. Wayne is the one that knows a lot there. Lots of possibilities. - Some new shortcuts and getting up to speed. Alan was showing us some coding shortcuts. Params, is defined, and quick conditional processing. Things like a turnary operator (one line true or false if statement - switch), elvis operator (reference something and it is able to self-define if it doesn't exist but will use a real value if it exists - less breaking code for things that are undefined). - There are many paths that we could take and would work. Let's make a plan and then work that plan. - What we do is not easy. There are so many moving parts and pieces. As we build, we keep finding that it comes back down to more and more permissions and settings. Subs of subs. Eventually, it could become simple if you get enough sub pieces built into the mix. Kinda crazy. - We are also seeing more and more needs for bulk tools and such. - We are also seeing that people are really looking for a system that could do almost everything with both global tweaks (per business vertical) and also granular control (permissions, settings, etc.). Almost a wish list of sorts. - As we get out, in the field, we may end up adding some icing here and there. Maybe even some icing per business vertical. - On black box stuff - what if we had a list of what happens and/or what black box code is running? We may need to use some kind of technology to help us monitor and/or use what black box code that is out there. Maybe a way to notify our developers, consultants, and even our users what code they are using. - Small concepts - creating an adilas fracture account - future concept once we get a few of the other pieces in place. This was an idea from Steve, clear back in 6/22/17. We would basically, allow the normal or classic adilas to keep going, and then start building out the adilas fracture accounts. Everything would be broken up into tiny modular controls but would also have bulk tools, templates, and industry specific defaults to help play the game. This subject could take up volumes, as far as other ideas and concepts that we would like to include. Super cool idea and future project. - Steve would like to see us work on breaking out users from the systems... They, the user pools, exist and can interact as needed but they become their own entity - Imagine pools of professional (adilas community members and power users) users that could work for other companies as needed. Separate users and systems, even more than what they currently are. Steve has some good ideas on that. Kinda like a marketplace for features and functions as well as power users, employees, and people talent. Fun ideas. |
||
| Shop 4153 |
|
Adilas Time | 11/28/2018 |
Somewhat of a quiet morning this morning. Steve was flying out to Grand Junction, CO, to meet with a new adilas developer. His name is Spencer. My first task of the day was getting a non-compete and non-disclosure document ready for Spencer. Alan popped in and had some questions about discounts for my cart favorite buttons. We went over some options and ideas. I spent some time adding drill-down links to advanced search reports (PO's and invoices). I chatted with Wayne about digital file uploads and importing inventory for a client. After that, I worked with Eric more on the sub special account tracking project (loyalty points, rewards, and gift cards). See attached for the latest notes. |
||
| Shop 4192 |
|
Adilas Time | 12/3/2018 |
Alan and Steve were working on some tweaks for ecommerce. They have some new code that helps generate tiered pricing code and they were debugging some of the pieces. Around 10 am, Wayne popped in and was giving us some information and an update about the servers and what things he was looking at as far as thresholds and matrix. He is really helping things out and is able to watch things and really get things more and more standardized and monitored. That will be a huge help. I'm really excited about that. Eric joined and had a number of questions. For example: How do we flag the transactions to know what type they are? (manual, double tuesday, normal, auto, redeem, etc.) What about tracking rules and history changes for the rules? What about changing things (rules) right in the middle of the day and/or middle of the transaction? Eric is thinking we may need a way to change things and then publish and/or commit changes in bulk. That would allow small tweaks to happen and then fully wait for all other changes before really committing things (stages). We talked about a few of these things and decided that we will use 3rd party error logs to track rules and changes. We also decided that we would not do the publish and/or commit changes in bulk. For now, all changes will be live as they happen, one by one. Alan and I were on the meeting and went over a number of projects that are currently in the works. We went over some needs on the sales tax project. We decided to do one more major push on that project and then push up the code and get things going. We have been close on this one for awhile, but it keeps getting hung up with the moving black box (custom code) target. Alan reported on his permission and user project. This is a project that breaks users and permissions into a more object oriented model with services, logic, and database access objects (DAO's). Basically, our existing code base checks a three-way connection of user to permission to corporation on every page in the entire system. A lot of that data doesn't change very often. So, in the background, we are spending time and resources checking relationships that are fairly stable. Some pages have between 10 and 20 permission checks. That is 10-20 trips to the database for data that doesn't change that often. So, we are starting to cache (temporarily store) the data in the session scope. If nothing changes, we'll start using session or memory checks vs full database checks. If anything does change, we reflush the session cache and then go from there. This reduces the number of database trips by tons, if you take each page, used by x number of users per day, all with active database checks and queries. Great savings on time, resources, and processing. We also went over a couple of other projects such as a round 4 for sub inventory and ways we could speed up some of the manual processes for reoccurring invoices, reoccurring merchant processing payments (credit card stuff), and tying things together in a better flow environment. Good meeting and lots of good progress on multiple fronts. |
||
| Shop 4196 |
|
Adilas Time | 12/4/2018 |
Steve and I were talking about some fun sales ideas and using the new adilas doggie graphics. See element of time # 4216 in the shop for some fun images. We got a bunch of new graphics yesterday from the artist. Dustin was showing Steve and I some of the new functionality on the cultivation side. It is a nice interface with tons of backend wiring to make it really fly. Pretty cool. Eric popped in and had a couple of questions for Steve and I dealing with mag stripe readers and integrating with loyalty cards and what not. Steve answered most of the questions. After that, Wayne and I looked over a data import on the data 6 server. We talked about some additional pieces that will help the import look and be more clean. Emails, tech support stuff, and looking into bug reports. Towards the end, Steve and I had a small chat about the assisted living business vertical and providing some guys a quote to use our system. No firm values, but we were playing with options based off of rooms or options based off of facility sizes and what not. Good stuff and Steve is excited to see where things go. |
||
| Shop 4198 |
|
Adilas Time | 12/6/2018 |
Quick meeting with Steve to go over some code changes. I spent some time recording notes and touching base with Alan on some projects and concepts. Tons of emails and light tech support stuff. Worked with Wayne, Dustin, and Eric on different projects. |
||
| Shop 4204 |
|
Adilas Time | 12/12/2018 |
Steve and I were working on a change out in ecommerce land. We were trying to get the inventory counters (do I have enough quantity) to work and alter messages based off of selling just plain parent inventory, showing parent inventory but selling sub/child inventory, or just selling and showing sub inventory. Kinda deep and we had to rewrite some code to help make it work. We had a client come onto the meeting to ask about some database questions. Wayne Andersen joined and ended up being the main key player that had the answers and basically helped the client out. Wayne is moving into the main server side point of contact. He is monitoring the servers, changing specs, options, and even scheduled tasks. Great asset and a huge help. Good stuff. Emails and other small tech support things. Wayne also helped me out with data migration for client. We covered a few micro tweaks, but most of the data is doing great and flowing correctly. |
||
| Shop 4232 |
|
Server | 12/13/2018 |
Bryan and I were working on the data 11 server and trying to get it ready to release. We had to back track and rerun some of the database updates. Some of the updates are cumulative and are built on changes of changes. Once we got everything working, the other pieces started to fall into place better. We will be passing that server off to Wayne next week to have him work his magic and tightening things up and locking things down (security wise). |
||
| Shop 4197 |
|
Adilas Time | 12/17/2018 |
Wayne and I were on the morning meeting going over serves and what not. Wayne has some big plans and is even starting to experiment on different server configurations. The next servers that we spin up are going to have a Linux box to hold the database and a Windows box to do the web and Adobe ColdFusion stuff (server-side code). We also went over some other options and even goals of where we are headed. I've been trying to keep things separated, on purpose, for years. I'm feeling better about it and I'm more willing to bend and allow some new technologies to help us manage things better and more efficiently. Good progress. Part of our server conversation was dealing with FTP (file transfer protocol), using Git repositories, Putty, Puppet, Nagios, etc. These are all server based pieces that allow for us to standardize, compare, and maintain from a single source. Some of the conversation was talking about getting rid of FTP and moving more to a repository based upload and sync for all of the servers. After we got done talking about actual physical servers and configuration, we spent a good 45 minutes talking about potential changes in the database arena and what options we have available there. We were talking different engines, table types, transactional vs aggregate (summed up data), archived data, indexing, partitioning, etc. Lots of good conversation about table locking, row level locking, locking conflicts, query speed, etc. Pretty deep database stuff. |
||
| Shop 4207 |
|
Adilas Time | 12/18/2018 |
Great morning meeting today. Steve and I started out the conversation talking about progression and who is doing what. We used to be stuck in a model where both of us were running with all of the pieces. We now have a great team and each person has their own expertise and passions. That is awesome. We spent some time going over some new things, and even some potential things that coming down the pipeline. Exciting. Dustin joined and we did some code merging for him. We had Eric pop in and ask some questions. Wayne popped in and Eric and Wayne did some testing on one of the servers together. Eric was browsing pages and clicking buttons and Wayne was watching CPU's, memory, and databases on the actual server. Pretty fun to see how things are starting to work together. Alan joined us and we chatted with him. We went over some of the code and new changes between the live inventory update section and the delayed inventory update section (new feature). We went through a number of scenarios and talked about some other needs in that area. Alan also asked about some plans and how we are going to be heading more towards version controlled deployment, testing servers, and that process. Good stuff. I merged in some database updates and ran those updates on all serves. Good morning meeting and lots of progress in many areas. |
||
| Shop 4199 |
|
Adilas Time | 12/19/2018 |
On the morning meeting. Steve, Wayne, Dustin, Eric, Alan, and I were in today. Wayne and Eric were talking query caching techniques and switching between aggregate sums and totals and non aggregated (simple transactional data). The conversation kinda went along the levels of watchers, feeders, hooks, triggers, etc. Eric was saying are we going to be building new aggregates based on the old design or are we going forward with a new design and then build aggregates off of the new design. Pretty deep data model changes. What are the impacts to those changes? One of the questions came up about testing impacts and how does that work. Are we fixing legacy and/or being pro active and moving forward. One of the questions was the po/invoice line items table. It currently has both PO lines (inbound inventory) and invoice lines (outbound inventory) in the same table. The reason goes clear back to location specific levels of inventory tracking. If no locations were ever needed, we would hold thing (line items) in the different tables. However, if you add an unknown number of locations, that complicates the data model and it get hard to be able to roll the inventory levels both backwards (going back in history) and/or seeing current levels. Going on to a different topic, Wayne and Eric were talking about a testing server and even stress testing certain queries and/or database tables. They were talking about caching queries and how often do we reboot these servers. Because we use Adobe ColdFusion, we've had to implement a nightly reboot to help flush memory. As Wayne gets into the servers and monitoring things, we are seeing that the servers are working pretty hard by the end of the day and then fully refreshing things based off of reboots. That is both good and bad. We are on purpose flushing the cache and the memory. However, sometimes a cache and/or an item held in memory saves tons of time. We still need to compare the info and see what the differences and advantages are. Like Alan said - we break stuff and then we fix it. |
||
| Shop 4205 |
|
Adilas Time | 12/20/2018 |
10 am - group discussion to talk about servers and new configuration stuff. - Currently all of our servers are and/or have been setup differently. That becomes a nightmare to manage. - The server setup is done every couple of months... that makes it hard to remember what the setup process is and/or was. Our goal is to help make our environment become more stable and also more standardized. - Wayne likes to use a program called Puppet. This allows for a master template and/or recipe to be deployed out to other serves. Similar to ghosting or cloning things. As we install and setup new serves, Wayne could then help and manage those serves. He was talking about server roles, scripts, and applying updates and changes. Setting things up and then maintaining that same type setup over time. - If Wayne starts taking care of the servers, it enables us to spend more time developing. - How do we deploy code to the servers? We are currently using Git (source control and version control). We are using phase one where we push code to the server. We would like to use a step 2 process where Git (our version control) actually pushes the code up to the server. When we get to the automatic level of deploying code to all servers, we need to make sure that we have all dependencies in place. This includes our database updates. Currently, the database updates are scripted and then run by users per server. Wayne is talking about a documented process that writes a chain of processes that have been run and still need to be ran. - We just added a new server - data 11. We are going to be experimenting on that new server and using Git (source control) to push files up to that box. We are also going to be mirroring a new server configuration to help do some side-by-side testing. We are also planning on migrating corporations from data 1 (older server) to the new data 11 server. This is strategic based on trying to migrate clients off of an older server into a newer server environment. - There is another part of this process - that is testing and running tests to make sure that things are working. Eventually, this could get into stress testing and really seeing where the code breaks and/or cracks (pressure and stress testing). Eventually (bad word), we would like the tests to help keep us upright and to verify that we are still good to go. - Small discussion about custom code and getting to a confidence level of what is being done and managing expectations with that custom code. There is some more feedback and communication that is needed here. - We really want this to be a group and a team effort. We are going to need help with ideas, code, migrating, testing, and deploying. - One known dependency piece is the database update stuff. We have to make sure that the database get tweaked (the landing zone) before we push the code up. We are seeing some sort of cross process where we use Git commits and known processes (order of operations) and then match them up with a record on the actual servers. This would allow us to see code on Git/Bitbucket and also compare that with a list on the actual data servers. - Small discussion between Windows and Linux boxes. The discussion was talking about database connection strings and where the actually database live (same server and/or remote connections) and where the server-side software exists. How do they connect. We also briefly talked about security of allowing connections between servers, clients, and databases. We are planning on testing things quite highly before anything goes live. - At what point do you change? It comes down to the burning platform type analogy. - Small discussion on changes to the database and the code... if brand new and no one is using it, easy pea-sy. Once it starts getting used (people are going and moving at full speed) it gets way more tuff and difficult. We are looking for a moving model and getting consistency. - Primary goal - keep our customers happy. Secondary goal - all make some money and be able to keep going with what we are doing? Basically, we need a stable process that our customers like and have confidence in what we do and how we do it. That is awesome. - Wayne jumped in and showed us some of the things that he is watching and monitoring. These are things like: how much memory is being used, how many connections, how many queries per timeframe, CPU usage, hard drive size, and other setting monitors. Wayne was showing us some things from his Nagios server and from his Cacti server stuff. Both are graphing and monitoring systems and what are the trends, traffic, and other server statistics. - As a side note, we are also going to be upgrading to Adobe ColdFusion 2018 and MySQL 8. Some of the older servers are using Adobe ColdFusion 11 and MySQL 5.6 or 5.7. That should help out as well. - We will be making changes as the need arises. We don't want to just make changes just to make changes. - Small questions and answers between the developers and Wayne. Lots of talk about tuning, specializing, and customizing systems, hardware, software, etc. Miss configured settings and getting all of the serves tuned to the right settings. Rollover, fail over, and master/slave type topics. Database partitioning vs corp-specific tables. How do database partitions and indexing effect things? Creating independency between serves and code and serves and databases. Isolation vs shared vs other options. Live data vs old dead data (companies that are no longer using our system). Archiving data, rolling up data and totals, storage, etc. virtual machines vs actual dedicated boxes. Physical locations vs virtual locations of the servers, redundancy, backups, data centers, and even what vendors (hosts) we use. Lots of good discussions. - Wayne and Alan were talking tons and tons about testing and testing strategies. They were also talking about getting things to the level of being able to apply stress based tests and performance tests. Basically, putting things through the paces. They were also talking about concurrent hits (multiple users doing the same thing) and managing tests based on simulated usage and what not. Good stuff. - Picking up the low hanging fruit due to no current performance testing and/or performance configurations. As we get into this, we should be able to pick up a few of the low hanging pieces of fruit. That is exciting. - Starting with the results in mind and then working backwards from that vs writing things and hoping for a certain result. Perception, expectations, vision, and outlook. Some great ideas. Test driven design ideas. - At the end of meeting, Dustin was willing to help with the testing. That may be a perfect fit. Currently, he has some pretty integrated processes that he is working on and nobody is pulling on him for super tight deadlines (client requests). He is working on internal projects. |
||
| Shop 4194 |
|
Adilas Time | 12/24/2018 |
On with Steve and Dustin. We got caught up from happenings over the weekend and both Steve and Dustin had a couple of questions. After that, we then all of us went on mute and started working on our own projects. My first task was buckets full of emails and what not. Setup some sub account stuff for Wayne on the Newtek site to help manage some of our servers, support tickets, and account details. Eric popped in and we setup some blocks of time to work on the sub special account tracking stuff - first couple weeks in January. This is for things like rewards/loyalty points, gift cards, in-store credit, etc. It will be good to get some dedicated time to work on that project. |
||
| Shop 4201 |
|
Adilas Time | 12/26/2018 |
Steve, Dustin, and I were on the meeting. We briefly talked about who is doing what, and who is checking in and on what projects. Light game plan stuff. Wayne popped in part way through and had some questions. I helped him out for a little bit and then Steve did some training on what we normally do inside of adilas and how to monitor the corporation stats and usage from inside of adilas. Wayne is looking to simulate some of the bigger corporations and build some stress tests for the different servers. He is trying to get things performance tuned where possible. After that, we broke into our individual projects. I was working on a new printable invoice that has no special formatting and colors and also prints nicely on a single 8.5 x 11 inch sheet of paper. I'll calling it the black and white (plain jane) printable invoice. |
||
| Shop 4300 |
|
Meeting with Shawn - Year end payroll stuff | 12/31/2018 |
Meeting with Shawn about where we are at with end of year tax updates and changes. He has a number of new state and federal tax changes. His code isn't all the way done quite yet. We will be meeting again tomorrow. In the mean time, I will be running the tax table copier code that we have. We have to run this same report every year. It allows the payroll system to keep working and running. Then, as Shawn has his new changes, we run each smaller section and it strategically updates just certain pieces and parts of the federal and state withholdings tables. Good stuff. After my meeting with Shawn, I started checking emails. It looks like there was a SQL injection hack against one of the servers yesterday. A SQL injection is where a hacker takes existing code and tries to find a weakness in the existing code. It basically has the server run a normal SQL query against the database, but part way through the normal process, it tries to break out of the normal flow and set some values, variables, and/or inject custom code. Wayne Andersen, one of our guys, was able to track it down and put a temporary patch on the code. The hacker was calling a sleep command on one of the servers which was virtually locking the database for a certain period of time. Not that I applaud this, but there are some pretty creative persons out there. I'm glad that we have some top level guys on our side. Anyways, I spent the rest of the morning making a few code changes to push up to all servers to keep things nice and tight. |
||
| Shop 4202 |
|
Adilas Time | 12/31/2018 |
On with Steve for the first part of the morning. We were going over updates and new requests. Lots of moving pieces. Alan popped in and we talked about the delayed inventory counter and updates on some other projects. After that, I helped Steve with an array loop for a custom report. He was converting from a normal query (database feed) loop into a hardcoded or hand-built data array of arrays (multi-dimensional array). After that, Bryan popped in and we helped him fix a small bug dealing with CSS and pulling in certain page variables on a full black box takeover report. Towards the end of the session, Wayne popped in and we talked about server security and how to virtually "harden" our servers and make them not be "soft" targets out in the world of web servers, database servers, and web sites. It's a pretty crazy world out there and there are lots of super villains (virtually speaking) roaming about. We will keep working and go from there. |
||
| Shop 4281 |
|
Adilas Time | 1/7/2019 |
Reviewing things with Steve. We talked a little bit about a new email server for adilas. Currently, we are using an existing shared account setup by Newtek to run all of our emails through. Going forward, we may want a little bit more control and/or get our own email servers vs using the normal Adobe ColdFusion. Wayne is the server guy and might be able to help us out there. Good stuff. Steve was talking to a rep and I was overhearing their conversation - lots of talk about ecommerce and how to get people logged in and tons of other ideas and topics. As part of the conversation, I heard him say - "Adilas is clay - what do you want?" I love it and I've heard it before from others, just not sure if I have recorded it. We have a custom business solution that is configurable. Wayne popped in and we were talking about email server options. He is super smart and has done tons of that. We spent some time talking about security features, queues, etc. Wayne is also doing some automated tests and is helping to harden up the servers. He is hitting some of our servers as if he were an outside hacker. That helps us see where the vulnerabilities are (in some ways). We also talked about options for testing, staging, and production environments on all servers. This deals with different code branches and how to virtually use three different code sets, three different databases, and even three different sites (web addresses) where we could simulate live data and other variables. We have never been able to do that. Basically, we could duplicate live data for testing and staging and then play in a semi-live but non destructive manner. That would be super cool. |
||
| Shop 4276 |
|
Adilas Time | 1/8/2019 |
Steve and Dustin were on the morning meeting. Steve had a quick question about a custom report for owners. We talked about some security hashes that could help the report be more secure. The admin report needs to be outside the secured environment and kinda a quick access link to a quick breakdown report for admin users. Steve has the report built, he is just adding some security and then going to add an access point from inside the secured environment. I got a call from Russell. We talked for quite a bit about some custom client needs and how best to proceed with those requests. We also spent some time talking about using Bridgerland or BTech to help build out some of the fracture type pieces. The term "Fracture" comes from an idea that Steve had back in June of 2017. Everything in adilas seems to be fracturing and breaking into smaller and smaller pieces. Just discussions at this point, but basically a centralized brain (backend engine) and then a deployable front end that could be hosted on any client server or through a commercial web host. No special setup and a fully customizable frontend interface. The whole thing would talk and/or communicate through API socket connections and back and forth API traffic. We talked about ideas, options, etc. If I were to put together a small fracture tick list, it would be something like this: (just ideas) - Customizable look and feel (corp-level, department level, user level, and whatever in between) - Preset defaults with ability to tweak out the defaults and settings (good starting spot and/or basic structure - starting templates) - Permissioned out and/or micro permissioned (down to the functions per section) - Settings for layout, settings for display (show/hide, sort order, aliases, instructions, required yes/no, validation rules, etc.) - As of right now, we are seeing settings on 4 different levels. They are world (corporation or business entity), groups or system player level (customers, invoices, deposits, expense/receipts, PO's, parts/items, vendors, users, stock/units, balance sheet items, quotes, elements of time, etc.), page level settings (what will show/hide, sort order, placement, flow, etc.), and finally, user level settings and defaults. How do I want to play the game (at a personal level)? - Existing structure and flow, but it could be modified. Basically, a template of the starting procedure and/or process but make it able to be modular (build mini data assembly line type options per procedure/task). Think of our model with the mini bubbles and/or pods. These interface with flow, permissions, time, flex, and mapping clear out to the accounting levels. - Real in-line database extensions. This allows us to provide a basic starting point (database tables and template flow) but also allows for things to be expanded and/or contracted (lessened) based off of configuration. These database extensions could be data types and allow for numeric, decimals, text, dates, on/off toggles, and even long text or JSON storage. - Be able to save and build any kinda of report or data export - using existing tools - graphics, charts, graphs, and other summary type options - Support of both transactional data (what happens day to day) as well as aggregated (summed or pre-calculated values) - Digital story telling, using characters, relationships, cause/effect choices, consequences, etc. World building concepts. - Configurable interfaces and functionality per business vertical - click of button to switch layouts and/or processes. - Customizable (data or logic hooks or black box technology) on client side, server side, and display and logic sides. - Responsive and/or mobile ready - Tons of flags, tags, and special callouts - Be able to tie everything to time or elements of time. This could allow for groups, categories, types, sub locations, sub phases, sub status, etc. - The list goes on... Most of the ideas have been recorded somewhere in the adilas developer's notebook pages. A great resource, it just may take some time to review and categorize. ---------------------------------------- Back to other topics, Eric popped in and we made a few more notes and decisions on the sub special account tracking stuff (gift cards, loyalty points, in-store credit, etc.). After that, Wayne jumped on and we talked a little bit about email servers and what is needed there. I spent the rest of the time recording notes and reviewing to do lists. Busy times. |
||
| Shop 4288 |
|
Adilas Time | 1/10/2019 |
Steve, Dustin, Wayne, Eric, and I were on the morning meeting. I gave a small update on my "on site visit" yesterday with the tool company. Tons of new notes and pages of ideas and requests. Wayne wanted to talk about ways of standardizing code, and how things get implemented. He pitched a couple of fun and good ideas. He had us look at an article about ways to use Git (version control software) and have a number of different stages and/or branches. He was also explaining about how he could implement things like this inside of adilas. Super talented and we've never even been able to consider some of these concepts. Very interesting. Here is a link to the article... not exactly this process but some similarities. https://nvie.com/posts/a-successful-git-branching-model/ After Wayne was finished, Eric and I chatted about the sub special accounts homepage and what that would be and/or look like. We made a small plan and then Eric jumped off. Steve and I then started talking about how some of the developers are really wanting to jump in and play the game. We talked about Russell and what he wants to do, Wayne and what he wants to do, Alan and his goals, where Calvin is at, Dustin, Spencer, etc. Right about that time, Eric popped back on the meeting and was asking Steve about some ideas and concepts of revenue sharing and how we could build things out to a more and more stable working and development environment. Eric was talking about how much better adilas as a whole would be if he was able to build out core features and projects vs doing the custom one-off implementations all the time. Some of these developers work and work and work and then their projects are done. Most of them want something that is reoccurring and/or can be reused over and over again. That seems to be a trend. Very interesting, almost the exact or similar topic that we were on. While Eric and Steve were talking, I was listening and making some mental notes. We don't know which way to jump yet, and we don't want to overload the boat so that it tips (get too far extended by debt and/or payables), but there are some awesome opportunities right in front of us. We have a great talent pool that we know, like, and have the skills to do what is needed. We just need to figure out how to keep funding the journey. That is awesome. From Steve - he thinks that we have crossed a new checkpoint. We are having guys with talent that are virtually knocking on our door saying - I want in. Russell's word - "Dependable" on what we called the people on our team. Steve was also talking about some supplemental experiments with salespersons and people helping to push our product out there. We are going to start funding some small sales missions and covering certain individuals for 10-20 hours a month doing sales. If they get a sale, they are able to charge their normal setup and/or consultant rates. If they are prospecting, they will be on a small adilas budget to help them cover prospecting time and maybe some gas money. Basically, a small "low to no" budget sales force, but helping to augment and/or supplement the sales efforts. Fun stuff. Towards the end of the session, I took some time and recorded some notes. To some, it may seem like a waste of time. To me, it is what I do and that's part of the job and/or what I like to do. I gain from it in big ways. Whatever I write, I have to think about it, record it, re-read it, and it improves my memory going through that exercise. Anyways, that's why I write so much. Once it is down on paper (virtual and/or physical) I can refer back to it and it lessens the stress load. There is an old saying, the faintest scratch on paper is better than the sharpest mind. |
||
| Shop 4319 |
|
Meeting with Spencer | 1/10/2019 |
Wayne, Spencer, and I jumped on and we did a quick review of the short and sweet cart interface. We are going to be trying to work through API calls, AJAX, JQuery, and PHP for this project. This is somewhat of an experiment. Wayne and Spencer were talking about wishes and goals as well. Wayne would really like us to use unit testing, different Git (version control) branches, and not rely so much on FTP (file transfer protocol). Good demo and good discussion. |
||
| Shop 4285 |
|
Adilas Time | 1/14/2019 |
Alan, Steve, Dustin and I were on the morning meeting. The first little bit was each person reporting on what they were working on and what issues are still outstanding. Steve had a couple of questions for Alan and Dustin. They are following up on different tasks. I spoke with Alan a little bit about our plans for some changes in how the sub inventory and sub barcodes were going to be searched and filtered. Next, I gave Steve a small update on my meeting with Spencer and Wayne from last week. He asked for some drawings on what was going on. I explained that Spencer was at a turning point where he was going to be needing access to actual data. He doesn't know Adobe ColdFusion very well yet, but he is a PHP master. PHP is another open source server side scripting language. Wayne and I decided that we would let Spencer build out his new prototype in PHP and use the adilas API sockets to get and pass data back and forth. That sort of spun us off into a small discussion on where are we going and how are we planning on integrating all of these pieces. That, of course, is a whole other topic. We touched on the need to build out the adilas API sockets (play at the wall - allow outside data connections) and how that would fit. Calvin jumped on and a couple of the other guys bailed out. Steve and I had a good talk with Calvin. Our current project with Calvin is an outside label builder for custom and bulk labels. Part of our conversation was helping both adilas and Calvin get our communications being built up and on better levels. We chatted, got on the same page, and will hopefully be back on task next week. Calvin still has some other projects that he is working on right now. Good meeting. Steve and I then spent some time talking about how the trend is kind of going toward 3rd party solutions and 3rd party build outs and then trying to inter connect them with internal adilas flow and processes. This took us back to a subject of PHP and other adilas API socket connections. Eric popped in and had a couple of questions. He is building an project for sub special account tracking stuff like loyalty points, gift cards, etc. Some of our discussions today were dealing with page flow and naming conventions. We talked about having a new sub homepage for the special account tracking stuff. We then talked about how the user would have to let us know what special account type they were looking for information on, and then what that process would be like as they walked from step to step, adding filtering, and then finally results with drill-downs. Lots of concept level talks about flow and data. Good stuff and I think that Eric is making some good progress. We'll still need to tweak and refine things, but progress is being made. Lots of emails and other things, just trying to get caught up and going. After that, Steve and I jumped back on the discussion about PHP, adilas API sockets, playing at the wall, internal vs public files, what servers would look like (just Adobe ColdFusion boxes, just PHP boxes, or dual setup of both ColdFusion and PHP per box). We have some questions that we will be asking Wayne about options and direction. We also made some good break trough's by noting which files and servers were private (owned and controlled by adilas) and which files and servers were public (owned by 3rd party and/or outside entities). Just adding what was public and what was private, really helped the conversation and get both Steve and I on the same page. What we are seeing is that we need to keep pushing for a full separation between the data (database, storage, and access to the data), the logic (functions, methods, API sockets, and flow), and the actual display (what things look like, where they focus, and what they do or don't do - visual interfaces). Those three things data, logic, and display are huge. The more we separate them, the more modular our application becomes. We didn't spend a ton of time on this... but all of our discussions were somewhat pointing to the greater and greater need for the adilas market (adilas world) to play a part in the puzzle. Currently, we have a saying "Play at the wall" for the adilas API sockets that we expose to the outside public. That wall is basically the access point between the adilas database and logic and the outside world. We are almost seeing a 2nd wall (virtually speaking) starting to form up. That second wall or outer wall is the adilas marketplace and who has what, who offers what, how is it obtained, or who has made pieces that virtually are able to be plugged in and/or integrate with adilas core functions and functionality? I'm betting that the open market will end up playing a bigger and bigger role as things progress. Our challenge is how to manage that as it grows. Good stuff. |
||
| Shop 4287 |
|
Adilas Time | 1/17/2019 |
We got a report from Alan on the delayed inventory update stuff. You can now save your work, delete/remove some records, reset things, and then finally process the saved pieces. We are really close to getting that launched and online to let people start playing with it. Good stuff. Eric jumped on and had a few questions. After that, Wayne jumped on and we went over some server things. Wayne is in the middle of a task to move about 70ish corporations from an older data 1 server up to a newer data 11 server. He is just doing prep work and practice runs right now, but building up for the actual migration process. He had some questions and a lot of them are dealing with different files on different servers. We know that we need it (custom code options), but it does make some of the standardization process more difficult. Anyways, we chatted about a number of options and even pitched a couple ideas back and forth about using includes, config files, and database storage of either values or objects (JSON stuff). Lots of good talks and discussions. Eric came back on and had some questions on how to deal with optional database joins and displaying conditional output. Where this comes from is we allow the sub special account tracking transactions to be either tied to a customer, an invoice, a payee/user, or just generically tied to text entry (not a real database item). This allows our gift cards, loyalty points, and other sub special account tracking accounts more flexibility. I showed him some pages where we already do similar type logic (media/content and flex grid). In between times, I was working on helping the customer tax category to stick. This is for customers that are say set to a tax category of wholesale, resale, government, etc. They are not taxed, but often a retail item will be setup as normal taxable or with tax included. My current mini project is trying allow the non taxed customers to get the correct auto tax categories as they go through checkout and cart creation process. |
||
| Shop 4282 |
|
Adilas Time | 1/21/2019 |
First topic of the day today was talking about the talent pool that adilas has access to. Steve and I chatted about a number of the different developers, reps, consultants, and sales people who are helping us to play the game. We talked about how best to keep funding those efforts and endeavors. Good stuff, but you do have to be creative. I showed Steve an update on where we are for the customer tax category project that I've been working on. We also briefly talked about a new sales flyer and where we are headed with that venture. Lots of moving pieces. I worked on more code for the invoice side of the customer tax category project. This helps with invoice line items being added after the fact and still being able to maintain the correct tax categories if an item is added later on. Eric popped in a couple of times and has a few small questions. We talked about touching base almost daily until we could get a firm grip on when we could have the sub special account tracking stuff done. This deals with loyalty points, gift cards, etc. Eric also had some questions about doing custom work or internal adilas work. He mentioned, that it would be so cool if we had all of the custom one-off pieces that he has built, inside of the main adilas platform. That would be super cool. In the meantime, we are gaining ideas and knowledge of what is wanted and what is needed. Sometimes we have to play the custom one-off game until we either know enough about the needs and wants of our clients or we get the correct amount of internal funding to build it as a core piece. Wayne popped on and we chatted with him about moving and migrating a couple of companies from servers to other servers. Basically, a company that has a dedicated box, just acquired a couple more companies that are on another server. They want everything under just one roof on the same server. As we were talking, Wayne had a couple questions and ideas. He brought up the fact that if we wanted to, we could split all of these databases into smaller single corp instances and run them on their own databases vs deploying things in a shared or semi-shared environment. We talked about pros and cons and I shared a little bit of history with Wayne on what we have been calling the world building project. We have wanted to do this (getting people off the bus - splitting up the database) for years and years. Looking forward, I'll bet that Wayne will end up helping us out there. Good stuff. Spent the rest of the time coding on the customer tax category project, emails, paying bills, and trying to get some verbage together for a new news and update on the customer tax category changes. |
||
| Shop 4283 |
|
Adilas Time | 1/22/2019 |
Steve and Dustin were talking about new processes and using some new and fancy display options. After that, I helped Steve with some JavaScript calculations and some small page changes. Wayne popped in and he gave a report about some of the server issues that happened yesterday. It sounds like a company was trying to pull multiple queries that had 2 million records per query. Basically, a log jam in the database. As we were talking about things, we were talking about moving from a purely transactional database, to a more aggregate type environment (aggregate meaning sums and totals vs individual transactions). Tons of data is awesome, but we need to limit the transactions and how many we are trying to chew up per bite. Some of the reports need to be re-written to be more efficient. Nobody wants to read and look at 2 million lines... all they really want is the totals, the counts, and the sums from that data. We may need to filter the data and better display it in a drill-down type basis. Wayne was talking about DAO's (database access objects) and getting the queries in a more standard location and where to access those assets. We are making progress and making things more stable. Sometimes when our users see an error, they instantly go back to what things were (older past errors) and then they fear the worst. That is just human nature. These are some of the growing pains. As a funny side note... Wayne was saying, other companies that seem light and fancy, they will have the same issues as they grow, their day will come when they are up against the wall and have to move from transactional data to a more aggregate type model. Wayne was also talking about dynamic services vs just static boxes (dedicated servers). Basically a way to throttle resources vs setting up a static environment with specific resources. We were also talking about roll over protection and other mirror type values. We lightly were talking about how we may be out growing our current hosting company. We may start looking into AWS (amazon web services), Google, and/or other bigger players. Currently we are using Newtek and they have been awesome for years and years. There was also some talks and discussion about a new pricing model based on usage, storage, bandwidth, requests, etc. We would love to get there but it still seems to be out there a bit. We were also talking about stats and then also projecting those stats out to our users. Some of this may require us to setup things per instance or per client. Random side note, I wonder if we were to go back to the drawing board and start with the end goal in mind. Would that change things? How, why, and how deep? Do we want that? Maybe help our clients run based on sizes and needs. We grew from a small shared environment into a semi dedicated model and then into a fully dedicated model. We now have multiple dedicated servers. Wayne was saying something about Docker (spelling) containers and how to group things and somewhat create a virtual playground or virtual cluster per corporation or per company. Once we get them into the container of sorts, we could then expand that contain as needed. SaaS (software as a service) and how to expand and grow things. Funny quote from Steve - "We need to get Wayne on a faster horse." Meaning, we may need to help Wayne get on an environment where he is not so limited (existing dedicated servers, structure, and physical boxes). Maybe we need to move more to the virtual playground. Steve had some ideas about using more of the invoice homepage type mentality. Basically, we had an older report that pulled in the last 30 days worth of transactions. We totally changed that page to pull quick counts, graphs, charts, and sums. We then only show the last 15 records (really easy on the system). They users can flip/flop between daily, weekly, monthly, quarterly, yearly reports at the click of a button. All of the values are queried and pulled using a technology called AJAX (go get just the data and return without refreshing the whole page). Then, if they want more details (actual transactions), we have a number of other reports where they can filter the data to smaller and smaller levels. Steve would like us to do more and more of that to help eliminate the full detailed transaction searches. Great idea. Towards the end of the session, I spent some time and built in a pre-check query for the advanced invoice line items search. If it has more than 100,000 records trying to return, it shows an error and requires the user to filter the details down a little bit. Apparently, this was the query that brought down data 8 yesterday for a bit. The company that was running the query tool was searching for over 2 million records in a single report. They were running back to back queries of the same size. That big of a bite created a data log jam in the database (table locking for joins then processing and doing calculations on 2 million plus records per query). That eventually caused us to reset the whole server. As a side note, that same query tool joins about 5 tables in order to get the results. If you do that for a couple thousand records, no problem... if you do it for millions and millions, at a time, it is a problem. |
||
| Shop 4279 |
|
Adilas Time | 1/24/2019 |
Wayne and Steve were talking shop about ways to configure clusters and groups of servers. Lots of talks about AWS (amazon web services) and how they monitor and provide tons of sales stats. Talks about monitoring API socket calls, queries, requests, emails being sent and received, storage, bandwidth, etc. They were talking about using the stats as the base level and then we would just do a mark-up on top of that value. There may be some thresholds and bench mark values, but we could really change our pricing model. Steve would love to almost give the software away for free and then we just charge for processing and storage. They were also talking about letting the billing cycles run automatically based off of the stats plus mark-up. They then switched to a small demo of the Docker containers and Docker servers (ways of managing a number of like instances and virtual machines). Lots of ways of deploying and configuring mass numbers of servers and also keeping things synced up and ready to go. Lots of talk about breaking every corp into their own database instance and spinning things up on multiple different servers (clusters of servers). Tons of fun world building stuff. We may end up needing to store and make accessible certain data and values between different servers and still allow bouncing between different corps and even different servers. Fun new levels of what is possible. Once we start breaking things up, it may allow us break up other thing (pieces and functions) within the adilas environment. We honestly don't even know what is possible and what may end up shaking out of this restructure. Pretty crazy. Eric and I spent some time working more on the sub special accounts and special account tracking stuff. We setup some time for next week to get in there and really start polishing things up and doing some finish work. There are quite a few pages and backend methods (functions) that have been built. The next stage is going over things with a fine tooth comb and helping the mock-ups and alpha releases become more stable. Good stuff. When I wasn't on the meeting, I was building the customer purchase history page to help show the last known prices per item per customer. This will really help out those who do either contract pricing and/or have a variable pricing model. Spent some time working with Steve to try to roll some of his JavaScript calculations back and forth. We could get them to go one direction (populate and calculate) pretty easy, but we were struggling with rewinding things and making it recalculate. Just normal stuff. Later on, Eric popped back in and had some questions about flip flopping between FORM and URL scope variables. I showed him a number of examples, where we do the same thing on other pages. He caught on really quickly. |
||
| Shop 4275 |
|
Adilas Time | 1/28/2019 |
On the morning meeting with Steve, Alan, Wayne, and Dustin. Checking up and getting caught up with what happened over the weekend. Notes from Wayne about server stability and processes Infrastructure - We have greatly increased this portion. We would like to fix how we deploy code to the servers. Currently we are just using FTP and are able to push code as needed to different servers. Code - The last couple server issues have been code related (bugs, poorly written code and queries, or loose code). These code problems are currently affecting our servers as much or more than the infrastructure process. See attached for a small proposal from Wayne about how to configure our environment. Wayne would like to look into Lucee vs ColdFusion. I put tons of notes on that physical PDF upload. We talked about some costs and also options going forward. We talked about DNS (domain name servers - where are things pointed), SSL's (secure socket layers - https stuff), emails and texts, etc. We can virtually push some of the logging into the AWS CloudWatch services. Amazon also has some other servers that we could harness and/or use. Some of the other services are AWS Cost Explorer, AWS Budgets, AWS Cost and Usage Report, and Amazon Route 53. Steve was asking questions about how we could make an adilas user group (power users - adilas community) that could be linked and/or joined to different companies or different adilas clients. Almost an extension of the adilas reps and consultants - who wants my skills, I have a power user account, and that could be tied in to anyone's account (based on permission and access). All secure, but also very mobile. Basically a way to separate users and clients. We also talked about splitting up the databases (world building) into corp-specific databases (smaller single databases) and then working on the mixed or cross-corp queries. In the background it could be tons of different services and even computers, but in the frontend, the presentation seems singular and very streamlined and smooth. This also opens up more revenue options for our developers to help code cross corp or consolidated reports and such. Some talks about future white labeling options and how we could setup adilas as a platform and then allow them to pay the AWS bills and they pay us for usage of the code. The rest of the talks circled back around to the code and how we create and deploy our code. Lots of talks about automated testing and getting all of that stuff super stable. Being able to up-scale to handle bigger and bigger loads. Alan popped in and also brought in the possible option of down scaling as well. No one likes to talk about this, but we need to think about both side of the coin. If we are on a dynamic environment, we could virtually scale up and/or down. Once again, it comes back to a two-part puzzle... you have both code and infrastructure. Alan was talking about how to encourage our developers to run more of a test driven code structure. This will be a cultural switch. If we make it so that the system becomes the bad guy, we could help to change that culture. We've done this before, when we first introduced permissions and such. We talked about training, tooling, and guidelines to help some of these developers. Most of the talks today have dealt with changes to infrastructure - we also know that there is possibly a bigger conversation about the code development side of things. Where are we going and/or heading? Eventually, some of the adilas functions and features will become components and virtual standalone pieces (modules of sorts). We need the flexibility of a Legos type scenario... multi interlocking blocks that could be mixed and blended as needed. From Steve - I'm seeing lots of our wish list boxes being checked with these new proposed changes. From Alan - This seems great for scaling. Hardware is one of the hardest ways to scale. If we could turn it into a service, it becomes easier to manage. Alan was also talking about scaling up and scaling down. Make sure you can go in both directions. How much weight are forced to carry... being able to absorb or extend as needed. We can make the whole presentation more seamless. Currently, we send clients to data 10, data 11, etc. If we go more in this direction, it just runs more seamless and we scale things in the background as needed. In the background, we almost need a platform babysitter that helps us know what is going on and/or what is available. Our clients tend to like - our pricing, our possible functionality options, and how easily we can customize things. Dealing with timelines... We are seeing this transition between 6 months to a year. Maybe even more. We will start on it immediately, but it still may take some time to roll these things out. Also, we can only see so deep, there may be some unknowns that hit us as we get into things. Alan was saying some of the fun development sayings such as the last 10% takes 90% of the time and other things like that. It always gets crazy. Slow and steady wins the race. Lots of good things on the horizon. |
||
| Shop 4341 |
|
Working with Wayne | 1/28/2019 |
Working with Wayne over a GoToMeeting session to setup some new accounts at Amazon Web Services (AWS). |
||
| Shop 4277 |
|
Adilas Time | 1/30/2019 |
Meeting with Steve and Dustin to start off the morning. Dustin had a couple of questions on ways to track some of his internal code changes. We talked strategy for a bit. Steve then had a question on a client's custom label. It was duplicating one of the fields. We dug in and found that it was a sub inventory attribute that was virtually sharing an id number with another sub inventory attribute. It was appearing to duplicate the data due to the numbering of the attributes. Random error. We went in the backend and fixed it. We haven't had any other complaints about that, so we are assuming that somehow both attributes got assigned the same reporting number. As Steve and I were fixing the sub inventory issue, we were talking about sales, customer support, and how we are hoping that these new server configurations are going to help us out. We also talked about getting someone to help Shari O. - she is getting buried and needs someone to help. We also talked about some other ideas to think about while we are breaking up the bus (analogy of getting people off the bus and onto their own motorcycles or cars - aka world building). Here are some of the quick notes: - What about mini options for AWS servers... Currently we have multiple dedicated servers (with fixed number of processors, RAM memory, and fixed hard drives for storage). What if we took those bigger boxes and virtually broke out a new virtual instance for each of our clients. If it could work, it would be almost like a mini virtual dedicated box per client. Just an idea. - Steve would really like to split out users from corporations (allows users to exist as their own entity and also as part of a master list). Then, we could bridge people over and across and allow users to jump between corporations as they get assigned. We currently can do this, within a single box or cluster. It would be awesome if we could do this on a universe or global scale. Any user (has a single account) and could be interconnected and/or have access to any other corporation (world) based on permissions and being bridged over. Think of home planets and bridging people from worlds to worlds. (digital passports and what not) - Currently, we (adilas admin) are the only ones who can bridge users between corporations. If it went out further... we could allow individual parties to allow/invite other users to come in and help with any projects and also set connection durations (how long they could virtually stay). If we empower the users to create those relationships, that takes the load and the liability off of the admin adilas team. Good stuff. - Steve really wants to help out workers and/or dependables - We would really like add some visual upgrades - CSS and settings. As a side note, settings are going to be huge going forward. We are seeing at least four levels of settings - corp (world), group (system players), pages, and user settings. - Steve and I were looking at some stats that Wayne had gathered for us... crazy to see those stats and this is just one month from the data 0 box. We would love to see all of the servers and all of the stats, side-by-side, and compare. That would be crazy. - The deeper we get, the more settings and being able to toggle things on/off (custom setup options) are going to play in. We were even talking about new settings for ecommerce and companies that allow for new customer/client accounts to be setup. What fields do they want to show/hide, what ones are required, what special instructions, what names or aliases, what sort order, etc. Everybody wants crazy deep levels of control on how they set things up. - Steve and I talked about the pros and cons of the black box options... on the one hand, we can configure any page to do whatever we want. On the other hand, if we go black box vs building a new setting, we have to do the same thing over and over again. Sometimes the speed of the black box option actually creates more work later on. The longer route is building a setting, but it then becomes easier to manage that later on, plus less duplicating code. |
||
| Shop 4368 |
|
General | 2/5/2019 |
We got a report that there was a problem with selling out stock/units from the data 0 box. I went in and looked around. I re-uploaded the page that was throwing the error. I tried it and it still didn't work. I did a remote login on the server and found that a single table was fully locked and set to read only. I pulled a known value and then tried to change it. The error came back as the table was set to read only. I called Alan and sent a text to Wayne. Alan called me back and said that I would have to reset the MySQL database services (quick turn on/off of just the database). I did that and it seemed to fix the problem. Just wanted to record that for future use, if needed. |
||
| Shop 4365 |
|
Adilas Time | 2/11/2019 |
I got into the meeting a little bit late. Steve and Dustin were working on some things. Once they were done, Wayne began reporting on some of the new AWS (amazon web services) things. We were talking about moving some of our existing pieces (server stuff) over and across to AWS and then tweaking things from there. Lots of options to help optimize things. There are so many things on the virtual to do list... we'll just get started and then go from there. We are also excited to start seeing real costs and real usage patterns. This is both internal and external. Wayne and I spent a couple of hours going over tons of things... data servers, content servers, images, corp-specific folders and storage, session stuff, security hashes, Windows specific code, and tons of other things. Super good meeting. Steve, Josh, and I ended up having a discussion about the new discount engine (new code that is being released) and wanting our clients to move from Classic to the Snow Owl theme. We have so much more functionality on the newer Snow Owl theme. Some people are too busy to switch, some are just unsure, some think there are issues, etc. We would really like to use the discount engine to help us transition those users over to the newer look and better settings. It takes a village to do some of these tasks and things. Delegate, empower and get out the way. We keep building and tearing things down. That is part of the process. We have some great people all around us. Let's keep feeding those fires. Yee haw! |
||
| Shop 4407 |
|
Adilas Time | 2/18/2019 |
Wayne jumped on and showed Steve and I his first instance of adilas running on an AWS (amazon web services) setup. We had a few small glitches, but great progress. Wayne showed us around and how he could virtually set timers, watchers, and virtually dial in needs based on usage and/or preset timers or requirements. Huge paradigm shift in our thinking. Both Steve and I spent some time bouncing through pages and doing light testing. I made a small document with a few of the light tweaks that may be needed. Eric joined the meeting and had some questions for all of us. He got a new database from Wayne, had some 3rd party solution questions for Steve, and Eric and I talked about our plans for the next couple of days. After the main meeting, Steve and I chatted briefly about new options and where things seem to be headed. Lots of new options are starting to pop up. Exciting, but it will take some management to really make them fly. Good stuff. |
||
| Shop 4415 |
|
Working with Eric | 2/19/2019 |
Eric and I were working through some database settings and changes. Eric has a brand new database from Wayne and we are lightly refining it and helping it to be more stable and ready for use. Steve had me do a code merge and we got some new files pushed to all servers. As a side note, he has already done over 30 code branches on his own. Most of those branches had 20+ files per branch. Good stuff. |
||
| Shop 4410 |
|
Adilas Time | 2/20/2019 |
Hopped on the morning meeting with Dustin. Just the two of us were on there for the first part. Dustin had some questions about some of the reports coming off of the cultivation homepage that he and Steve were working on. We ended up talking about having a plan and really knowing where the different pieces either are and/or should be. Knowing is half the battle (old G.I. Joe quote). If you know what should happen, then you could go back and actually check that. If you don't fully know, how are you supposed to check and/or verify what is happening. You've got to know and/or have a map of sorts. Wayne came on and gave a small report. He is making good progress on the AWS stuff and reported on some custom tags and ideas on doing unit testing using a special framework and program. Most of our testing will be in ColdFusion but some of it may end up being in Java or some bigger or more robust language. |
||
| Shop 4413 |
|
Adilas Time | 2/26/2019 |
Wayne and Steve were having some good discussions on the new AWS (amazon web services) stuff. Lots of talk about bringing new corporations on and getting them all setup out in the AWS landscape. They were even talking about rewriting our API to match the AWS environment in a better manner. Calvin was giving us a demo of his Adilas Label Builder app. He showed us a full build from the ground up. We built a PO label and then did a number of live tests. We had Wayne, Steve, and myself on the demo. Calvin is doing a great job. I will be meeting with him later on today to finish up some pieces. Briefly working with Eric on some local JavaScript validation and questions. He is getting further along on his sub special account tracking project (loyalty points, gift cards, etc.). Working with Wayne on media/content stuff. He is going through and testing all kinds of stuff on the new AWS environment. Currently, we have provided him a list of some known bugs and he is working through them. That is awesome. Spent some more time working on the adilas tick list (giant to do list). Still just trying to get all of the smaller projects listed out and on one spreadsheet. That's a pretty big project in and of itself. |
||
| Adi 1453 |
|
AWS - Amazon Web Services - changing over to the new server model | 2/26/2019 |
Wayne has been heading this project, along with Eric. |
||
| Shop 4444 |
|
Adilas Time | 3/4/2019 |
Talking with Steve and Dustin about options on black box... - They were talking about using settings saying use custom, use core, use x, y, or z... we may have to wrap pure black box code with dynamic populating options (which option to use). - We could really use a way to help show if the corps have black box options. Maybe even a flag (under the covers or in the hidden HTML) that says whether or not it using black box and/or core functionality. - It may also be helpful if we could allow users to pick and choose if they want the black box option (full custom), the core adilas option (non custom defaults), or an industry specific option (build these options specific per industry). Wayne popped in and was reporting on some AWS stuff. - As we start moving over to AWS, a lot of the switching between test and live (URL stuff), is kinda going away and things are becoming more dynamic. Mostly dealing with URL, web addresses, domains, and path stuff. - We talked about files and media/content storage and what to make publically available and what not to. We also talked about settings and adding in public and/or private boxes per corps (places to store things). We also talked about allowing users to put timelines (expiration dates) on sharing files and such. Say something like, I'll share this file with you for two days or I'll share this file for a couple of hours, etc. Once the expiration date of the URL or file happened, they would be denied unless they opened it back up. Kinda like opening and closing windows and doors for specific time periods. - Wayne was talking about non language specific functions that we could run at any time. He was calling them Lambda functions. Very similar to an API socket connection or API call. Basically allowing the code and the response to be run using different code languages (mixing and blending coding languages). - Wayne was also talking about off loading certain API socket calls and groups of calls to certain sub processes. Splitting up the flow and traffic based on needs and like functionality. Basically specializing code to be more effective and grouped. - File versioning and auto file versioning - comes automatic with certain boxes out on AWS. - Designing a life cycle process of sorts (putting things deeper and deeper into storage). Maybe use the access time (when was it last asked for or used) as the key indicator. This could be done if we need to mange active vs passive storage. We talked briefly about the analogy of water turning into snow and then going clear to ice. This may also come in to play with compliance, storage, active/inactive accounts, and long term cold storage. - We spent quite a bit of time going over how the transition between our existing model and where things are headed and how to help with that transition. It got us into some discussions about master corporation lists, master user lists, and what permissions where set per section. Steve joined in and gave us some good ideas while we were talking about breaking out user/payee/employees off into their own entity. - We ended with some conversations about world building, universe level, cluster and galaxy levels, world levels, etc. Fun conversation and lots of upcoming options. |
||
| Shop 4440 |
|
General | 3/4/2019 |
I was going to be working with Eric but got hung up on a call with Steve and Wayne going over server stuff. Recording notes, emails, and basic to do list stuff. |
||
| Shop 4447 |
|
Adilas Time | 3/5/2019 |
When I first got on, Steve and Alan were going over some Metrc (state compliance) API socket questions and what not. They talked for quite a bit until Alan had to take his kids somewhere. Later on, we were talking with Steve and Wayne about the login process and procedure. Steve would love to keep going with the data portal type analogy where a person comes to adilas and then logs in. At some point, they are able to enter the virtual data portal or data sphere. As part of that conversation, Steve would love to open up the entry point and almost make it their own (the user's) virtual landing spot (my own room or my space). What do you want to do? Where do you want to go? What does it look like? What is available to you? etc. Wayne was talking about going to a more simple login for the entry point. Maybe just an email and password type authentication process. Even using a single login access type level (Google, Facebook, Amazon, Yahoo, etc.). As a future to do project, it sure would be cool if we could allow users to come into the virtual data portal or data sphere and let them set things up as a frontend entry point. Imagine a virtual lounge with some tables and chairs, pictures, etc. Get the people into a nice comfort level and then let them go from there. It would be cool if they could pull in quick numbers, graphs, charts, etc. - basically their own dashboard. Eventually, even their own features, functions, and options. Steve was also talking about, in the future, allowing users to be more open and actually set themselves up as assets (teachers, trainers, consultants, or even workers). Allow them to use their own virtual home base entry point to be able to help others who need their help. After that, Wayne and I got into some talks about how the adilas API sockets are setup. We talked about the different highways (virtual roads within the API socket connections) and what authentication was done for each of the different paths. We went in and did some drawings and even looked and code and database records. I showed some page samples (existing pages and flow) to give him the full idea of what goes where and how things play. |
||
| Shop 4445 |
|
Adilas Time | 3/6/2019 |
Alan and I touched base on some of the work that he is doing with reoccurring invoices and automating that process. He is working with USAePay (merchant gateway) and automating both the reoccurring invoices (when and how do they happen) and automating the reoccurring payment part of that puzzle. Currently, the there are two side, the USAePay side and the adilas side. The current project is automating things so that both side know what the other is doing and the reoccurring credit card payments get attributed to the correct reoccurring invoice on the adilas side. Currently, a human has to make some of those connections and finish some of those transactions. After Alan and I were done with that, Wayne joined us and we had a good discussion about the new Lucee/AWS stuff (new build out). We spent quite a bit of time talking about OAuth stuff (special multi-level authorization processes), single sign-on, and other user level security things. Wayne had a couple of questions and both Alan and I were helping with ideas and direction. That project is deep, but Wayne seems to be fully going in the right direction. Pushed up some code that allows the advanced parts/items search page use URL (web address) variables. We have a client that has requested URL access to a couple report pages, so far. As a side note, if you expose the variables to the URL scope, you can virtually manipulate the search form without actually pointing and clicking on certain search criteria. They are basically creating their own links (virtual favorites) and then running their own pages to control inside adilas pages. That is pretty advanced, but as long as you have an active login, you could do it, no problem. Kinda interesting. |
||
| Shop 4446 |
|
Adilas Time | 3/7/2019 |
Steve and Alan were talking about frontend automation on the credit card side of things. We are looking into API sockets for USAePay (our credit card gateway that we are using) and being able to pull reports that show customer credit cards that have expired, will expire, or expire during a set date range. It would be super cool to get this information in order to help our billing department. - Steve is really excited to see what the AWS (all of the stats and such) side of things will bring to the table. We really want switch our billing based on storage, throughput, bandwidth, requests, etc. That would be awesome. - Two parts, the gateway side and the adilas side of things... we need the header and app side of the communication process (extension of the invoice due date project). The goal there is to use adilas and be able to communicate back to the users (different companies) and let them know if their invoices are getting to a certain age. Based on settings, the goal is to warn and help get a payment and if needed, to shut off and prompt for payment before usage resumes. There are more details, but that is the general idea. ------ Got on a Zoom session with Calvin. He was having a problem with an existing API socket. As he was looking deeper, we recently made a number of changes to that page back in January. It is dealing with sub inventory, searches, and calculating sub inventory quantities. I scheduled an hour, later today, to look into his question. ------ About 11 am, Steve, Bryan, and I got on a meeting to look at Bryan's adilas community projects page. This is an area where adilas users and consultants can submit and vote for what projects they want us to work on. Basically a way to get outside input on priorities and what is needed and wanted. Steve sees some of this as each user having their own little individual user account (almost outside of adilas). They then could do whatever they need to outside of any specific corporation, just as a user. When they want to go in and do some work, they would need to enter a corporation and/or world. Basically creating a separation between users and worlds (adilas accounts). Some of our conversations turned to possible misuse, abuse, rants, and managing potential problems. In a way, it is almost like opening up a virtual forum and public facing entry point. We also talked about design and styling out the page to make things look more modern. It is crazy how deep, sometimes just a single decision goes to crazy deep levels, and it is hard to see what is going to happen. Lots of cause and effect decisions. Steve was talking about how the look and feel almost helps guide the process. How well does it show? Do people want to spend time doing something that looks old? If it looks modern and smooth, would they use it more? What do people accept? What do people want? After the discussion about look and feel, Steve ended up back on the master user accounts topic and being able to use a single sign-in type interface. This deals with users being able to independently use certain functionality outside of an assigned corporation. We also talked about being able to submit projects and notes and having some sort of sign-off and/or approval type process. We also talked about timelines and being able to show other projects, ideas, completion rates, what project are on target and/or in progress, and other ways of communicating as to what is going on. Long story made short, we love the ideas and concepts, but it still needs some loving and direction. Eventually, we want to open this adilas community forum and community projects to all users and consultants. ------- Talking with Wayne about the new open/general login process. He was talking about an open id (somewhat of a master user id - a hashed username string). We were talking about questions about what happens if a user gets setup but hasn't been associated to a specific world and/or a corporation? How do we allow those assignments to be made, requested, and eventually approved. Wayne was talking about an authorization queue and a way to approve and allow access to certain users. ------ Worked with Dustin on adding new entries in the sub GPS/RFID tag table. This is a sub of elements of time. He is tying things into his cultivation and production pages. |
||
| Shop 4465 |
|
Prepping files for Wayne | 3/8/2019 |
Did some prep work for Wayne. He is working on creating a new open user login using AWS vs internal adilas login stuff. He needed a couple of pages built to help approve and accept open users being bridged between corporations. The pages allow for accepting a request or denying an access request. I built him three small pages that had an outline of the code that will end up being real. This was more of a prep work project than actual code. Sent the files to Wayne. |
||
| Shop 4466 |
|
Adilas Time | 3/11/2019 |
Joined up with Steve on the Monday morning meeting. He was showing me some new pages that he was working on and using some prebuilt CSS templates that we purchased. Russell Moore got us started with those CSS templates a few years back. Steve has been in there playing around and is grabbing code and pages and plugging in real code and database values. It is starting to look pretty good. As a side note, a couple times today, we have circled back around to prebuilt templates and what they offer. Steve and Dustin were talking about some of their combined efforts and different demos that Dustin has been giving and doing. He has done a great job and is very easy to work with. That is a huge plus. Calvin joined in and had a few questions. He also helped both Steve and I get the latest versions of his adilas label builder wizard. We worked with the label editors and then also gave Calvin a few change order to do list stuff. We would love to get some data formatting functions to help make the data look good. The other major topic was talking about 3rd party solutions and how we secure those pieces. I told Calvin that I would work with him on what is needed and how best to get the desired outcome. We are planning on adding a section for Calvin and MyEasySoftware in the adilas 3rd party solutions section. One little nugget from todays talks and discussions was: We may be better off getting one or two key persons trained up on certain features and implementations and then allowing those parties to charge or get paid to help setup the others who need those pieces. It helps get specialists and also really cuts down on the tech support required to do harder or more complicated tasks and processes. The summary is: Get people to pay for value added services, especially somewhat technical or complicated setup or in-depth processes vs trying to teach everybody how to do it on their own. The other option to that, which would be nice if possible, is to make the setup and/or processes more simple and intuitive. Somehow we need to monetize some of these deeper tools. Either charge for setup and training or increase the monthly reoccurring. Wayne joined the meeting and had a few questions. He and Calvin chatted about AWS, windows services, and how they may be able to use AWS Lambda functions to do similar things that we are doing under the current Windows server model. It got pretty techy. We setup a new permission for Wayne to use in his open id user pools and how to grant or deny access between open id users and different worlds or corporations. Steve and I did some more work on templates and getting a good starting place to work from. Steve was talking about how awesome it is to use prebuilt CSS templates due to the fact that you start from a working picture (static or fake data) and then build in functionality from there. We did a code merge for Steve and I had to help out with some page view icons for some of the new pages. Towards the very end of the call/session, Wayne popped back in and had some questions about changing the MySQL data engine from MyISAM to INNODB type tables. Techy database stuff. He also had a question about the scan and add to cart process and how complicated it seemed to be. We talked briefly about some performance tuning and options. Basically ways to help go in and split things apart and/or speed up certain queries. Afterwards Steve and I chatted and talked about some of the cool things that are coming down the pipeline. Keep moving forward. |
||
| Shop 4468 |
|
Adilas Time | 3/12/2019 |
Steve and I were on the GoToMeeting session for about 2 hours this morning, just the two of us. We were both working on other small projects and just talking back and forth. Lots of good things are going on. It has been quite the journey. Some of our subjects were things like: progress, small micro tweaks, continual growth and tweaking, building for the future, countless blessings, laying down stepping stones, building on foundations, willingness to learn, skill levels, being inspired by one another and what we are doing, our guys and gals (developers, sales, tech support, reps, consultants, etc.), and how many untapped avenues there are in front of us. Tons of potential. As a side note, sometime it really helps to have someone else along with you on the journey. When one gets tired, bored, or burned out, the other may be able to help, encourage, inspire, and/or lift. It really helps to have a friend and just keep going. Sometimes that continual pushing is better than one short burst of energy. Wayne came on and had a few questions. He also reported on a few of the things that he is working on. After he left, Steve and I kept talking about some of the talent and team members that we have, that are going along with us on this epic journey. Those other people are carrying the load and helping out. That is awesome and we are very grateful. We are hoping that they are having fun and being supported as well. It takes a team to do these things. After chatting and working on small projects, Steve and I decided to look into a report that some of the sub inventory searches were struggling when finding certain sub inventory values. These problems were only reported in certain cases. We did some local and live testing and couldn't make it fail. We came up with some possible issues or scenarios and then tried to fix what we could. We may need to go deeper, but we got a few things tightened up. We removed some spaces in the code and in the display for sub inventory items. We did some data trimming to help make sure we were getting what we were expecting. We pushed up the code and did some testing. Just a little after 11 am, I got a hold of Shawn and he jumped on with us. He is working on some payroll numbers and withholdings. Shawn and Steve were talking briefly about gardening and greenhouses. Both are somewhat hobby gardeners. |
||
| Shop 4467 |
|
Adilas Time | 3/14/2019 |
Steve and I were looking into a barcode scanning question from a client. We went in and logged in and looked around and didn't see anything out of the ordinary. We changed the item names and looked in the backend database to see if we could see anything. It seem like all is well. After that, Steve and Dustin started working on some of their production (mini manufacturing) processes. Eric joined and had some questions about adilas API socket settings and being able to turn certain things on/off through the 3rd party solutions. We also setup some time to work on code review for his sub special accounts stuff (loyalty points, gift cards, etc.). Tech support and helping Drea out. Wayne jumped on and helped with the backend tech support stuff. Basically, a company was missing a couple of records. We looked and the database had no record of them. Even the auto id numbers totally skipped them. From our point of view, the system should have given them an error message saying that a certain actions were not possible. Anyways, we did some research and got Drea as much information as we could. She will have the client call back two of their customers to see if they could get some data from them. There is no record in the actual database. Wayne and I then did a little session where he wanted me to look up some small bugs that are showing up in his server error logs. I recorded one of them and we looked at a couple of other ones. Small little issues. |
||
| Shop 4475 |
|
Adilas Time | 3/18/2019 |
Steve, Alan, and Dustin were on the morning meeting with us. Steve had some questions about a custom gram control that he was working on. Alan was reviewing with us his work with USAePay and helping to automate the invoice payments and reoccurring invoice stuff. The conversation trended towards the use of the external alternate id number and how those fields get used. We are already seeing a need for a one-to-many relationship between normal id's and the use of the external alternate id number (id numbers from outside parties and/or outside systems). Very interesting. We ended up talking about custom needs, settings, and how to help direct people in other areas. We spent a little bit of time talking about building generic tools and generic database tables vs industry specific and vendor specific tools and database tables. There are pros and cons between both. Generic helps cover the basis but sometimes takes a little bit longer to implement and design and develop. Specific code could be very fast, but you then need to somewhat duplicate pieces as things grow and expand (different parties wanting the same things). We also got into some talks about frontend development and backend development. Look and feel, user interfaces, flow, animations, and design vs functions, code, logic, database stuff, and backend tools. So many people judge our entire application based on their first impressions (what they see). There has to be a good balance between good tools and good looks. Working with Dustin on some JavaScript and advanced options. We spent over an hour looking around and trying to figure out how to cross tie some application pieces together. It got pretty deep with some of inspinia and bootstrap code (special CSS templates, JavaScript, JQuery, and HTML output pieces). Wayne popped in and gave us an update on where he is at on the AWS stuff. Lots of new moving pieces. Our goal there is to get the existing code working out in AWS land before adding all kinds of new code to the mix. After Wayne left, Steve and I were talking about some of the changes in the wind (virtual direction and force of the upcoming changes). Pretty interesting. We may need to get some other players involved and then figure out where they are going to fit in and who wants to do what. Lots of options. |
||
| Shop 4478 |
|
Adilas Time | 3/19/2019 |
I came in late, but Alan and Steve were looking into some Metrc API sockets and matching up things between systems. After that, Alan and Dustin got into some of the Inspinia datatables and how to interact with some of those new things. Alan was able to help Dustin out and point him in a good direction. Steve and I then looked into a balance sheet item called inventory in transit (asset). This is part of the math and code for the balance sheet. Eric popped in and had a few questions to help with his sub special account project (loyalty points, gift cards, etc.). Wayne was talking about some other options that are available through AWS. Top level firewall rules, XSS (cross site scripting) validation, queues, topics, reminders (SMS), etc. Wayne predicts that our ColdFusion pages will become smaller and more efficient as we offload some of the other code functionality to other tools and/or other applications. So many options. We also talked about new possible options for using and doing custom black box pages as well as custom themes (global or industry specific). We were talking about all custom code and file storage (photos, scans, images, files, media, content) per corp and being able to charge for that. That really takes it down to the corp level and charging for storage and usage. Emails, paying bills, and light tech support. |
||
| Shop 4473 |
|
Working with Shannon | 3/19/2019 |
Shannon and I met and talked about progress. I shared with her that we have 4-5 big projects that are coming into play in the next little while that all have a balance sheet flavor of sorts. We went over those pieces and how they play in. Some of the projects are: expand the transitional invoices and adding in inventory in transit (shown as an asset), new transitional PO project that Will is working on (in code sign-off but stills needs a little work), sales tax expansion project (on phase 5 of 5 and just need to finish some things up), Eric's sub special account tracking project (sub of the balance sheet for things like loyalty points, gift cards, in-store credit, etc.), and sub inventory with mini conversions (deeper inventory tracking and how that affects the balance sheet). I also spent some time drawing out some changes that are coming with our transition out to AWS (amazon web services - new web hosting model) and things that Wayne is working on. I drew our current model and also what I know of the newer AWS model. We talked about pros and cons and I tried hard to help Shannon know where things are going. Some exciting stuff coming down the pipeline. We talked about the concept of filtering and boiling things down and using a funnel type analogy to get towards the goal. Sometimes it takes years and years, but we are still making progress and learning along the way. We ended our meeting by using a quote from an author (different Shannon - Shannon Hale) - "There will still be time..." Sometimes that really helps me out, if I'm stressed or something. There will still be time... |
||
| Shop 4476 |
|
Adilas Time | 3/20/2019 |
The morning meeting started with Steve going over some of his plans. Normally he has been taking Wednesday's off, but he had a couple of small questions. He is building a new page to help cross tie PO's with balance sheet items (some special tax project of sorts). He is using some new CSS templates to wire things up. He is getting good and is able to start seeing his way through the entire project. It is pretty cool to see him getting the ideas, concepts, and then being able to mix and blend the pieces to get the output that he is looking for. That is exciting. Dustin was on with us as well. He is researching backend classes and API options for working with datatables for some of his projects. Steve wants me to start working on the transitional invoices and adding the inventory in transit (asset) piece to the balance sheet. I went in and added the new code. It wasn't too bad, most of the work was already done, it was just showing it up in the correct place on the report. Eric joined the meeting and had some questions about 3rd party solutions and push vs pull type requests. Most of our 3rd parties want to get data through the API sockets as a pull type request. We do have some that want the data pushed to them as things change (just in time or at the source of the changes). We talked about the differences in developing and also the differences in costs. Eric will be helping some of his clients move more towards the push type technology. We get better results that way and don't get flooded by too many pull requests. It is actually better for both parties, it just takes a little bit more planning and coding on the front end. Eric will end using that as a small revenue stream depending on what the clients want. Wayne and Alan popped in. Wayne let me know about a couple of pages out in the adilas marketplace that were not very secure. I ended up going through a number of pages and adding in some URL validation to help prevent XSS (cross site scripting hacks). |
||
| Shop 4477 |
|
Adilas Time | 3/21/2019 |
Steve and I were talking about our general direction as a company and how we want to get where we are going. Good discussion. I was running updates that Wayne had passed over to me for updating database tables between servers. I helped Steve with a small Metrc package table update and pushed up some new code. While I was doing that, Steve and Alan were working on some new code that deals with looking up both adilas id numbers and Metrc id numbers. Lots of back and forth between the two systems. Metrc is a state compliance system that we have to integrate with for some of our clients. Steve, Bryan, and I had a discussion about the adilas user group and when to launch some of that code. It currently exists, it is just somewhat hidden. We were talking about working with Wayne and his open id (open users) stuff. Eventually we would like to have all of the users held outside of the main corporations (a general user pool). Then, once we have that, we could then allow the users, in the open area... to vote on things, add new projects, and participate as they feel prompted. Steve would love all of the users to login into their own area... Then we could allow them to jump into the virtual data sphere and either start working, participate in the adilas community (all kinds of stuff), sell their own skills (real users doing training on what they do best), buy stuff, request access to certain sites, get training, etc. Lots of good options. Steve was talking about first impressions and helping to really help get some "wow's" and "that's cool". Steve wanted Bryan to start working on a timeline type page and/or report. Steve was talking about 4 main things that he would like in our virtual lobby - what are we working on, where do you want to work (what corps have granted you access), news and updates, and a virtual marketplace to allow you to offer your services (what are you good at). As far as the what are you good at (virtual job board), it would be super cool if we could show stats on what you have done in the system. For example: John Doe has 32,000 expense/receipts that he has made and 150,000 invoices and 10,000 uploaded photos and scans. Expand that idea, but just some ideas and such. Bryan and Steve got in to talking about some cool timelines, CSS templates, Inspinia and bootstrap options, awesome look and feel, etc. We also talked about how to move open community projects (general pool) into the adilas community funded projects (projects that people could donate and/or help fund) and how that would work. It would be super cool to show and allow votes to be cast on what people want, projects to be planned and commissioned and assigned, and parties being able to help and fund things as they see a need and/or want to participate. Great ideas. |
||
| Shop 4479 |
|
Adilas Time | 3/26/2019 |
It was just Dustin and I to start out with today. We pushed up some files for him to test live. I was trying to track down a small bug that Wayne had passed over to me to look at. It was something to do with code out in the adilas market (adilas world). Wayne popped into the meeting and gave us a small report as to where things are at with AWS transition. After that, Eric and I went over where we are at on the special accounts project. I'm trying to push on that project and finish up the code review. These are just general notes, but it was mentioned earlier today that one of the problems with our model is actually allowing the clients to control how much effort is put into custom code. They don't actually code things, but they do fund things. Sometimes they opt for the cheap route vs the best route for all parties. Sometimes this has an adverse affect on poorly written code or bad code. Another small topic from today was dealing with the size of the shared database structures. Some of them are getting very big. That makes it hard for certain queries to run efficiently or as optimized as possible. In the very near future, we will be pairing the database schema (tables and field names and values) into a smaller per corporation type model. That should really help with some speed and performance. Towards the end of the session I was working on a new application form for the state of Texas. This is used by trailer dealers and applying for special farm license plates and registration stuff. We already had this form in place, they just have a newer version that we had to code. |
||
| Shop 4480 |
|
Adilas Time | 3/27/2019 |
On the morning meeting with Dustin. He had a question about one of his custom pages. We got into it and worked on a dynamic variable for some of his JavaScript pieces. It got pretty deep as we had to find a special column number that was used to get special data that the page needed. We had to mix hardcoded columns, conditional columns, and an unlimited number of dynamic or user-defined columns. We had to find the correct column number that held a special batch number and that was dynamic as well (a mapped setting). Lots of moving pieces. Anyways, he nailed it and we got it done. We also set him up with some light FTP access to one of the servers to do some live testing. Good stuff. Wayne joined us and had a few questions and some updates. I then spent the rest of the session finishing up the new Texas application for farm use license plate form and PDF. I tested and uploaded files to all servers. Light tech support and emails. |
||
| Shop 4481 |
|
Adilas Time | 3/28/2019 |
We did a code merge and sign-off between Dustin and I. He has been working on some new settings, look and feel, and some cultivation pages and functions. Wayne joined us and started showing us a difference between the existing Application.cfm and Application.cfc. He was showing us some code on session start, on page request, on page load, on request end, etc. Lots of cool access points for the application as a whole. Economy, efficiency, consistency, etc. Lots of good stuff. We could pick up the gains and even gain some performance enhancements. At the end of the session, Wayne gave Dustin and I a few pictures and short peak into his life and what he and his family do for fun. It was nice to put names with faces and see what makes everybody tick. I really enjoyed that. |
||
| Shop 4513 |
|
Adilas Time | 4/1/2019 |
Steve was out all week, last week. He gave us all a report on some of his outings and adventures. Good stuff and Steve is excited to be back in the saddle. Alan reported on his reoccurring payment stuff. We talked about more charts, eye candy, and other reports. Alan and I also talked about working on some code sign-off and trying to get back to some of those other projects. I helped Steve with some code merging and pushed up some new files. I then got on a call with Eric and we touched base on his sub special account tracking project (loyalty points and gift cards). I told him that I was going to be pushing more on that this week. We also talked about an upcoming project to look at the adilas look and feel (over arching look and feel). This doesn't exist yet, but I was just talking with Eric about looking for ideas and making a plan. Anyways, he is interested in helping us out there. I setup a time with Shawn to work with him. I recorded some bills, did some email stuff, and recorded some notes. Trying to push the ball forward. Steve was on with Cory (an adilas rep) and they were going over some production and cultivation processes. Cory is going to be helping with some news and updates. After that, Wayne joined the meeting and we briefly went over the transition progress between Newtek servers (existing dedicated models) and upcoming AWS (amazon web services) stuff. |
||
| Shop 4522 |
|
Adilas Time | 4/2/2019 |
Wayne pretty much ran the morning meeting today. As soon as I joined, Wayne, Steve, and Dustin were already on. Once we got started, the entire session was dealing with updates and upcoming changes that are available to us out in AWS (amazon web services) land. Kinda interesting. We started the morning talking about photos, scans, and images and how those are stored currently. We moved to media/content (outside files) and then talked about ways of doing that kind of storage in the new environment. Wayne was showing us how quickly he was able to copy whole servers (existing dedicated boxes at Newtek) over to the AWS environment. He was also showing us how some of the resource management (CPU's, memory, and load balancing) were working as he spun up other instances. Very quick and very powerful. We are going to be able to speed up our time to market by leaps and bounds. Lots of talk about current model, options, and needs vs upcoming/future model, options, and new needs. There was quite a bit of time spent talking about existing flow, hot fixes, FTP (file transfer protocol), and code repositories and deployment options. Lots of talk about the advantages of building a testing library and running tests and unit tests to increase the level of comfort, efficiency, and confidence for the developers and the clients (system users). Wayne was using the term "tooling" and using the new tools and/or tooling environment to help standardize environments, processes, and expectations. We went over some possible problems with incomplete data and who is going to help mange and/or watch what pieces of the system. It really will be, and currently is, a giant team effort. We need all of the players to keep pulling their weight and doing what they do and how they do it. More and more talks about teams and cross training those teams. |
||
| Shop 4535 |
|
Code sign-off with Josh - Discount engine project | 4/3/2019 |
Josh joined the meeting and we worked through a few small things. He has 5 files that needed to be looked at. We talked about a few things and he will be reporting back in tomorrow for the final sign-off. Wayne jumped in and had some questions about where and how we are storing images. We talked about what it would take to get all of those images pushed out and stored on the adilas content server. As part of our conversation, we did a quick search to see how many pages may need to be updated. We got a number around 340 pages that deal with images and/or image paths. All of those files would need to be updated. Back on the code review project for Eric and the sub special account tracking stuff - sub of the balance sheet for things like loyalty points, gift cards, in-store credit, etc. |
||
| Shop 4521 |
|
Adilas Time | 4/4/2019 |
Meeting notes. Steve, Brandon, Wayne, and Dustin were on the meeting. Wayne was showing Steve and I about some cool image manipulation options. The site and tools are called Thumbor - image manipulation. It was capable of pushing up an image and then running all kinds of cool tweaks to the image, on the fly. Things like cropping, scaling, specific file sizes, grayscale, colorizing filters, etc. Pretty cool. Our goal there was to talk about ways of using existing tools to eliminate how much processing we make our ColdFusion servers do. Currently, we do all of our own image manipulation and storage on a per server basis. Just some ideas and concepts at this time in the game. After Wayne and Dustin left, Steve and I had a good discussion about where are things at and where are we headed. Both positive and potential dangerous and/or scary. Open conversation, no specific takeaways. Here are some of our notes: - Defining strengths and weaknesses and then working on both - Talking about the new AWS stuff - pros and cons - The skill level difference between an adilas user who is a developer and a normal or non adilas user computer developer - there is a difference. A lot of our stuff has a culture and all kinds of cause and effect relationships attached to single decisions, setting changes, and/or wants and needs. Interesting. - Your eductaion and expierence help you on your approach and/or your angle of attack - Revenue is not what you get to spend - We have a bunch of things that are partially done - finishers wanted - We talked about the scary pieces... These are mostly the unknowns... this could be on complexity of the AWS side of things and/or the unknowns on normal operational costs (speaking of AWS stuff). - Steve and I spent quite a bit of time on - Let's make a plan - this is huge. We really need to see what and where we are doing and going. We know that the plan changes from time to time, but we need something to help us direct this thing as we move forward. - Scratch built vs pre-fab or mash-up options. We have been pretty spoiled and have built our own scratch built pieces for years... we can't keep up with demands if we keep that same mentality. We are being somewhat forced to start using pre-fabricated pieces, outside code libraries, and outside products to create a mash-up of sorts. As a side note, even through we like scratch built features and options, one of the adilas goals is to become an API socket option (aka a mash-up option) for other companies. We want to build out the tools and then let others (individuals, companies, and even outside 3rd parties) consume the adilas API sockets as needed. - One of our concerns is, we spend hours and hours of our time on meetings and talking about possibilities. Technically, this is just R&D (research and development/design) stuff but it takes us away from other tasks (opportunity costs). We love it and we still need it. It comes down to a balance and a plan. - Talking about business and the different balances needed to keep things going and in check. Steve and I talked about an emerging 3-way balance between clients, systems, and education. Each of those main topics branch into sub topics. For example: Clients may branch into sales, funding, shear numbers (how many clients), and market demands. The system side of things seems to branch into user interface, functionality, features, settings, permissions, development, and tech. The education side seems to open into documentation, ease of use, instructions, guard rails (don't let people fall off), just in time learning, and the need for good reps and consultants and other trained individuals. Very interesting. Shannon and I had a similar conversation the other day. See this link for more information: https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4506 |
||
| Shop 4554 |
|
General | 4/4/2019 |
Helping Dustin with a code merge and light clean-up. We had to do some manual cross checking, but got the files merged in and uploaded to the servers. Spent the rest of the time doing clean-up, recording notes, and writing an email to Wayne requesting that we get a plan in place for the transition over to the AWS (amazon) stuff. |
||
| Shop 4526 |
|
Adilas Time | 4/8/2019 |
It must be Monday... We started out on the morning meeting and only Steve and I were on at first. We chatted about the transition over to the AWS (amazon) stuff. We have a number of questions and aren't really sure which way to turn. Steve needs to provide some of our clients with an answer, can we service them or not, and we need to know how long it will take to get the AWS stuff fully up and running. Lots of unknowns, but some great potential. Part of us wants to return to what we know (older stable ground) and the other part of us wants to keep pushing forward (new and uncharted but promising ground). It creates an emotional battle of sorts. We switched gears and Steve had some questions about a project where he is tying in balance sheet numbers to vendors. As part of his project, he was trying to come up with a switch that we could flip to help us know if a vendor was an inventory (parts or items) vendor or just a normal vendor. As we talked about it, we decided to take it out to an app type level (the 12 main system players). We talked about that and Steve liked that idea. I got him some code to help him get started. It is amazing how much, as we keep going, that the system keeps organizing itself into main player groups and what kind of relationships are needed per system or main player group. Very interesting. Almost like it likes to be organized into groups and related functions. We sure have learned a lot along the way. Alan joined the meeting and we were talking about some of his projects. He is still working on automating some of the reoccurring invoice stuff. We also talked about having Bryan work on the dynamic field names and settings per main player group. That is pretty deep and we may keep it tabled for now. Also, as we were talking about it, we were talking about how an object oriented programming approach may be a better solution for some of these new settings and defaults. Currently, we build and break, build and break (speaking about pulling and accessing settings). It may be nice to keep and hold some of the persistent or permanent settings and features. An object oriented model may be better equipped for that type of transaction. Currently, we look things up just in time. In the future, we may need to catch and hold those settings and maintain them in the user's session (stored in memory) options. Eric popped in and we did some check in and follow-up with his code review on the sub special account tracking project. This project is a sub of the balance sheet and deals with special accounts (mini bank account type objects) like customer loyalty points, gift cards, in-store credit, etc. That project is promised by next Monday. I will be trying to focus on the code sign-off this week. After that, Eric and Steve and I started talking about some of the new look and feel, CSS, and user interface stuff that Eric is wanting to help with. Both Steve and Eric were talking about a virtual "Adilas Cafe" or a global landing spot for the adilas users. This all goes back to separating the users from the main application code. There will still be a tie-in, but we are seeing a bigger need to keep users on the outside as a single entity and then allow them to go in and work or be a part of a corporation. We have many users that have and/or will need access to multiple corporations, and even be able to bridge across physical servers. Currently, our model is based on users per server and then tied to corporations based on active permissions to those corporations. We are seeing a need to break that down even further and have a master or global user id (virtual pool of users) and then allow them to be bridged to different corporations on a more global scale vs just per server (physical box) vs the possibilities of dynamic cloud networks. As we got deeper into the conversation about the potential of the Adilas café type model, we were talking about doing mock-ups, flow charts, etc. Eric had some questions about authentication servers and how that would all roll into the mix. We told him that he would need to get with Wayne to get more details. As we talked, we decided that Eric and Wayne should work together in a mini team type environment. As we explored the options, some of Steve and I's concerns (listed at the top of this entry) started to go away. We ended up somewhat asking Eric to be a project manager type role for this transition project between Newtek and AWS. That little tweak in the plan and how the developers were paired up, made a ton of difference and some of the anxiety started to go away. We need to crate a list of specs for Wayne and what we want the application to do. Plan and play as if for years. We also talked about in-house coordination and communication. That is a huge key and helps all parties involved. Steve was talking about skating to where the puck (pretend we are playing hockey) is going to be. He and Eric were talking about the existing login pages and the corporation chooser page as being the beginning of the adilas café (landing spot or centralized common ground area). Good discussion. We would really like to keep pushing the ball forward and making each system its own entity. This means having a centralized database controlling users and access to different corporations and/or entities and then having the individual entities having their own database or system for just their stuff. Currently, there are a number of tables that are shared between parties. For speed and efficiency, we really need to split things up more. This may also affect how we are able to bill for storage and processing vs a set monthly system fee. Anyways, as the conversation progresses, Steve and Eric were talking about using the choose corporation page as the starting common spot or commons area. Steve was also saying that he would like the users to be able to go to work (assigned or authorized corporations) as well as go play (demo sites, play grounds, or play sites). Basically, anybody could have an adilas account, and then they could either go into a real site (aka work) or a play site (aka play and testing). Fun ideas. One of Eric's and Wayne's first item of business will be to do a virtual inventory check of where things are at on the project and what will still be needed and/or stands in the way. That will be awesome. It really was an mini answer to prayers that we decided to team up Eric and Wayne. It helped us let go and be willing to embrace some of the unknowns. As part of that, we are hoping that having the guys work together in mini teams helps us prioritize what really needs to be done and when. Sometimes, by yourself, it is hard to know what needs attention first, especially if it feels like everything is vying or trying to get the input, attention, and/or priority. Crazy stuff, I'm been there before and will be back again. Steve and I talked about cycling through hardware and how that is just part of the line of work we are in. Later this year, we will need to buy some new laptops and upgrade some of our development environments. One of the breakthroughs for today was the mini team concept. We have Steve and I, Steve and Dustin and Josh, Brandon and Alan, Wayne and Eric, Shari O. and Pat and Drea, etc. There are starting to be all kinds of little teams. That is awesome. Shawn popped in and reported on some payroll updates and changes. We scheduled a time to meet again tomorrow. He is also willing to help me out with some of my projects and such. After that, I spent the rest of the session recording notes and trying to get caught up (as good as I could). |
||
|
|
||||||