Search The Adilas.biz Developer's Notebook
Time Period:
Daily (enter the day you want to see)
Monthly
Custom Date Range to
Template Filter:
Color Code:
General Text Filter:

(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:
 
Adilas.biz Developer's Notebook Report - 4/4/2023 to 4/4/2023 - (4)
Photos
Time Id Color Title/Caption Start Date   Notes
No po photos available. Click to view time details.
Shop 10005 Adilas Time 4/4/2023  

Steve and I were going over sub inventory attributes. We got into all kinds of attributes. We talked about sub inventory attributes, parent attributes, and flex attributes. Currently, each section or attribute does a specific thing. There is a growing need for more or better sub attributes and parent attributes. Easier to get things into the database for storage and easier to pull the data back out. I mentioned to Steve that we would really like to add a few fields and values to the current sub inventory attributes. They are things like: part category id, app type id, main id (tied to the part_id), and sub inventory attribute id numbers. We have some of those columns but there has not been a project to standardize things yet. It's still on the wish list.

Quite a bit of talk about new corp-specific tables and data storage. Evolution... everything is evolutionary... look and feel, logic, business flow, and even sales (how we sell our products and services). We will keep working on making it easier and easier to use. SG&A costs (selling general and administrative costs) and going clear out to the financials. To the client, it is just data storage. To us, we have to make it all flow and work together as a system. Sometimes that's a challenge.

As recap - for sub inventory attributes or sub attributes:

1. Add the part category id as a look-up value (this would be a new column)
2. Add the main part id as a look-up value (we could use the column called main_id to hold the part_id - it would work perfect)
3. Add in the correct app type id as a look-up value (we already have this column but don't use it for sub inventory attributes - we just need to use it and tie it in better)
4. Add in the associated sub inventory attribute id number as a look-up value (this would either be a new column and/or repurpose an existing column that is not being used in the custom_text, custom_dates, and custom_numerics tables).
5. If we do change things here, we may want to go through these tables and rename fields and values. It was originally created for a specific project and then used over and over again for other semi related projects. Now that we know what it will be used for... we should take the time to future proof it a bit.

If we could add these fields and/or data points into the sub inventory attributes, it would be so much better for getting the data back out of the system. Currently, things are tied to the sub inventory id or sub reference id. We then look that up to figure out the part id and then use the part id to look-up the part category id. It would duplicate a little bit of data but it would make it so much easier to find things and quickly reference things. Currently, we have to join multiple tables and go virtually up and down the chain to find everything that we need. I would recommend that we do a special project, add the above, do some clean-up and then move forward. That would really help. Just my two cents.

 
No po photos available. Click to view time details.
Shop 10018 Server Meeting 4/4/2023  

Hostek went down a couple of days ago. Wayne was reporting on what was going on. We talked about communication and disaster recovery processes. Who does what and what are steps and responsibilities. We need to more tech support from our hosting companies. We have like 40 servers there at Hostek. Most times they do great. However, if things go wrong and/or bad, we don't get any preferential treatment. We kinda need that.

Anyways, Wayne was doing his own trouble shooting processes and found a few problems. We have a growing need for more documentation for our processes and procedures. We also need to keep some of them super secure. That makes for an interesting mix. There is also a ongoing need for more communications and keeping everybody in the loop that needs to be there.

At some point, we would like to reclaim some of the WordPress stuff on our main site. Sometimes WordPress is a high level target, with tons of plug-ins, themes, and required sequential updates. Once again, we need to get documentation for all of these pieces. The next subject was a statement that everybody needs to give us documentation and architecture layouts. Some people don't like that, don't think like that, and it's worse then torture for them. We have to figure things out and figure out who is going to do what. Everybody has talents, virtues, strengths, and weaknesses. It is tough to require the exact same things from everyone. It will end up being a moving balance.

As a side note, we may end up needing to help certain people do some of those things like documentation, training, and certain communication skills or tasks. There may be a need for a new role to help the devs and get the info out of their heads and into a consumable format. Eventually we have to get documentation on all internal and external dependencies. There is a big difference between knowing what to do and actually doing it. Sometimes we are pushing so hard, it's hard to slow down and virtually clean-up or sweep the floor.

We talked about having a checklist for our developers. We have an old one that Alan and I worked on years ago, but that's all that we have at this point. Some of the developers just can't do the documentation (and sadly, some of them we don't want them to do it). It seems like the next steps are helping to collect and organize the information and documentation. We have some holes that need to be filled. John was commenting that we need to add this into the budgets and project costs. We need to charge more than just the developer's time. Once again, we may be going too fast or running too hard. We are missing a part of the puzzle.

Next, we went into talking about Adobe ColdFusion uptime on hosted platforms. Wayne was reporting to Cory about a survey that he was reading and what it was saying. Cory wanted the guys (Wayne and John) to call and talk with Hostek to see if we could some things changes (service levels and response times). We need to make sure that we have the access and tools that we need. Some of our clients are 24/7 everyday, even holidays.

The new dedicated testing server was the next major topic. We switched over to talking about the data 5 server, capturing documentation, and walking through the project with both Wayne and John. They are working on both training and documentation and so it is taking a bit longer. Making good progress. John has a project that is done that needs to be tested by some outside parties. He and Wayne are setting up and managing the project queue. Cory is helping to coordinate the actual projects and the testing.

Spent some time talking about look and feel and talking about a new version of the internal shopping cart. We know that there is a need there, we are just not sure how deep to jump. We may end up doing things in a couple of rounds. Round one, just look and feel. Round two new settings to toggle on/off certain fields, sections, columns, and features. There may be another round that gets into a smart cart level (deep cart engine logic). In a nutshell, we want to remove things and make it smarter and easier.

We are looking for feedback. Talking about timing on projects, testing, and pushing things all the way until they are live and in production (and fully documented). Shari O. popped in and was asking about insurance and levels of support from Hostek. Sometimes, the lack of support can be a deal breaker. We've seen this even in sales of our system. It's a part of the puzzle that gets overlooked sometimes.

 
No po photos available. Click to view time details.
Shop 10036 Data clean-up for a client 4/4/2023  

Working on a data clean-up project for a client. Deep in the logic (loops and conditional statements). John contacted me and we jumped on the GoToMeeting session. He and I ended up talking about sanitation of data, testing servers, and turning off all outside API sockets and 3rd party solutions. I showed him how to clean-up and turn off a few outside dependencies for the new testing server.

 
No po photos available. Click to view time details.
Shop 10037 Data clean-up for a client 4/4/2023  

Back on the data clean-up project. Actually writing the update code. Finished up all but the subs. Came back later and got all of the sub inventory updates done as well. Two different sessions. One from 5:15 pm to 7:00 pm and the other from 8:30 pm to 9:15 pm. Total of 2.5 hours for these two sessions.